flutter-flame-harness
Reduces game development cycle time by providing pre-built scaffolding for Flutter/Flame projects, lowering engineering effort and time-to-market for mobile …
A Claude Code plugin that takes a Flutter/Flame game from raw idea to app-store submission. Phase A runs a structured pipeline — market research, planning, design, and a generator-evaluator build loop where a skeptical QA gate runs the game before approving it. Phase B automates AdMob integration, release builds for Android and iOS, store screenshots, and store submission. Fixes learned from shipping real Flame games (audio pooling, haptics, app lifecycle, store/build pitfalls) are baked in.
- Generate boilerplate code structure for a new Flutter Flame game project
- Automate setup of game physics, collision detection, and sprite management systems
- Build game assets pipeline from design files to deployable app store submission
Reduces game development cycle time by providing pre-built scaffolding for Flutter/Flame projects, lowering engineering effort and time-to-market for mobile game initiatives.
Mobile game development teams using Flutter seeking faster project initialization and standardized architecture.
https://github.com/tjdrhs90/flutter-flame-harness
By tjdrhs90
How to Get It
git clone https://github.com/tjdrhs90/flutter-flame-harness — then in Claude Code: /plugin marketplace add <path-to>/flutter-flame-harness and /plugin install flutter-flame-harness
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
After installing, paste this into Claude:
Help me generate boilerplate code structure for a new Flutter Flame game project
Trust Signals Auto-scanned
Community Pulse New
No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 33 GitHub stars; contributors unknown; last commit 0d ago; license MIT.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 33 GitHub stars; contributors unknown; last commit 0d ago; license MIT.