Flutter Design System and Accessibility

When to use

Invoke when adding a design system and accessible component library to a scaffolded Flutter app, hardening accessibility (screen-reader semantics, dynamic text, contrast, touch targets, RTL), wiring the internationalization seam, or building permission-request and accessible auth UIs.

Do not use for: app scaffolding or the ThemeData placeholder itself (use flutter-app-scaffold-and-runtime); navigation topology, route-level layout placement, or auth-gate redirects (use flutter-navigation-and-routing); state management, token logic, or the native permission-request engine (use flutter-state-and-data-fetching); performance budget enforcement (use flutter-performance-and-reliability).

Inputs

Required:

• A scaffolded Flutter app with the app/app.dart ThemeData placeholder and the // TODO(flutter-design-system-and-accessibility) seam.
• Approved mobile-architecture.md, or explicit confirmation that mobile architecture is intentionally deferred.

Optional: