A game-production baseline for your AI agent
Make your game.
Keep your bearings.
Give your coding agent a shared playbook for planning, building and checking your game. Keep the decisions, the context and the final say in your project.
Works alongside Codex, Claude, Cursor and compatible coding agents.
Hephaera A little more direction. A lot less starting over.WHAT IT IS
A shared playbook.
Right in your repository.
Hephaera lives in a .hephaera/ folder inside your game project. It gives your agent reusable instructions, specialist workflows and a place to keep project context between sessions.
You describe the result you want. Together, you work out a plan, use the right tools and check what actually happened. You still choose the engine, approve the work and review the result.
Take the short tourFROM IDEA TO REVIEW
Start with a conversation.
You don’t need to memorize a list of commands to ask for useful work.
“Help me make a small playable prototype. Start with movement, one enemy and a clear HUD. Show me a plan before changing files.”Walk through your first session
- 01
Talk it through
Explain what the player should experience and what matters to you.
- 02
Make a plan
Choose a manageable scope, the right tools and a way to judge the result.
- 03
Build and check
Work through the change, with tests, playthroughs and evidence that fit the task.
- 04
Review and decide
Keep what works. Revise what doesn’t. Approve delivery when it’s ready.
Set the direction
Choose your engine, project structure and visual style.
02 / DEVELOPMENTKeep the work connected
Plan features, fix bugs and carry useful context into the next session.
03 / PRODUCTIONMake room for the assets
Turn approved floor plans into buildings and schematics into models with separate moving parts.
04 / SOUNDLet audio have its own lane
Use separate workflows for effects and ambience, music, and speech.
GET STARTED
One folder.
A better starting point.
Versioned npm and NuGet setup installs the baseline and creates your project scaffold automatically. Select security patch 5.2.1 after confirming publication; it retains building models, mechanical assemblies and reusable game effects. Both package routes use authenticated GitHub Packages.
Package setup, prerequisites and manual fallbacknpm exec --yes --registry=https://npm.pkg.github.com --package=@timothymeadows/hephaera@5.2.1 -- hephaera install --project .Authenticate for the GitHub feed and confirm the exact release is published before setup. The guide covers npm first, NuGet next, then manual clone/submodule options. Public registries are deferred; native tools and models remain separate.
TWO WAYS TO FIND YOUR WAY