flutter-designlisted

# Flutter Design Design with evidence. Do not jump from a vague request to widget code. ## Workflow 1. Inspect `pubspec.yaml`, Flutter/Dart versions, app structure, theme, routing, state management, reusable widgets, tests, and current git state. 2. Identify the product, primary user, critical action, platform mix, content hierarchy, constraints, and measurable success condition. 3. Classify the work and invoke the smallest useful specialist set: - Existing-interface diagnosis: use `$flutter-audit`. - Tokens, themes, or component contracts: use `$flutter-design-system`. - Approved UI implementation: use `$flutter-implementation`. - Transition or interaction motion: use `$flutter-motion`. - Accessibility, text scaling, keyboard, or RTL: use `$flutter-accessibility`. - Rendered review or golden tests: use `$flutter-visual-qa`. 4. Before implementation, record one explicit visual direction: type character, density, palette behavior, geometry, imagery, and motion character. Read `references/visual-direction.md` and `references/anti-slop.md`. 5. Enumerate data and interaction states: initial, loading, empty, populated, partial, error, offline, disabled, destructive confirmation, and success as applicable. For multi-domain dashboards or connected tools, read `references/connected-product-workflows.md` and define the connective model before arranging regions. 6. Define acceptance criteria for compact and expanded layouts, themes, text scaling, and critical in