name: design-system description: Apply design tokens and creative direction consistently autoTrigger: When creating or modifying visual components
Apply Design System
Before creating or modifying any visual component:
- Read
/design-system/DIRECTION.mdfor creative direction - Read
/packages/ui/tokens.tsfor design tokens - Read
/apps/web/styles/globals.cssfor CSS custom properties
Token usage
- Use CSS custom properties (e.g.,
text-text-primary,bg-surface-secondary) - Never hardcode colors — always reference tokens
- Use spacing from tokens via Tailwind classes
- Use the motion curves defined in tokens for animations
Typography hierarchy
- Display:
font-display— for hero headlines - Heading:
font-display— for section headings - Body: default font — for paragraphs
- Tracking: apply tracking classes as defined in tokens
Animation rules
- Always check
prefers-reduced-motionbefore animating - Use GSAP for scroll-driven animations
- Use Motion for component-level animations
- Spring animations preferred over linear/cubic-bezier
- One signature moment per page, not scattered micro-interactions
Anti-patterns (from CLAUDE.md NEVER DO list)
- No Inter/Roboto/Arial
- No purple gradients
- No generic card grids
- No #FFFFFF backgrounds
- No opacity-only hover effects