flutter-flame-harness
A Claude Code plugin that takes a Flutter/Flame game from raw idea all the way to the app stores.
Install one, then just prompt in plain English. The FLOW.md fires the right skill at the right moment. No re-orchestration, no babysitting.
Featured
A Claude Code plugin that takes a Flutter/Flame game from raw idea all the way to the app stores.
Orchestrator — bootstrap a Flutter/Flame game pipeline (idea→playable game) and dispatch each phase skill. Use when starting or continuing a flame-harness run.
Phase 7 — analyze the game, decide a rewarded-ad strategy, guide manual AdMob ad-unit creation, and inject google_mobile_ads + ATT/UMP consent code.
Phase 8 — bootstrap signing credentials, generate fastlane config from templates, and build + upload signed IPA (TestFlight) and AAB (internal track).
Phase 4 — propose verifiable completion criteria and mandatory hard gates; reach AGREED (1-pass default, multi-round negotiation in --strict).
Phase 3 — define the Flutter design_tokens.dart spec (palette, typography, spacing), the game's art/visual concept, and the asset/audio sourcing plan.
Phase 6 — skeptical QA. Run the game, watch it, then judge against the contract. Default = functional check; --strict adds quality and edge-case passes.
© 2026 Flowy · Free and open source
Built for Claude Code · Not affiliated with Anthropic