ark: Command for Claude Code

.claude/commands/sync-docs.md

sync-docs is a command for Claude Code from chakra-ui/ark. It costs 14 tokens per session (339 once invoked), scanned A, original, MIT.

A documentation-maintenance command that reviews recent component work and records reusable patterns, pitfalls, and guidelines in project files.

In plain words
What is it for?
Use it to update component pattern notes, agent instructions, and project-level guidance after development work.
Why use it?
It helps prevent useful lessons from getting lost in conversation history and keeps guidance for future component work up to date.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions CLAUDE.md.

This is chakra-ui/ark's own configuration. It tells Claude Code how to work on ark itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ark configures →

About the project

Ark UI is a headless component library: it supplies accessible UI behavior and structure without visual styling, so developers can build their own design systems. It supports React, Vue, Solid, and Svelte applications.

chakra-ui/ark · 5,453 stars · on GitHub · ark-ui.com

Reuse

Borrowing it

Nothing to install: this file belongs to chakra-ui/ark. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/chakra-ui/ark/main/.claude/commands/sync-docs.md
Clone the repo
git clone --depth 1 https://github.com/chakra-ui/ark

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for sync-docs

README.md
[![agentmods](https://agentmods.dev/badge/commands/chakra-ui/ark/sync-docs/github.svg)](https://agentmods.dev/commands/chakra-ui/ark/sync-docs)
Your own site
<a href="https://agentmods.dev/commands/chakra-ui/ark/sync-docs"><img src="https://agentmods.dev/badge/commands/chakra-ui/ark/sync-docs/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for sync-docs

Your own site · 80×15
<a href="https://agentmods.dev/commands/chakra-ui/ark/sync-docs"><img src="https://agentmods.dev/badge/commands/chakra-ui/ark/sync-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 339 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00014 $0.00339
Opus 5.5 $0.00006 $0.00136
Sonnet 5.5 $0.00003 $0.00068
Haiku 4.5 $0.00001 $0.00034

Measured 2mo ago against content hash c78c8f9a4c85, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

sync-docs scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/sync-docs.md · 50 lines

What it actually says

Review the conversation history and identify patterns, best practices, and learnings from recent component development work. Then update the following files as needed:

Files to Update

  1. @.claude/docs/component_patterns.md

    • Add new component patterns discovered
    • Document common pitfalls and solutions
    • Add best practices for component API usage
    • Include documentation writing guidelines
  2. @.claude/agents/component-example-creator.md

    • Update code quality standards based on learnings
    • Add new documentation guidelines
    • Include patterns for better example creation
  3. @CLAUDE.md (if needed)

    • Update project-level guidance
    • Add new principles or conventions

What to Include

Focus on generic, reusable patterns that will help with future component development:

  • Component API access patterns (Context vs hooks)
  • Common styling requirements
  • Documentation writing best practices
  • State management patterns
  • Accessibility considerations
  • Cross-framework consistency guidelines

What to Exclude

Skip component-specific implementations unless they represent a broader pattern that applies to multiple components.

Process

  1. Review recent work and identify patterns
  2. Read current documentation files to avoid duplication
  3. Add new sections or update existing ones with clear examples
  4. Use ✅ CORRECT / ❌ WRONG patterns for clarity
  5. Include rationale for why patterns are important
  6. Keep updates concise and actionable

After updating, provide a summary of what was added and why it will help future development work.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2mo ago First seen · 50 lines · 14 tokens per session scan A c78c8f9a4c85

Subscribe to this mod's changes

sync-docs is a command published in the GitHub repository chakra-ui/ark (5,453 stars, last pushed 2d ago), licensed MIT. It adds 14 tokens to every session and 339 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

sync-docs compared with commands from other repositories

sync-docs next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
sync-docschakra-ui/arkCommand5.5k2d agoMITA14Claude Code
gen-videoAdityaraj0421/naksha-studioCommand35319d agoMITA56Claude Code
initmahmoudilyan/marmouiCommand203mo agoMITA39Claude Code
prototypemahmoudilyan/marmouiCommand203mo agoMITA36Claude Code
marmo-buildmahmoudilyan/marmouiCommand203mo agoMITA27Claude Code
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code