Shadcn Component Boundaries

C3SC0-V4113/Scaffold/skills/shadcn-component-boundaries

by C3SC0-V4113ba1fac59145ed48f727247299ebb09289b87f27bApache-2.03 starsListed Oct 9, 2026Updated Oct 9, 2026Repository updated 3 days ago

Trigger: components/ui, shadcn, component placement, common components, feature components, atomic design. Enforce registry and product component boundaries.

Instructions onlySoftware Development
AI-generated overview

Enforces shadcn component placement boundaries between registry primitives, shared common components, and feature folders.

What it does
This skill provides rules and decision gates for classifying and placing UI components in a project that uses shadcn. It resolves the components and ui directories from components.json, reserves the ui directory for registry-managed primitives, and directs reusable product components to common/ and feature components to feature folders. It also enforces one-way dependencies (feature to common to ui) and reports the ownership classification and final path for each component created or moved.
When to use it
Use it when creating, moving, wrapping, or reviewing UI components in a shadcn-based project. It is intended for decisions about where a component belongs and whether product behavior is leaking into registry primitives.
Requirements
Requires a project using shadcn with a components.json file; optionally uses the installed shadcn skill's project-context command and @shadcn/lint when configured. It ships no scripts, only instructions and a reference document.

shadcn Component Boundaries

Activation Contract

Load this skill when creating, moving, wrapping, or reviewing UI components in a project that uses shadcn.

Hard Rules

  1. Resolve paths from components.json (its aliases for components and ui) or the installed shadcn skill's project-context command. Never assume components/ versus src/components/.
  2. Reserve the resolved ui directory for registry-managed primitives installed from shadcn or compatible registries.
  3. Never place product-owned wrappers, composites, sections, domain components, or feature behavior in the ui directory.
  4. Put reusable product-owned components under common/ in the resolved components directory.
  5. Put feature-owned components in a named feature folder or colocate them with that feature.
  6. Compose: wrap a registry primitive from common/ or a feature folder instead of adding product behavior to the primitive.
  7. Keep dependencies one-way: feature → common → ui. The ui directory never imports from common or feature folders.
  8. 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.
  9. When @shadcn/lint is configured, shadcn/no-restyle enforces the ui boundary: call sites may pass layout classes through className, but look comes from variants and sizes. Add a variant to the primitive instead of restyling at the call site.

Decision Gates

Component ownershipDestination
shadcn or compatible registry primitiveresolved ui directory
reusable product-owned component<components>/common/
feature-specific component<components>/<feature>/ or feature colocation
route or page compositionframework route/page directory
theme tokenglobal stylesheet variables

Execution Steps

  1. Read components.json and resolve the components and ui aliases to directories.
  2. Search installed primitives before creating custom markup.
  3. Classify ownership and reuse scope with the table above.
  4. Place the component; see references/placement-examples.md [blocked] for edge cases.
  5. Verify no product-owned file entered ui and 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 [blocked] — worked placement decisions.

Source and attribution

Source:C3SC0-V4113/Scaffoldinskills/shadcn-component-boundariesat commitba1fac5

License: Apache-2.0

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal