Flutter implementation

Use when building or modifying in-app Dart code. Follow .cursor/rules/architecture.mdc, state-management.mdc, and design-system.mdc.

Before coding

1. Read docs/ARCHITECTURE.md and check for similar existing code
2. List files to create/modify (5–10 lines) — confirm with user if scope is unclear
3. For new feature slices, prefer mason make feature from bricks/feature/, then adapt the generated files
4. Match folder layout: features/<feature>/{data,domain?,presentation}/

Stack context

• provider + ChangeNotifier ViewModels — no Riverpod
• go_router, freezed for models and sealed UI/error states
• Design tokens from lib/design_system/tokens/
• l10n for user-visible strings
• Repositories return Future<Result<T, Failure>>; inject via MultiProvider

Implementation checklist

Structure

• One screen / ViewModel / repository per file
• ViewModels in presentation/view_models/
• Register new repos/services/ViewModels in app/dependencies.dart
• data/services/ per data source; repositories above services

ViewModels

• Extend ChangeNotifier; private repository fields
• Explicit loading/error/data fields or sealed UI state
• notifyListeners() after state changes; clean up in dispose()

Views

• context.watch<ViewModel>() to rebuild; context.read<ViewModel>() in callbacks
• No business logic in build
• Semantics on interactive widgets; touch ≥48dp (Material) / ≥44pt (Cupertino)
• ListView.builder for long lists; Selector to narrow rebuilds

Data

• No Supabase.instance.client in widgets or ViewModels accessing globals
• Map errors through core/errors/error_mapper.dart

Routing

• GoRouter in app/router.dart
• Inject ViewModels/repos in route builder via context.read()
• Auth: refreshListenable on auth ViewModel (ChangeNotifier)
• context.go() / context.push() — not Navigator.push

Tests to add (required)

Per .cursor/rules/testing.mdc — all rows apply; no skipping.

Before finishing

• Run flutter analyze --fatal-infos and flutter test
• Update docs/DECISIONS.md if architecture changed
• Use review-code skill when user requests review

Output format

## Files touched
- ...

## Tests added
- ...

## Open questions
- ...

Never

• Use Riverpod or flutter_riverpod
• Ship code without required tests (testing.mdc)
• Add dependencies without user approval + docs/DECISIONS.md
• Hardcode secrets outside core/config/env.dart
• Hardcode user-visible strings outside l10n
• Let views call repositories directly