What problem does it solve? Flutter apps without a token system scatter raw hex colors, shadows, and durations across widgets, making dark mode, contrast compliance, and reskinning error-prone. This Skill pins every Daybreak design value into lib/theme/ as a single-source primitive pool plus typed ThemeExtension slots, so widgets never hardcode a color, shadow, gradient, or duration. ## Core Features & Use Cases - Two-tier token architecture: A primitives.dart file (the only file allowed raw Color values, named by hue family + CIE L*) feeding DaybreakColors, DaybreakShapes, DaybreakElevation, and DaybreakMotion ThemeExtensions with copyWith, lerp, and an asserting of(context). - Hand-authored light and dark ColorSchemes: No ColorScheme.fromSeed, no dynamic_color, no google_fonts; outline maps to borderStrong so controls keep visible boundaries, and #F97350 primary is enforced as fill-only (2.76:1) with primaryDeep for text. - Contrast budget gate: Nineteen measured foreground/background pairs in both themes, verified by a unit test using the WCAG relative-luminance formula, with documented decorative-only carve-outs. - Use Case: When adding a new screen or reviewing a widget that renders a hex, BoxShadow, LinearGradient, or Duration, apply this Skill to route every value through a named slot, keep the sunrise gradient RTL-safe via AlignmentDirectional, and land any new token with its contrast-budget row and test in the same commit. ## Quick Start Ask the AI to apply the daybreak-tokens rules while editing a file under lib/theme/ or building a widget that needs a Daybreak color, radius, shadow, gradient, or duration.
