design-components
/design-components
Opisuje katalog komponentów systemu projektowego: anatomia wspólna dla motywów, warianty, stany, kontrakt dostępności, sloty i18n oraz zakres zmian motywów, w design-system/COMPONENTS.md.
Ocena i bezpieczeństwo
- Pliki w paczce
- 2
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 22.09.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Opisuje katalog komponentów systemu projektowego: anatomia wspólna dla motywów, warianty, stany, kontrakt dostępności, sloty i18n oraz zakres zmian motywów, w design-system/COMPONENTS.md.
Wyzwalacze z opisu
Argumenty
/design-components [optional: which components to (re)spec — default: the full catalog from FOUNDATION.md]
Oryginalny opis (EN)
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 machine-readable ## Catalog list. Trigger after /design-themes whenever the user wants to define, spec, or restructure the component set — e.g. "let's spec the components", "define the component catalog", "what components do we need", or /design-components. Requires FOUNDATION.md (uses its Catalog trim); seeds from the bundled sta
Jak działa
- Step 1 — Draft the whole spec
- Step 2 — Walk the open decisions
- Step 3 — Write
- When you are done
Podgląd SKILL.md
--- name: design-components description: > 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 machine-readable ## Catalog list. Trigger after /design-themes whenever the user wants to define, spec, or restructure the component set — e.g. "let's spec the components", "define the component catalog", "what components do we need", or /design-components. Requires FOUNDATION.md (uses its Catalog trim); seeds from the bundled standard catalog, walks only the genuinely open decisions with the human, and writes the spec — no HTML: building the kitchen-sinks is /design-build's job. Re-entrant: revises an existing COMPONENTS.md diff-oriented. Do NOT trigger for adding one component to a finished system (/design-add-component) or for changing a built component (/design-revise). argument-hint: "[optional: which components to (re)spec — default: the full catalog from FOUNDATION.md]" model: opus allowed-tools: Read, Write, Edit, Glob --- # Design Components — Spec the Catalog You are phase 3: you turn FOUNDATION.md's catalog trim into `design-system/COMPONENTS.md` — the **structural spec** that `/design-build`'s workers implement and `design-check.sh` audits against. Spec only; you write no HTML. **Preflight:** `design-system/FOUNDATION.md` must exist (stop and point at `/design-foundation` otherwise); read it, the bundled standard catalog (`references/standard-catalog.md` beside this skill), and the conventions (`<skills-root>/design-audit/references/conventions.md`) — the catalog grammar, marker contract, and required sample set constrain what you write. `THEMES.md` should exist too; if it doesn't, warn that theme-variance notes will be guesswork but proceed if the human wants. If `COMPONENTS.md` already exists, this is a **revision**: work only the components `$ARGUMENTS` names, and warn that changing the spec of an already-built component obligates a `/design-revise` pass. ## Step 1 — Draft the whole spec Build the full `COMPONENTS.md` draft yourself in one pass — no subagent needed; the standard catalog is the seed: - Start from FOUNDATION.md's **Catalog** section (the included slugs + additions). For standard components, instantiate the standard-catalog entry, adapted to the foundation (a "calm, editorial" system needs fewer button variants than an ops console). - For project-specific additions, draft a first-cut spec from the foundation and the products named in the intent. - Order the `## Catalog` list in kitchen-sink order (the standard catalog's grouping is a good default). Per component section: ```markdown ## <Name> - **Slug**: `<slug>` - **Anatomy**: the shared DOM in one short indented sketch — elements, nesting, where label/help/error/icon live. One structure for all themes. - **Variants**: - `<variant-slug>` — when-to-use one-liner. (Exact grammar, two-space indent — `design-check.sh` parses this list and verifies each variant ships a `data-ds-story="variant-<slug>"` sample in every theme.) - **States**: which of default/hover/focus-visible/disabled/invalid/loading apply. - **Overflow**: what happens when content outgrows the shape — `truncate` / `wrap` (and how the shape adapts, e.g. radius downgrades on multi-line) / `disallow` (a content rule keeps it short). Mandatory for bounded-shape components (button, badge, chip/pill, tab — anything whose silhouette is part of its identity); a pill wrapping to two lines is a spec decision, never a rendering accident. Also state here whether the component is naturally full-bleed (inputs, tables, banners) — everything else renders at intrinsic width in the kitchen-sink. - **Accessibility**: roles/ARIA wiring, keyboard expectations, labeling rules. Composite controls (affixed input, input-with-button) name the single focus-ring owner per the conventions' one-indicator rule. - **i18n**: which parts are locale-formatted slots (data-ds-locale), RTL notes beyond the default mirroring; the long-string sample's behavior follows the **Overflow** line. - **Theme variance**: what themes may legitimately vary (density, columns, emphasis) vs what is fixed. ``` ## Step 2 — Walk the open decisions Don't interview all ~25 components — present the draft's shape (catalog list + one example section) and walk **only the genuinely open calls**, one at a time: - Variant sets that depend on product reality (does anything need a destructive button? how many table densities?). - The project-specific additions — these get a real per-section dialog since no standard entry backs them. - Anywhere the foundation and the standard catalog pull apart. - Theme-variance opportunities worth designing (the list-as-rows-vs-columns kind) — each one named per component, since it's what makes multiple themes worth having. Adjust the draft as decisions land. Cutting a component is always on the table — every entry is markup someone maintains. ## Step 3 — Write Write `design-system/COMPONENTS.md`: intro line, `## Catalog` (exact grammar: `- \`slug\` — one-liner`, kitchen-sink order), then the per-component sections. Update FOUNDATION.md's Catalog section if the dialog changed the set (one-line edit, not a rewrite). ## When you are done Report: catalog size, the components with notable theme variance, anything deferred. Hand off to `/design-build` to produce the kitchen-sinks. Defer any commit to `/commit`.
Pliki w paczce (2)
- SKILL.md 5 KB
- references/standard-catalog.md 4 KB
Wersje
W bazie nie ma innych skilli o nazwie design-components.
Migawka bazy z 13.11.2026 · wersja paczki 8aa402aa8f74 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 90design-add-component
Dodaje nowy komponent do gotowego systemu projektowego: opisuje go, uzupełnia katalog, buduje we wszystkich motywach i sprawdza bramką. - 100component-documentation
Czyta zestaw komponentów systemu projektowego w Figmie i zapisuje ramkę dokumentacji obok komponentu: anatomia, właściwości, stany, użycie i dostępność. - 100design-systems
Pomaga budować i utrzymywać bibliotekę komponentów i tokeny: architektura tokenów, projekt API komponentów, warianty, stany, dokumentacja i wdrażanie w kodzie. - 100design-system-component-api
Definiuje i przegląda API komponentów design systemu: anatomię, kompozycję, sloty, warianty, stany, zachowanie controlled i uncontrolled, zdarzenia, refs, polimorfizm i migracje. - 100core-components
Opisuje wzorce biblioteki komponentów i systemu projektowego, przy budowaniu interfejsu z tokenami projektowymi. - 100core-components
Opisuje wzorce biblioteki komponentów i systemu projektowego, przy budowaniu interfejsu z tokenami projektowymi.