From visual-design
This skill should be used to regenerate the component index after manually adding, editing, or removing component spec files. Trigger phrases: "update component index", "rebuild component index", "refresh design index", "regenerate component index".
How this skill is triggered — by the user, by Claude, or both
Slash command
/visual-design:update-component-indexThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Regenerate `design/components/index.md` from the current spec files.
Regenerate design/components/index.md from the current spec files.
Look for design/components/ directory. If it doesn't exist:
STOP. Tell the user: "No component compendium found at design/components/. Run the
visual-design-consultant skill first to establish a design system."
If design/components/index.md exists, read it and note the current component list.
If it doesn't exist, note this is a first-time generation.
Use Glob to list all .md files in design/components/ excluding index.md.
For each spec file, read it and extract:
.md extensionSort all entries alphabetically by component name.
Write design/components/index.md:
# Component Index
| Component | Category | Related | Keywords |
|-----------|----------|---------|----------|
| [name] | [category] | [related] | [keywords] |
One row per component. If design/components/ has no spec files, write the file with just
the header and an empty table.
Compare the new index against the previous one (from Step 2):
Report to the user:
npx claudepluginhub thekostakis/requirements-gatherer --plugin visual-designGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.