This skill helps a coding agent answer one question about a game idea, usually whether a mechanic is fun. It writes a short brief with a core verb, keep and kill signals and a timebox, then builds a greybox with a debug HUD in a folder the main game never imports.
The user plays it without coaching and reports back, and the agent records a keep, kill or retune decision in the brief. A keep means a rewrite in the real project, not a copy of the prototype code.
What You Get
- A BRIEF.md template with question, core verb, throwaway flag, timebox, keep signal, kill signal and result
- A pseudocode shape where only the core mechanic is real and tuning values sit as named constants
- Written keep, kill and retune rules that rest on observable playtest signals
- A verify list covering launch, a full loop, the debug HUD, containment in the prototype folder and the recorded result
- A gotcha list on polishing too early, missing kill criteria and prototypes that grow into the product
Common Use Cases
- Testing whether a dash or grapple mechanic feels good
- Deciding whether an idea deserves production time
- Retuning one timing value and replaying
- Keeping experiments out of the shipping codebase
What Makes It Unique
The deliverable is a written decision, and the skill requires the kill signal to be fixed before anyone is attached to the code. It asks the user to hand the build to a player with no explanation and report whether the verb was used unprompted within about 30 seconds, so the agent’s own play does not decide the result.
Under The Hood
The agent loads the SKILL.md only; it has no scripts or references. It writes BRIEF.md and the prototype code under a prototypes folder, launches the prototype from the command line or a local web server on localhost, and may drive it with scripted input. It runs git status or searches imports to confirm nothing outside the prototype folder changed. It does not call outside services.