Intent UI — Component & Style Enforcer

rules/

Rules

• Styling Rules — Semantic color tokens, className utilities, variant conventions
• Icons Rules — Heroicons usage, no data-slot, no sizing inside components
• Forms Rules — Form component patterns, TextField, Select, Checkbox, etc.
• Components Rules — Always use Intent UI components instead of raw HTML elements
• CLI Rules — How to search and install missing components from the registry

When reviewing or writing code

1. Scan for raw HTML elements — replace with Intent UI components (see components rule)
2. Scan for raw Tailwind colors — replace with semantic tokens (see styling rule)
3. Check icon usage — no

   data-slot="icon"

   , no sizing inside UI components (see icons rule)
4. Check form patterns — use Intent UI form components correctly (see forms rule)
5. Check imports — ensure components come from

   @/components/ui/

6. Check className utility — must use

   cx

   from

   @/lib/primitive

   , not

   cn

   or

   clsx

7. Missing components — if a needed component doesn't exist in

   src/components/ui/

   , follow the CLI rule to search and install it from the registry