Gsp polished prototype
Skill mike007jd/game-superpowers/skills/gsp-polished-prototype
Use when the target is a coherent, demo-ready prototype rather than a minimal first playable.From its SKILL.md
npx -y skills add mike007jd/game-superpowers --skill gsp-polished-prototypeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.3 KB, 256 tokens by cl100k_base, as published. Nobody here has run it
Game Polished Prototype
Goal
Produce a polished prototype, not just a barely playable vertical slice.
Required quality bar
A valid polished prototype should usually include:
- the requested core loop,
- core requested features in scope,
- a coherent menu / start / retry / pause flow when relevant,
- readable HUD and affordances,
- meaningful feedback and feel,
- clear visual direction,
- production-grade code structure for the critical path.
Use:
../../shared/checklists/polished-prototype-rubric.md../../shared/checklists/production-code-checklist.md../../shared/checklists/game-feel-pillars.md
Workflow
- Protect the user’s real ask. Do not cut away defining features merely to move faster.
- Build a strong first minutes experience.
- Implement the requested feature set for this pass, not just one isolated mechanic.
- Make the build feel deliberate: feedback, transitions, fail/retry, readability.
- Keep architecture clean enough to continue development.
- Verify and repair before calling it done.
Important
If the user asked for a strong prototype, first-playable is not enough.
This skill exists to resist that accidental down-scoping.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.