Individual skill

rust-game-polish-release

Finish and package small Rust games with MVP lock, playability checks, resource packaging, release builds, smoke tests, and disciplined post-MVP polish. Use when preparing a Rust game prototype for sharing, packaging bracket-lib assets, or deciding what finishing work belongs before release.

plugins/LVTD-LLC/skills/skills/rust-game-polish-release/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 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)
1,531
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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

1. Confirm the MVP loop is playable from launch to win/loss or exit.
2. Freeze core mechanics before adding content and visual polish.
3. Verify resources load from the release layout.
4. Run formatting, linting, tests, and release build commands.
5. Smoke test controls, restart, level transitions, and exit behavior.
6. Write a small release checklist instead of making last-minute architecture