Iron Law: Never use raw color hex values, spacing literals, or inline TextStyles — always reference design tokens; run /lint-design-system before any UI PR.

Iron Law 2 (token SSOT): Each token family (AppSpacing, AppRadius, AppSize, AppOpacity, AppShadows) has exactly ONE canonical scale. Never introduce a parallel "legacy" scale alongside the canonical one (e.g. a numeric space1..space16 series next to a t-shirt xs..xxl series). Migrate callers and delete the old scale in one PR — never use @Deprecated to defer the migration.

UI Standards - Design Tokens & Patterns

Design token system and accessibility patterns for Flutter applications.

When to use: Auditing UI compliance, implementing spacing/radius/size tokens, theme usage, accessibility, or responsive layouts.

Process:

1. Identify domain from user request
2. Load reference:
   • Design tokens, theme colors, typography, responsive layouts → Read reference/ui-design-tokens.md
   • Accessibility, semantics, focus management, reduced motion → Read reference/ui-accessibility-patterns.md
3. Apply patterns using loaded reference
4. Verify: No hardcoded colors, all touch targets >= 48px, semantic widgets on interactive elements