Individual skill
game-production-stages
Plan and route a game or playable 3D demo through art direction, sandbox, environment, character, assembly, atmosphere, gameplay, and shipping. Use at the start of any game-shaped project or when replanning one mid-flight. Coordinates reference-pack-authority, asset-judge-loop, 3d-asset-quality, and verify-by-playing, with a playable placeholder sandbox required before production assets.
skills/game-production-stages/SKILL.md
Source commit d907ca964dd2b86b973eadb165f7413a971bb131
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 13
- Repository last updated
- Sep 1, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- 3d Repository topic
- agent-skills Repository topic
- ai-agents Repository topic
- blender Repository topic
- claude-code Repository topic
- game-development Repository topic
- remakebench Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 7,420 bytes
Read excerpt
# Stages, gates, and which skill owns each
This is a routing document. The craft lives in the specialist skills; this map exists so they
load at the right moments instead of by trigger luck, and so ordering mistakes that have each
cost real projects real rounds are not re-made.
## The map
| stage | work | exit gate | loads |
|---|---|---|---|
| **0 — Art direction** | Hero image, site plan, section, elevations, materials sheet, character sheet — generated, pinned, hashed | Operator approves the hero (cheapest rejection point) + **congruence pass done, spec-as-text written** | `reference-pack-authority` |
| **1 — Playable sandbox** | Template adopted WHOLE if one is used; capsule player; greybox world built from the layout's own collision data; core loop playable | **`verify-by-playing`** — real input, route traversed, camera owned | `verify-by-playing` |
| **2a ∥ Environment** | Batch assets, coherent PBR surfaces, layout geometry | Judge passes the batch | `asset-judge-loop`, `3d-asset-quality` |
| **2b ∥ Character** | Model, rig, clips (generate high-poly → bake route) | Rig proven by MEASURED joint motion; sockets by read-back through the actual loader | `3d-asset-quality` |