woostack-design-system

woostack-design-system

Create a working, project-owned component catalog by inspecting the target repository for compatible controls, catalogs, and design rules, and by sourcing newly needed components from the current upstream shadcn component documentation. This skill ships no templates, component sources, or frozen coverage inventory: the catalog frame, specimens, coverage record, and provenance are created in the target, and every newly needed control comes from the live docs and registry at creation time, never from embedded assets. Build an internal visual catalog showing component variants, states, and interactions; treat component and preview source as the implementation reference, and do not generate code snippets, copy controls, or separate usage-example documentation. This command owns component-system creation; arranging multi-step flows is the separate woostack-design layout standard, unchanged here.

Command and authorization

/woostack-design-system
/woostack-design-system inspect the existing catalog
/woostack-design-system add a date-range specimen
/woostack-design-system repair catalog keyboard navigation
/woostack-design-system update the catalog's typography examples

Inspect first; an undocumented catalog still counts as existing. A component library without a catalog does not prevent creation, but its compatible controls must be reused. Explicit read-only or local-only limits take precedence. Never create branches, commit, push, publish PRs/issues, mutate Projects, initialize Woostack configuration, or migrate product UI automatically.

Inspect and choose placement

Read repository instructions, design rules, manifests, lockfiles, public UI exports and their callers, styles/tokens, existing catalogs and verification commands. Preserve unrelated work. Use bundled implementation patterns and testing guidance; reading these invokes no other workflow and authorizes no implementation.

Apply compatibility to actual imports, props, composition, style setup and dependencies. Choose repository-native catalog placement, not a copied workspace path. Reuse compatible controls and catalogs in specimens and navigation/chrome. Adapt catalog callers to their public APIs; do not rewrite existing components to fit newly created ones. For incompatible or non-React products, use an isolated React catalog whose dependencies and configuration do not alter the product's framework, runtime dependency set or behavior.

If a catalog exists and maintenance was not requested, stop before installation or generation. Report its location, observed coverage, API/style compatibility, provenance, interaction gaps, and concrete scoped repair options. Distinguish inspected facts from unverified runtime behavior.

Create or maintain locally

Follow adaptation and creation. Decide creation from repository inspection, not from shipped assets: none are shipped. Reuse compatible catalogs, controls, tokens, and examples before creating anything new. Before any implementation mutation, disclose the declared coverage user-visibly per agree the coverage: inventory or unambiguous coverage set, focused or exhaustive label, and material exclusions, even when repository evidence supplies the proposal. Repository facts can propose a focused set but are not requester agreement to narrowing; honor an explicit full-coverage request, and ask one focused scope question only when the request and evidence leave a material choice unresolved. When scope is determined, disclose it and proceed within authorization without a questionnaire or approval gate. Record the declared coverage, source provenance, extensions and gaps in a coverage record the target owns. Without design rules, use the neutral shadcn Base UI baseline, not Git Stacks branding or Quiet Workbench styling. Source newly needed controls and examples from the current upstream docs/registry — via the current Base UI-backed shadcn CLI where it fits the target configuration — adapting them to real project APIs; never CLI-overwrite existing UI or initialize over custom setup. Compatible existing primitives are reused, not migrated. Creation may need registry/CLI network access; the resulting catalog has no remote-source requirement at runtime. Resolve only newly selected dependencies from authoritative registries under the bundled dependency guidance.

Do not add a substitute scaffold, generator, or embedded source dump in place of inspecting the repository and sourcing current upstream. Do not overwrite custom components, tokens, examples, rules or unrelated work. Compare before changing existing destinations. Report a conflict and leave the conflicting surface unchanged; complete independent in-scope work without silently substituting a duplicate implementation. Maintenance is not permission to regenerate the catalog or upgrade unrelated dependencies.

Verify and report

Use verification and the target's native commands. Verify real imports, the declared coverage, live specimens, and actual browser behavior; a placeholder catalog, extracted source without live specimens, typecheck alone, or site packaging check is not recreation. Leave no mock controls, dead specimens or unsupported "complete" claims.

Report catalog placement and commands, declared coverage with gaps, source provenance for reused and newly created controls, retained upstream notices, design adaptations, preserved customizations, conflicts, and checks actually observed. Separate deterministic checks, installed-skill/host outcomes and browser evidence. Failed or unrun required checks remain unverified; name the missing prerequisite and do not claim completion. Local verified changes are the endpoint; publication requires a separate user request.