Flutter Engineering
Resolve repository truth
- Read
../../../.github/specs/flutter-engineer.spec.md and relevant feature specifications when present.
- Inspect the actual application path,
pubspec.yaml, analyzer rules, formatter configuration, source patterns, tests, generators, and task automation.
- Treat repository configuration as authoritative when generic guidance differs.
- Confirm requested behavior, acceptance criteria, supported platforms, and privacy or offline constraints.
Load only relevant references
- Architecture and feature boundaries: architecture.md
- Riverpod and state: state-management.md
- Offline-first storage and synchronization: offline-first.md
- Routing and deep links: routing.md
- Localization: localization.md
- Design system and accessibility: design-system.md
- Notifications: notifications.md
- AI provider abstractions: ai-providers.md
- Testing: testing.md
Do not load unrelated references solely because they exist.
Implement a vertical slice
- Place domain rules, data access, application state, and presentation in their established layers.
- Reuse project abstractions before adding new ones.
- Preserve explicit loading, data, empty, and error states.
- Keep external services behind interfaces and inject dependencies through established mechanisms.
- Route user-facing text through localization and use design-system tokens and components.
- Include accessibility semantics, responsive behavior, privacy, and offline degradation when applicable.
- Never hand-edit generated files; run the configured generator.
Test and validate
Add the lowest appropriate tests for domain logic, repositories, providers, widgets, goldens, or user flows. Run dependency synchronization and generation only when required, then formatting, static analysis, focused tests, and repository-mandated checks. Use the task runner when it is the canonical interface.
Review the final diff for generated artifacts, dependency drift, localization coverage, state ownership, error visibility, accessibility, privacy, and unintended cross-feature coupling. Report changed behavior, checks and results, and any blocked validation.
1---2name: flutter-engineering3description: Design, implement, refactor, debug, or test Flutter and Dart application work using repository-aware architecture, state management, storage, routing, localization, design systems, notifications, AI-provider boundaries, code generation, and validation. Use for scoped Flutter feature and maintenance tasks.4---56# Flutter Engineering78## Resolve repository truth9101. Read `../../../.github/specs/flutter-engineer.spec.md` and relevant feature specifications when present.111. Inspect the actual application path, `pubspec.yaml`, analyzer rules, formatter configuration, source patterns, tests, generators, and task automation.121. Treat repository configuration as authoritative when generic guidance differs.131. Confirm requested behavior, acceptance criteria, supported platforms, and privacy or offline constraints.1415## Load only relevant references1617- Architecture and feature boundaries: [architecture.md](references/architecture.md)18- Riverpod and state: [state-management.md](references/state-management.md)19- Offline-first storage and synchronization: [offline-first.md](references/offline-first.md)20- Routing and deep links: [routing.md](references/routing.md)21- Localization: [localization.md](references/localization.md)22- Design system and accessibility: [design-system.md](references/design-system.md)23- Notifications: [notifications.md](references/notifications.md)24- AI provider abstractions: [ai-providers.md](references/ai-providers.md)25- Testing: [testing.md](references/testing.md)2627Do not load unrelated references solely because they exist.2829## Implement a vertical slice30311. Place domain rules, data access, application state, and presentation in their established layers.321. Reuse project abstractions before adding new ones.331. Preserve explicit loading, data, empty, and error states.341. Keep external services behind interfaces and inject dependencies through established mechanisms.351. Route user-facing text through localization and use design-system tokens and components.361. Include accessibility semantics, responsive behavior, privacy, and offline degradation when applicable.371. Never hand-edit generated files; run the configured generator.3839## Test and validate4041Add the lowest appropriate tests for domain logic, repositories, providers, widgets, goldens, or user flows. Run dependency synchronization and generation only when required, then formatting, static analysis, focused tests, and repository-mandated checks. Use the task runner when it is the canonical interface.4243Review the final diff for generated artifacts, dependency drift, localization coverage, state ownership, error visibility, accessibility, privacy, and unintended cross-feature coupling. Report changed behavior, checks and results, and any blocked validation.
egohygiene