Build UI with shadcn/ui components first, including chart patterns from shadcn/ui charts guidance. Use CLI-driven component generation and consistent design tokens.
Instalação
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Build UI with shadcn/ui components first, including chart patterns from shadcn/ui charts guidance. Use CLI-driven component generation and consistent design tokens.
Treat DESIGN.md in the repo root as the design authority when it exists.
Prefer existing src/components/ui/* components before custom primitives.
If a component is missing, add it via shadcn CLI instead of rebuilding behavior manually.
Keep styling within existing project tokens and component variants; do not drift back to generic shadcn defaults when DESIGN.md specifies Chai tokens.
If the product exposes theme choices, preserve the Light, Dark, Chai, System distinction from DESIGN.md; never treat Chai as the automatic dark-system result.
For charts, use shadcn chart patterns (with Recharts) and style them with the restrained warm palette and table-vs-chart guidance from DESIGN.md.
Use accessible defaults (labels, focus states, keyboard support) from shadcn components.
Recommended Workflow
Check if required component already exists in src/components/ui.
If missing, add via shadcn registry/CLI.
Compose screens using shadcn primitives (Card, Button, Input, Select, etc.).
For data visualization, use shadcn charts structure and avoid ad-hoc chart wrappers.
Match chart color, border, hover, and annotation choices to DESIGN.md, especially the rule that orange is highlight-only.
Common Checks
No duplicate custom button/input/select implementations.
Dialogs, popovers, and menus are built with shadcn primitives.
Charts use consistent spacing, legends, and axis labels.