A command template for adding a new Ark UI component, where Ark UI provides unstyled interface behavior for React applications. It lists the component files, exports, theme recipes, and examples to update.

Use it to implement and register a named Ark UI component, including its React code, imports, theme variants, and examples.

It turns a component addition into a defined checklist, reducing missing exports, typings, styles, or documentation examples.

ark — Command by chakra-ui

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add commands/chakra-ui/chakra-ui/ark

Clone the repo

git clone --depth 1 https://github.com/chakra-ui/chakra-ui

Made for: Claude Code.

Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 935 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00006	$0.00935
Opus 5	$0.00003	$0.00467
Sonnet 5	$0.00001	$0.00187
Haiku 4.5	$0.00001	$0.00093

Measured 2d ago against content hash 051960900a01, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ark 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 2d 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/ark.md · 108 lines

How it starts

The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Context

Ark UI is a headless UI library styled with @ark-ui/react.
Reference: https://ark-ui.com/llms-react.txt

Task

Implement a new component named $ARGUMENTS with the following steps:

Component setup
- Create a folder in @packages/react/src/components/$ARGUMENTS
- Add the component implementation in $ARGUMENTS.tsx
- Add an index.ts to re-export typings and the component in long form
- Add a namespace.ts to support dot-notation imports
Exports
- Update @packages/react/src/components/index.ts to include $ARGUMENTS
Anatomy
- If the component isn't exported from ark-ui anatomy, add it to @packages/react/src/anatomy.ts
- Import anatomy: import { componentAnatomy as arkComponentAnatomy } from "@ark-ui/react/component"
- Export anatomy: export const componentAnatomy = arkComponentAnatomy
Recipes
- If variants or sizes are needed, create a recipe in
  @packages/react/src/theme/recipes/$ARGUMENTS.ts
- Import anatomy and use defineSlotRecipe
- Important: Add recipe to theme system:
  - Import in @packages/react/src/theme/slot-recipes.ts
  - Add to slotRecipes export object
Examples
- Add an example at
  @apps/compositions/src/examples/$ARGUMENTS-basic.tsx
Storybook
- Create stories at @packages/react/__stories__/$ARGUMENTS.stories.tsx
- Export examples from compositions with proper naming
Documentation
- Add docs at @apps/www/content/docs/components/$ARGUMENTS.mdx
- Follow the style of existing component docs (usage, variants, examples)
- Include descriptive paragraphs for each example explaining:
  - What the example demonstrates
  - When to use this pattern
  - Benefits and use cases
Reference implementation
- Use segment-group (@packages/react/src/components/segment-group/) as a guide for:
  - component.tsx → style context setup
  - index.ts → exports
  - namespace.ts → dot-notation support

Read the full file on GitHub · 108 lines

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.

2d ago First seen · 108 lines · 6 tokens per session scan A 051960900a01

Subscribe to this mod's changes

ark is a command published in the GitHub repository chakra-ui/chakra-ui (40,613 stars, last pushed 2d ago), licensed MIT. It adds 6 tokens to every session and 935 once invoked, about $0.0000 per session on Opus 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.

Frontend React a11y accessible chakra-ui react-components uikit

check-docs-consistency

Use the check-docs-consistency skill to validate alignment across rootage/design/react docs.

daangn/seed-design · 6 tokens

design-to-code

Mockup-to-component pipeline using Google Stitch, 21st.dev, and Storybook MCP. Accepts a screenshot, a description, or a URL and produces production-ready React components, checking existing Storybook components before generating anything new. Use when implementing UI from a mockup or screenshot. To call the MCP tool…

yonatangross/orchestkit · 86 tokens

ark