flutter-flame-harness

English | 한국어

A Claude Code plugin that takes a Flutter/Flame game from raw idea all the way to the app stores. The harness orchestrates a structured pipeline of skills — research, planning, design, contract negotiation, and a generator–evaluator build loop — so every stage produces a verified, hand-off-ready artifact before the next one begins.

Why

AI coding tools usually skip the boring parts — they code before pinning requirements, skip tests, and stop while it's half-done. This harness delegates the process, not just the code: guardrails → plan → a generator↔evaluator build loop with a skeptical QA that runs the game before judging → human review. And it isn't theory — the fixes earned shipping real Flame games (audio pooling, haptics, app-lifecycle, performance, store/build pitfalls) are baked in, so a generated game doesn't re-walk the same traps.

Games

A mix of games I've shipped and games built with this harness — Flutter + Flame.

Portrait

Landscape

Phases

Phase A (complete): research → plan → design → contract → generator ↔ evaluator → playable game

The generator and evaluator negotiate completion criteria before any code is written, then build the Flutter/Flame project in three sub-phases (scaffold → API wiring → UI polish), with the evaluator gating each hand-off.

See docs/SMOKE-TEST.md for the full manual smoke-test procedure.

Phase B (complete): admob, build, screenshot, submit, retro

Automates AdMob integration, release builds (Android + iOS), App Store / Play Store screenshots, submission, and a post-launch retrospective.

See docs/SMOKE-TEST-phaseB.md for the full manual deploy dry-run procedure.

Install

/plugin marketplace add tjdrhs90/flutter-flame-harness
/plugin install flutter-flame-harness@flutter-flame-harness

Updating

The plugin is copied into a cache at install time, so editing the source doesn't take effect until you re-sync. After pulling new commits (the version bumps each release):

/plugin marketplace update flutter-flame-harness   # re-sync the latest version into the cache
/reload-plugins                                     # apply it in the current session

Confirm the new version in /plugin. If a change doesn't appear, reinstall: