How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/c3sc0-v4113/scaffold --skill shadcn-component-boundariesBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
shadcn Component Boundaries
Activation Contract
Load this skill when creating, moving, wrapping, or reviewing UI components in a project that uses shadcn.
Hard Rules
- Resolve paths from
components.json(itsaliasesforcomponentsandui) or the installed shadcn skill's project-context command. Never assumecomponents/versussrc/components/. - Reserve the resolved
uidirectory for registry-managed primitives installed from shadcn or compatible registries. - Never place product-owned wrappers, composites, sections, domain components, or feature behavior in the
uidirectory. - Put reusable product-owned components under
common/in the resolved components directory. - Put feature-owned components in a named feature folder or colocate them with that feature.
- Compose: wrap a registry primitive from
common/or a feature folder instead of adding product behavior to the primitive. - Keep dependencies one-way: feature → common → ui. The
uidirectory never imports fromcommonor feature folders. - Use semantic tokens from the global stylesheet. Treat tokens as quarks and registry primitives as atoms; do not force molecule or organism names into paths.
- When
@shadcn/lintis configured,shadcn/no-restyleenforces theuiboundary: call sites may pass layout classes throughclassName, but look comes from variants and sizes. Add a variant to the primitive instead of restyling at the call site.
Decision Gates
| Component ownership | Destination |
|---|---|
| shadcn or compatible registry primitive | resolved ui directory |
| reusable product-owned component | <components>/common/ |
| feature-specific component | <components>/<feature>/ or feature colocation |
| route or page composition | framework route/page directory |
| theme token | global stylesheet variables |
Execution Steps
- Read
components.jsonand resolve thecomponentsanduialiases to directories. - Search installed primitives before creating custom markup.
- Classify ownership and reuse scope with the table above.
- Place the component; see references/placement-examples.md for edge cases.
- Verify no product-owned file entered
uiand no reverse import was introduced.
Output Contract
State the ownership classification and final path for every component created or moved, and confirm the dependency direction holds.
References
- references/placement-examples.md — worked placement decisions.
