Skip to content
Skills Library
Design & UX · Building & coding

design-add-component

/design-add-component

Add one new component to a finished design system: spec it Socratically (seeded from the standard catalog when it's a known pattern), append it to COMPONENTS.md's catalog and sections, build it across every theme via a component-smith worker, re-assemble the kitchen-sinks, and gate with the deterministic check plus a scoped visual-critic pass. Trigger whenever the user wants a component added to an existing design system — "add a date-picker to the design system", "we need a stepper component", "the system is missing a file-upload", or /design-add-component. Requires FOUNDATION.md, THEMES.md,

Repository
skills ↗
Licence
MIT
Last repository change
22.09.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 22.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Add one new component to a finished design system: spec it Socratically (seeded from the standard catalog when it's a known pattern), append it to COMPONENTS.md's catalog and sections, build it across every theme via a component-smith worker, re-assemble the kitchen-sinks, and gate with the deterministic check plus a scoped visual-critic pass. Trigger whenever the user wants a component added to an existing design system — "add a date-picker to the design system", "we need a stepper component", "the system is missing a file-upload", or /design-add-component. Requires FOUNDATION.md, THEMES.md,

Triggers from the description

s a known pattern), append it to COMPONENTS.mdadd a date-picker to the design systemwe need a stepper componentthe system is missing a file-upload

Arguments

/design-add-component <component name/slug> [what it's for]
Original author description

Add one new component to a finished design system: spec it Socratically (seeded from the standard catalog when it's a known pattern), append it to COMPONENTS.md's catalog and sections, build it across every theme via a component-smith worker, re-assemble the kitchen-sinks, and gate with the deterministic check plus a scoped visual-critic pass. Trigger whenever the user wants a component added to an existing design system — "add a date-picker to the design system", "we need a stepper component", "the system is missing a file-upload", or /design-add-component. Requires FOUNDATION.md, THEMES.md,

How it works

  1. Step 1 — Spec it
  2. Step 2 — Build it
  3. Step 3 — Assemble & gate
  4. When you are done
Original SKILL.md headings · 28 lines, 316 words
SKILL.md preview
---
name: design-add-component
description: >
  Add one new component to a finished design system: spec it Socratically (seeded from the standard catalog when it's a known pattern), append it to COMPONENTS.md's catalog and sections, build it across every theme via a component-smith worker, re-assemble the kitchen-sinks, and gate with the deterministic check plus a scoped visual-critic pass. Trigger whenever the user wants a component added to an existing design system — "add a date-picker to the design system", "we need a stepper component", "the system is missing a file-upload", or /design-add-component. Requires FOUNDATION.md, THEMES.md, and COMPONENTS.md to exist. Do NOT trigger during the initial catalog phase (/design-components) or for changing an existing component (/design-revise).
argument-hint: "<component name/slug> [what it's for]"
model: opus
allowed-tools: Read, Write, Edit, Glob, Agent, Bash(bash *design-build/assemble.sh *), Bash(bash *design-audit/design-check.sh *), Bash(rm -rf design-system/.fragments*)
---

# Design Add-Component — Grow the Catalog

The out-of-band entry point for one new component after the system is built. Same contract as the phase skills, scoped to a single slug.

**Preflight:** `design-system/FOUNDATION.md`, `THEMES.md`, and `COMPONENTS.md` must exist — otherwise route to the missing phase skill and stop. Read the conventions (`<skills-root>/design-audit/references/conventions.md`) and check the component isn't already in the catalog (then this is `/design-revise`'s job — say so and stop).

## Step 1 — Spec it

Draft the component's section yourself: if the standard catalog (`<skills-root>/design-components/references/standard-catalog.md`) covers it, instantiate that entry adapted to FOUNDATION.md; otherwise first-cut it from the foundation and the stated purpose. Same section shape as every other component: slug, anatomy (shared DOM), variants, states, accessibility, i18n, theme variance.

Walk the open calls with the human one at a time — variants, states, the theme-variance opportunity — exactly as `/design-components` would. Then edit `COMPONENTS.md`: the `- \`slug\` — one-liner` catalog line at its right position in kitchen-sink order, plus the section.

## Step 2 — Build it

Spawn one **component-smith** subagent (`subagent_type: component-smith`) with the slug, the `COMPONENTS.md` path, the conventions path, every theme dir, and the fragments dir. It writes the fragments; you never see the markup.

## Step 3 — Assemble & gate

1. `bash <skills-root>/design-build/assemble.sh assemble design-system <theme-dir>` for each theme dir (the new block lands at its catalog position), then `… index design-system` if theme dirs changed (they didn't — skip).
2. `bash <skills-root>/design-audit/design-check.sh design-system`. FAILs on the new slug → respawn the smith once with the FAIL lines; still failing → surface to the human.
3. Spawn **visual-critic** (`subagent_type: visual-critic`) scoped to the new slug across all themes; present findings, apply approved fixes via another targeted smith round.
4. `rm -rf design-system/.fragments`.

## When you are done

Report: the slug, its catalog position, per-theme variance notes from the smith, gate summary, critic verdict. Defer the commit to `/commit`.

Versions

The database has no other skills named design-add-component.

Database snapshot: 13.11.2026 · package version 73c404fa6253 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 85design-add-theme
    Add one new theme (a light+dark pair) to a finished design system: optionally distill fresh references, seed a complete token strawman via the theme-drafter subagent (kept a deliberate sibling of the existing themes), refine Socratically with prototype loops, write the two theme…
  • 100design-components
    Spec the design system's component catalog: settle which components exist and, per component, the shared anatomy (one DOM for all themes), variants, states, accessibility contract, i18n slots, and what themes may vary — written to design-system/COMPONENTS.md with its…
  • 90review-component
    Reviews a UI component against its Open Components contract, or a codebase's theme and component styles against a foundation like Design Tokens, reporting every rule as pass or fail with its ID and the evidence, then fixing the failures. Use when asked to review, audit or check…
  • 86add-component
    Add or change a Roastpilot UI component in packages/ui, keeping the design system in step. Use when a screen needs a reusable piece of UI, or an existing component's look, sizes or rules change.
  • 92add-component
    Add a new component to the VelvetKit registry, or add a sub-part to an existing one. Use when asked to build, add or scaffold a UI component in this repo (not in an app that has installed VelvetKit — that's a different skill).
  • 100design-system-doc
    Document a design system component. Use when the user says "design system docs", "document this for the design system", "add this to the design system", "design token", "component library docs", "style guide", "design system entry", or wants to formally document a pattern,…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.