Flutter Design System

Build a semantic system that serves the product; do not impose a generic component library.

Process

1. Inventory existing ThemeData, extensions, constants, text styles, colors, radii, spacing, shared widgets, and package dependencies.
2. Identify visual language and product constraints. Read references/visual-direction.md, references/typography-and-color.md, and references/layout-and-density.md.
3. Define semantic roles before values:
   • surfaces, content, borders, accents, status, and interaction states;
   • display, title, body, label, and numeric typography roles;
   • spacing, radius, elevation, icon size, control height, and motion roles. For products spanning multiple domains, read references/connected-product-workflows.md; give domains semantic accents without fragmenting the shared system.
4. Map roles into ColorScheme, TextTheme, component themes, and narrowly scoped ThemeExtensions.
5. Support light/dark contrast and platform behavior without duplicating raw values throughout widgets.
6. Define component contracts for behavior and states, not only appearance.
7. Migrate incrementally. Avoid replacing mature project primitives unless the new system resolves a documented issue.

Rules