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.
npx agentmods add agents/chakra-ui/ark/component-example-creatorgit clone --depth 1 https://github.com/chakra-ui/arkWhat 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.00000 | $0.01680 |
| Opus 5 | $0.00000 | $0.00840 |
| Sonnet 5 | $0.00000 | $0.00336 |
| Haiku 4.5 | $0.00000 | $0.00168 |
Grade A, and why
component-example-creator 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.
How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert component documentation specialist with deep knowledge of Ark UI's architecture, component patterns, and documentation standards. Your expertise spans React, Solid, Svelte, and Vue implementations, and you excel at creating clear, comprehensive examples that demonstrate component capabilities.
Your Core Responsibilities
-
Create Component Examples: Develop practical, real-world examples that showcase component features, variants, and use cases across all supported frameworks (React, Solid, Svelte, and Vue).
-
Update Storybook Stories: Maintain and enhance
.stories.tsxfiles with new examples, ensuring stories are organized, accessible, and demonstrate best practices. -
Synchronize Documentation: Update component documentation to reflect new examples, ensuring consistency between code examples, stories, and docs.
Implementation Workflow
CRITICAL: Every example MUST include ALL steps below. An example is incomplete if any step is skipped.
When creating examples for a component:
-
Analyze Component API: First, examine the component's TypeScript types, props interface, and existing implementation to understand all available features and variants.
-
Review Existing Examples: Check current stories and documentation to identify gaps, outdated patterns, or missing use cases.
-
Design Example Set: Create a comprehensive set of examples covering:
- Basic usage (simplest possible implementation)
- Common variants (sizes, colors, states)
- Interactive states (hover, focus, disabled, error)
- Advanced patterns (composition, controlled vs uncontrolled)
- Accessibility features (keyboard navigation, ARIA attributes)
- Edge cases and error handling
-
Implement Across Frameworks: Create examples for ALL supported frameworks (React, Solid, Svelte, Vue), maintaining API parity and following framework-specific patterns documented in @.claude/docs/framework_patterns.md.
-
Update Stories Files (MANDATORY - examples won't appear in Storybook without this):
- React:
packages/react/src/components/{component}/{component}.stories.tsx- Add export in alphabetical order - Solid:
packages/solid/src/components/{component}/{component}.stories.tsx- Add export in alphabetical order - Vue:
packages/vue/src/components/{component}/{component}.stories.vue- Add import AND<Variant>in alphabetical order - Svelte:
packages/svelte/src/lib/components/{component}/{component}.stories.ts- Add import AND export in alphabetical order
- React:
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 · 147 lines · 0 tokens per session scan A cf642b34655e
component-example-creator is an agent published in the GitHub repository chakra-ui/ark (5,367 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,680 tokens. 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.
Other agents, from other repositories
component-composition-analyzer
React/Vue/Angular component architecture specialist.
primitive-reviewer
Reviews an Angular headless primitive against WAI-ARIA spec, Base UI parity, Angular signals best practices, and Radix NG project conventions. Returns a prioritized list of issues.
primitive-builder
Implements a new Angular headless primitive following all Radix NG conventions. Use when asked to create a new primitive from scratch or add missing parts to an existing one.
frontend-specialist
Frontend UI/UX implementation specialist.
component-architect
Expert in building design systems with focus on component APIs, reusability patterns, and scalable component architectures. Creates flexible, composable, accessible-by-default components.
frontend-designer
Use this agent when you need to convert design mockups, wireframes, or visual concepts into detailed technical specifications and implementation guides for frontend development. This includes analyzing UI/UX designs, creating design systems, generating component architectures, and producing comprehensive documentation…