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’s shared robotic owl, in charcoal, steel and goldHephaera A little more direction. A lot less starting over.
Build with the engine you choose
Three.js · Babylon.js · Phaser · Unity · Unreal · Godot

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 tour

FROM IDEA TO REVIEW

Start with a conversation.

You don’t need to memorize a list of commands to ask for useful work.

A first request might sound like this
“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
  1. 01

    Talk it through

    Explain what the player should experience and what matters to you.

  2. 02

    Make a plan

    Choose a manageable scope, the right tools and a way to judge the result.

  3. 03

    Build and check

    Work through the change, with tests, playthroughs and evidence that fit the task.

  4. 04

    Review and decide

    Keep what works. Revise what doesn’t. Approve delivery when it’s ready.

THE WORK AROUND THE GAME

Give each part a clear path.

Build effects around a model action

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 fallback
Authenticated GitHub package setupNode 24 + Git + Bash
npm 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

Guides for doing.
Reference for the details.

Find your next step

Type a few words to find a guide.

Looking for a command or contract? Use the reference wiki