Finish and package small Rust games with MVP lock, playability checks, resource packaging, release builds, smoke tests, and disciplined post-MVP polish.
SkillScore86Maintained
Automatic
◆Coding pack
Last verified 8/16/2026
What it changes
Passed 19 of 22 test cases with the skill, and 12 of 22 without it.
Without skill55%
With skill86%
Checks it passed that the model alone missed
The response specifies smoke testing level transitions.
The response explicitly mentions testing the game restart flow.
The response advises avoiding architectural refactoring during the release polish phase.
and 4 more in the full report
7 fixed12 passed either way3 still failing0 broke
Pass-rate lift
+32 pp
Tokens
-18%
Agent turns
0%
Response time
-20%
Model gemini-3.6-flashMeasured 8/16/2026v119 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 7
Prompt
What operational game flow state is frequently forgotten when testing game loop readiness right before publishing a compiled executable?
What was checked, without and with the skill
Checked
Without skill
With skill
The response explicitly mentions testing the game restart flow.
Missed
Passed
case-12 · gemini-3.6-flash · 8/16/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md26 lines2 files
Rust Game Polish Release
Use this skill to finish a small Rust game without destabilizing the MVP. Lock
the playable loop first, then package assets, run release checks, and add only
the polish that improves clarity or shareability.
Core Workflow
Confirm the MVP loop is playable from launch to win/loss or exit.
Freeze core mechanics before adding content and visual polish.
Verify resources load from the release layout.
Run formatting, linting, tests, and release build commands.
Smoke test controls, restart, level transitions, and exit behavior.
Write a small release checklist instead of making last-minute architecture
changes.
Read Next
Read references/polish-release-patterns.md for release gates, packaging
checks, and safe polish triage.
Source Notes
Guidance is transformed and paraphrased from Hands-On Rust Chapter 16 and
the book's recurring slice-based development pattern. Packaging details should
be adapted to the target engine, OS, and distribution channel.