| name | apply-design-system |
| description | Use when building or restyling any page or component. |
Design System Implementation Playbook
Maintain visual consistency and premium aesthetics across the codebase:
-
Read DESIGN.md first:
- Check defined HSL color tokens.
- Do not invent custom inline colors (like
bg-[#ab33ff]). Use Tailwind classes mapped to theme tokens (e.g. bg-primary, text-muted-foreground, border-border).
-
Reuse Existing Primitives:
- Do not rebuild standard components. Use:
<Button> for triggers.
<Card> for layouts.
<FormField> for form inputs.
<DataTable> for listing grids/rows.
<Modal> for alerts and overlays.
<StarRating> for review scores.
useToast for user notices.
-
Consistency & Feel:
- Ensure interactive actions have standard transitions:
transition-all duration-200 hover:scale-[1.01].
- Maintain padding standards (usually
p-6 or p-4 for containers, px-4 py-2 for buttons).
- Ensure dark mode is supported natively via color-scheme properties.