القائمة
Use when implementing or overhauling a CoGames-style game once the target contract is known, including scaffold, registration, mechanics, assets, and variant factoring.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when designing or repairing a CoGames-style game and the main risk is that the rules, map, roles, or play loop do not yet match the real game or prompt closely enough.
Use when creating a new mettagrid game from scratch and you need the design-first workflow that writes the rules contract, checks engine fit, and hands a clean build plan to `cg.game.build-game`.
Use when a CoGames-style game already works visually and mechanically and now needs to be split into a composable variant registry, dependency tree, and optional curriculum tree without regressing the default game.
Use when designing or repairing a CoGames-style game and the main risk is that the rules, map, roles, or play loop do not yet match the real game or prompt closely enough.
Use when a CoGames-style game is mechanically working but still has missing, placeholder, wrongly themed, or non-namespaced art, terrain, or atlas entries.
Use when creating a new mettagrid game from scratch and you need the design-first workflow that writes the rules contract, checks engine fit, and hands a clean build plan to `cg.game.build-game`.
| name | cg.game.build-game |
| description | Use when implementing or overhauling a CoGames-style game once the target contract is known, including scaffold, registration, mechanics, assets, and variant factoring. |
cg.game.build-game is the shared implementation loop for the cg.game suite. Use it once the target game contract is
known: for blank-sheet games after cg.game.new-game, or directly for existing-game fixes and overhauls. For a new
game, this means turning the rules contract into game.py, map.py, tests, a recipe entrypoint, and a playable default
path. The order stays the same: mechanics first, art second, variant factoring last.
Announce at start: "I’m using cg.game.build-game: I’ll lock mechanics first, then generate/namescape assets, then factor the stable game into a variant tree."
cg.game.new-game if the game does not exist yet or the design/engine mapping is still fuzzy.cg.game.build-game if the target loop is already known and the work is implementation or overhaul.cg.game.build-player if the rules are stable and only the player/policy behavior is changing.Lock the contract first. If this is a net-new game, finish cg.game.new-game phase 1 and phase 2 before editing. If
this is an overhaul, derive the same contract from the current game, README/CONTEXT, prompt, and tests.
Run cg.game.core-mechanics. Create or tighten the package scaffold, register the entrypoint, match the real game or
prompt, shrink/fix the map if needed, and get focused tests plus headless/GUI play smokes green.
Run cg.game.generate-assets. Generate or reuse the right visual entities, namespace the outputs to the game, and
prove the atlas/render path is clean.
Run cg.game.variant-tree. Only after the default game works, extract full plus meaningful slices into a
dependency-closed local registry and, if needed, a curriculum tree.
Finish with bop-it discipline. Re-run the smallest relevant test and play/audit suite, lint the touched files, then commit/push/PR with the state of the game and the exact commands that passed.
Uses: cg.game.core-mechanics, cg.game.generate-assets, cg.game.variant-tree, cf.bop-it
Pairs with: cg.game.new-game, pr.summary, pr.check-ci