MaestroFor agentsDesign systemSource

Everything on this site

Every page, and every section of every page. There is no search box: this site ships no JavaScript, and your browser's own find (Ctrl+F, Cmd+F) searches this page, which carries all of it.

Running itSelf-hosted and open source: what Maestro is, how to run it, how to configure it and how to build it.
MaestroA workspace where game designers and their AI agents build the design of a game together: characters, places, missions, progression, story.
License
Design system
What an agent is toldThese are the pages this instance serves to an agent, published so a person can read what their agent was handed.
A worked example: a metroidvaniaA single connected map, abilities that open parts of it, bosses that drop those abilities, and items scattered through rooms.
A worked example: an MMORPGA world with classes and races, a place graph, quest chains that gate each other, talent trees, and reputation with factions.
A worked example: a racing careerA career mode: drivers, cars you buy and upgrade, circuits, races, championships that run over several rounds, and licences that gate what you may enter.
Deciding a game's shapeFour decisions, in the order you actually face them.
NamingKeys are the API.
Auditing a designYou have a game with content in it and a question a listing cannot answer: is this actually playable? A player has to be able to get somewhere, in an order the design admits, and nothing here checks that until somebody asks.
Composing a viewA view is a stored query plus the renderer that draws it.
Joining a game somebody else designedYou have a token and a game you have never seen.
Seeding a gameFilling an empty game, or adding a whole subsystem to one that already has content.
AnalysisFour questions about a game that no listing answers, because each is about the shape of the whole graph rather than about any row in it.
CommentsA game's log, and the one place you and the game's designers write to each other.
DocumentsA document is long prose attached to this game's content: a dialogue script, a zone's lore, the game bible.
ErrorsEvery code below names a different recovery.
FieldsThe six field types are enumerated in skill.md, because you choose between them before anything here matters.
Queries and saved viewsA view is a query document plus a renderer.
The REST surfaceEvery tool is mirrored by a route, and this is where they are.
Reading the surface itselfEvery rule this surface enforces is on the wire before you break it.
The tool surface62 tools.
Maestro skillMaestro records the content design of a game: what a player can be, where they can go, what they can do and what they unlock.