Flutter UI Audit

Diagnose before prescribing. Keep audit work read-only unless the user requests changes.

Inspect

1. Read the screen, related state, navigation, theme, shared widgets, and tests.
2. Run the app or inspect screenshots when available. Record viewport, theme, locale, and state for each observation.
3. Evaluate:
   • product goal and primary action;
   • hierarchy, grouping, scan order, density, typography, color, and surface use;
   • navigation, forms, feedback, destructive actions, and recovery;
   • loading, empty, partial, error, offline, and success states;
   • compact and expanded layouts;
   • semantics, focus, text scaling, contrast, touch targets, RTL, and reduced motion;
   • widget boundaries, hard-coded dimensions, rebuild scope, and theme consistency.
4. Read references/anti-slop.md, references/layout-and-density.md, and references/visual-qa.md for applicable checks. For multi-domain surfaces, also read references/connected-product-workflows.md and verify that the connection is more than adjacent cards.