make-game

Orchestrates end-to-end game development from brainstorm through export by delegating to specialist skills.

66|4|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/SummerEngine/summer --skill make-game-summerengine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: make-game
Source: https://github.com/SummerEngine/summer/tree/main/library/skills/make-game
Command: npx skills add https://github.com/SummerEngine/summer --skill make-game-summerengine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building a complete game from a vague idea often stalls because agents improvise without structure, producing half-finished prototypes. This Skill provides a guided eight-phase pipeline — brainstorm, plan, scaffold, build, layer, polish, verify, ship — with checkpoints between every phase so scope stays controlled and each mechanic is verified before the next begins. ## Core Features & Use Cases - Phased orchestration: Runs brainstorm-game, new-project, design-mechanic, art-direction, game-feel, and export-and-ship in the correct order with explicit handoffs. - Persistent artifacts: Produces .summer/GameSoul.md, .summer/build-plan.md, art and audio bibles, plus one GDScript file per mechanic. - Verification gates: Requires summer_play and clean summer_get_diagnostics after every mechanic before continuing, preventing compounding bugs. - Use Case: A user says "make me a 3D platformer." The Skill brainstorms a one-page brief, writes a build plan with three core mechanics, scaffolds the project, implements movement, jumping, and a win condition one at a time, then layers art, audio, and polish before export. ## Quick Start Tell your agent "make me a game" and it will run this pipeline starting with a brainstorm to capture your idea in a one-page brief.

Frequently Asked Questions about make-game

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a complete game with an AI agent?

Say "make me a game" and this orchestration skill runs an eight-phase pipeline: brainstorm, plan, scaffold, build mechanics one at a time, add art and audio, polish, verify, and ship. Each phase ends with a checkpoint where you confirm scope before continuing.

What files does the make-game pipeline produce?

A full run produces a Summer Engine project with project.godot, a playable main.tscn scene, one GDScript file per mechanic, and planning documents in .summer/ including GameSoul.md, build-plan.md, art-bible.md, and audio-bible.md.

When should I not use the make-game orchestrator?

Skip it for narrow requests like fixing a bug or adding a single feature — use the specific specialist skill instead. Also skip it if you already have a working scaffold; start at the relevant phase rather than re-running the whole pipeline.

Does the pipeline verify the game actually works?

Yes. After every mechanic it runs summer_play and checks summer_get_diagnostics, refusing to stack a new mechanic on a broken one. A final QA pass plays from the main scene through the win condition before shipping.

Can I use a template instead of building from scratch?

Yes. If you want a template, the pipeline runs browse-templates during the scaffold phase instead of new-project. You can also cut polish or shipping phases if the brief is a jam or prototype rather than a release.