flutter-engineering

Flutter Engineering

Baseline Flutter engineering for HeyEddi apps. Detects which stacks apply and adds the correct tooling: Vue projects should use @project-engineering instead.

Subagents (default)

Delegate scaffold/audit/test scripts to Task shell; repo discovery to explore. Main chat picks stack from audit JSON. See reference/subagents.md.

Stacks

Stack	When	Tooling added
Flutter	Mobile / web frontend	pubspec.yaml, Riverpod, go_router, Material 3, widget tests
FastAPI	REST API backend	backend/, pytest, openapi.json, uvicorn on 8090
Firebase	Firestore / Auth	firebase.json, rules, emulators

Declare intent in .heyeddi/stack.json:

{
  "frontend": "flutter",
  "backends": ["fastapi"],
  "web_port": 8085,
  "api_port": 8090
}

Or "backends": ["firebase"] or ["fastapi", "firebase"].

Workflow

1. Prefs gate (always-on hard): @heyeddi-setup verify_setup --check before git/CI/commit assumptions; incomplete → run setup until pass.
2. audit_scaffold: per-layer JSON (flutter / fastapi / firebase).
3. scaffold_stack --stack auto: fills gaps (flutter, fastapi, firebase, or full).
4. ensure_flutter + ensure_python (via @project-engineering) as needed.
5. dev_server_info: Flutter web :8085, API :8090, Firebase emulators :4000.
6. Plan gate (always-on): @engineering-excellence check_engineering_plan --check before feature code.
7. Implement features (@design-handoff-flutter, @flutter-patterns, @dart-type-bridger).
8. run_tests + run_backend_tests + verify_build.
9. Change gate (always-on): audit_engineering --check (errors fail; warns advisory).

Local dev servers

Stack	Command	URL
Flutter web	flutter run -d web-server --web-port=8085 --web-hostname=127.0.0.1	http://127.0.0.1:8085
Flutter mobile	flutter run	device / emulator
FastAPI	cd backend && poetry run uvicorn app.main:app --reload --port 8090	http://127.0.0.1:8090/docs
Firebase	firebase emulators:start	http://localhost:4000

Set FLUTTER_WEB_URL (or DEV_SERVER_URL) for @visual-auditor when auditing Flutter web.

References

• reference/dev-server.md: Flutter web + mobile
• reference/fastapi-client.md: Dio + OpenAPI types
• reference/firebase-client.md: firebase_core + Firestore
• reference/heyeddi-handoff.md: chain @design-handoff-flutter

Related skills

• @dart-type-bridger: OpenAPI / Firestore → Dart models
• @flutter-patterns: repositories, Riverpod providers, auth
• @design-handoff-flutter: screenshot → Material widgets
• @project-engineering: shared FastAPI/Firebase scaffolds (invoked by scaffold_stack)

When the task is complete: suggest next skills

When you have finished the user's request for this skill (not after every tool call or subagent phase), suggest what to run next:

1. Run:

   python .agents/skills/heyeddi/scripts/suggest_next_skill.py --current-skill flutter-engineering --project-root .
   

   Add --route /path if you worked a specific route.

2. Include the script's ### Next step block in your final reply. The user copies the Prompt line into chat (e.g. @heyeddi-design craft /settings).

Pass --mode shape (or craft, audit, etc.) when you know which sub-command just finished.

See @heyeddi → reference/next-skill-handoff.md.