flutter-ui-designlisted

# Flutter UI Design Create coherent, platform-aware Flutter interfaces that feel authored for the product rather than assembled from framework defaults. ## Scope Own art direction, visual ambition, hierarchy, composition, semantic tokens, typography, color, surfaces, shape, state presentation, and rendered visual review. Route implementation structure, reusable widget APIs, forms, and UI state ownership to `flutter-ui-patterns`. Route constraint mechanics to `flutter-responsive-layout`, motion implementation to `flutter-animation`, advanced blur, refraction, shader, or custom optical rendering to `flutter-visual-effects`, accessibility compliance to `flutter-accessibility`, and navigation behavior to `flutter-navigation`. ## Preflight Before proposing a redesign: 1. Inspect `pubspec.yaml`, supported platforms, nearby screens, assets, fonts, and any supplied references. 2. Find existing `ThemeData`, `ColorScheme`, `TextTheme`, component themes, `ThemeExtension`s, and design-system widgets. 3. Preserve the established brand and component vocabulary unless the request explicitly authorizes a redesign. 4. Inspect the current screen at a representative viewport when the project is runnable. Source alone is insufficient evidence of its visual baseline. 5. Do not add a UI package, font, icon set, or competing theme merely because it is familiar. ## Design workflow 1. State the screen's primary user task and the visual failure in observable terms. 2. Classify the assignment