flutter-engineer

Use when working on Flutter/Dart projects at any complexity level — architecture decisions, state management, UI/rendering, navigation, performance, security, testing, observability, CI/CD, offline-first, monorepo, platform integration, code review, or debugging. Also use when Flutter tasks span multiple domains and one integrated decision is needed.

Lead authority for Flutter accessibility. Use when implementing screen reader support, semantics tree, focus traversal, contrast validation, reduced motion, touch targets, or keyboard navigation for any Flutter app targeting any platform.

Lead authority for Flutter app architecture decisions. Use when structuring a new project, refactoring package/module boundaries, choosing architecture style, resolving dependency violations, or designing migration paths from legacy codebases.

Lead authority for Flutter build and release engineering. Use for go/no-go decisions, build flavor configuration, signing, obfuscation, store submission, rollback planning, or defining release gates for production deployments.

Lead authority for Flutter CI/CD pipelines. Use when setting up GitHub Actions, Melos scripts, Fastlane automations, coverage gates, build flavors, obfuscation, golden test CI, Patrol CI, or store deployment pipelines.

Lead authority for Flutter code review and tech debt assessment. Use when reviewing PRs, auditing codebases, prioritizing refactoring, or synthesizing findings across architecture, security, performance, and testing domains.

Lead authority for Flutter debugging and root-cause analysis. Use when investigating crashes, ANRs, jank, layout overflow, memory leaks, isolate failures, async deadlocks, plugin failures, or release-only bugs. Returns ranked hypotheses with reproduction plans.

Lead authority for Flutter internationalization and localization. Use when setting up ARB files, implementing pluralization, RTL layout support, locale-aware formatting, typed translations with slang, or adding new locales to existing apps.

Lead authority for Flutter monorepo architecture. Use when designing Melos workspaces, package-first architecture, federated plugins, shared packages, dependency governance, or managing multi-app Flutter monorepos.

Lead authority for Flutter navigation and routing. Use when implementing go_router, deep links, auth guards, shell routes, nested navigation, or migrating from Navigator.push/pushNamed to declarative routing.

Lead authority for Flutter networking. Use when designing HTTP client architecture, implementing Dio interceptors, retry/backoff logic, auth token refresh, caching, optimistic updates, or offline sync networking layer.

Lead authority for Flutter observability. Use when implementing crash reporting, structured logging, performance monitoring, distributed tracing, analytics governance, feature flags, or privacy-safe telemetry.

Lead authority for offline-first Flutter architecture. Use when designing local-first apps, sync engines, conflict resolution, optimistic UI, retry queues, background sync, or mission-critical apps requiring reliability without connectivity.

Lead authority for Flutter runtime performance. Use when diagnosing jank, memory leaks, excessive rebuilds, slow startup, GC pressure, frame budget violations, or requesting performance optimization plans.

Lead authority for Flutter platform integration. Use when implementing platform channels, Method/Event channels, Dart FFI, AndroidView/UiKitView, federated plugins, native permissions, background execution, or bridging native SDKs to Flutter.

Lead authority for Flutter rendering pipeline internals. Use when diagnosing shader jank, raster thread overload, Impeller migration, layer tree optimization, complex animation performance, or understanding the Flutter engine render path.

Global critical override authority for Flutter security. Use whenever credentials, tokens, PII, secure storage, SSL pinning, obfuscation, root detection, or sensitive data handling is in scope. Can override convenience, performance, and UX.

Lead authority for state management selection, implementation, and rebuild optimization. Use when choosing between Riverpod/Bloc/Signals, designing provider trees, debugging rebuild storms, or migrating from legacy state solutions.

Lead authority for Flutter local storage decisions. Use when choosing between Drift, Isar, Hive CE, flutter_secure_storage, shared_preferences, or designing database schemas, migrations, and encrypted storage.

Lead authority for Flutter testing strategy. Use when defining test pyramids, implementing unit/widget/golden/E2E tests, recovering from flaky suites, selecting tools (mocktail, Alchemist, Patrol), or establishing coverage gates.

Lead authority for Flutter UI patterns, widget composition, theming, design systems, adaptive layouts, and accessibility-ready widget construction. Use when designing widget hierarchies, Material 3 theming, responsive/adaptive layouts, or custom widgets.