/startGetting started
Studio overview and command navigation
Flutter + Flame game production
Describe a game.
Get a project that runs.
Flame Studio drives an agent through the whole loop — design document, assets, Flutter and Flame source, tests, and a compiled build it launches to check that the thing actually boots. You get the source and a preview you can play, not a description of one.
- Standard Flutter + Flame source
- Every build is run before you see it
- No proprietary runtime
bootworkspace container ready
runwriting lib/main.dart
runwriting lib/components/player.dart
runresolving flame ^1.18.0
webflutter build web --release
webruntime check passed
collectpreview published
A loop that keeps the evidence attached.
Each pass leaves the source, the logs, the runtime check and the preview together, so you are judging the actual game rather than a report about it.
- 01
Write the brief
Genre, core mechanic, theme, and what a single round should feel like. The studio turns that into a design document before it writes any code.
- 02
It builds in a real workspace
An isolated container with Flutter, the Flame engine and the agent CLI. Assets, source, screens and tests are produced together, not stitched from snippets.
- 03
It runs what it wrote
Every build is compiled and launched headlessly before you see it. A build that does not boot does not reach the preview pane.
- 04
You iterate with skills
Add a mechanic, audit the UI for overflow errors, profile a frame, or package a release. Each skill acts on the existing project rather than starting over.
32 skills, and none of them reset your project.
Every skill acts on the snapshot the last run produced. The list below is read directly from the studio's own catalogue.
/brainstormBrainstorm
Interactive game concept generation
/auto-ideaAuto idea
Instant concept generation with no questions
What you see is what you own.
A successful run produces a normal Flutter project. Nothing about it depends on this service once you have downloaded it.
A standard Flutter project
lib/, pubspec.yaml, assets/, test/. Anyone on your team can open it in their editor and keep working without learning anything about this tool.
Evidence attached to each build
Build logs, runtime checks and the preview stay linked to the run that produced them, so you can tell what changed and whether it worked.
Nothing proprietary in the output
No runtime to license, no SDK to depend on. Download the source and the packaged build; the project outlives your use of the studio.
Start with one mechanic.
Describe the smallest version of the game you want and iterate from the build it gives you.