UI Primitives Shadcn Lucide

For substantial web work, reuse the scoped web contract when available; it replaces duplicated policy here. Match the requested scope and existing decisions; a missing optional sibling does not block this local procedure.

Overview

Use primitives as structure, not as the visual identity. Accessible primitives save time, but default styling is not design direction.

Workflow

1. Identify the requested component or architecture outcome, affected files and existing decisions; reuse established content and visual direction.
2. Inspect the project before editing when code exists.
3. Apply this skill's specific rules from references/ui-primitives-shadcn-lucide-guide.md.
4. Explain material implementation choices while continuing authorized work.
5. Implement when requested, inspect affected output, fix observed defects, and run the smallest decisive relevant checks.

Reference

Read references/ui-primitives-shadcn-lucide-guide.md when this skill triggers for a concrete website build, redesign, visual review, or implementation plan.

Ownership

Own customization of installed shadcn source and Lucide visual states. Preserve the selected underlying primitive family; use radix-accessible-primitives only for actual Radix mechanics and react-accessible-components for semantic requirements. Do not reinstall or replace primitives for a styling change.