원클릭으로
component-create
// Build a Kiso component from scratch. Reads shadcn/Nuxt UI sources, creates theme module, ERB partials, Lookbook previews, docs, E2E tests. Use when building a new component or picking up where a previous attempt left off.
// Build a Kiso component from scratch. Reads shadcn/Nuxt UI sources, creates theme module, ERB partials, Lookbook previews, docs, E2E tests. Use when building a new component or picking up where a previous attempt left off.
Build UIs with Kiso — accessible Rails UI components with Tailwind CSS theming. Use when creating interfaces, customizing themes, building forms, or composing page layouts in Rails + Hotwire apps.
Kiso component conventions and development workflow. Points to the right docs for building, reviewing, and shipping components.
Audit all documentation for staleness after code changes. Checks docs site, CLAUDE.md, skills references, contributing skill, agents, and project/ files. Use after completing a feature, merging a PR, or when asked to check docs.
Guide through releasing a new version of kiso. Use when cutting a release, publishing a new version, or running bin/release.
Review a Kiso component for quality and consistency. Runs the 12-point checklist against shadcn source, design system rules, and deliverables. Use on a PR, branch, or working directory.
Agentic Component Factory — build multiple Kiso components in parallel using builder and reviewer agents in isolated worktrees. Usage: /factory #47 #48 or /factory #47 #48 #49 (pass issue numbers)
| name | component-create |
| description | Build a Kiso component from scratch. Reads shadcn/Nuxt UI sources, creates theme module, ERB partials, Lookbook previews, docs, E2E tests. Use when building a new component or picking up where a previous attempt left off. |
Build a Kiso component following the established workflow and quality standards.
Read project/component-creation.md — this is the authoritative guide.
Follow every step: mandatory reading, naming rules, implementation steps,
Lookbook preview rules, and the quality checklist.
If given an issue number, read the issue with gh issue view N to get
the component name and any specific requirements.
Work through the implementation steps in order. The guide contains code templates for theme modules, ERB partials, Lookbook previews, and E2E tests.
Before finishing, run through the quality checklist at the bottom of
project/component-creation.md. Every item must pass.
Run lint and tests:
bundle exec standardrb --fix
npm run lint && npm run fmt
bundle exec rake test
npm run test:unit
npm run test:e2e