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.
- License 许可
- MIT
- 最近更新
- 2026-06-26
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- rust-game-polish-release
- license
- MIT
- metadata
- { "tags": "rust,gamedev,release,packaging,polish", "version": "0.1.0", "category": "Rust", "displayName": "Rust Game Polish Release" }
- description
- 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.
- compatibility
- Codex, Claude Code, and other Agent Skills-compatible clients.
02 资源文件 1
- 参考文档references/polish-release-patterns.md2.8 KB
03 SKILL.md 正文
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.
04 同仓库更多 Skills
android-emulator-qa
Use when validating Android feature flows in an emulator with adb-driven launch, input, UI-tree inspection, screenshots, and logcat capture.
supabase-postgres-best-practices
Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.
sentry
Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.
render-workflows
Sets up, develops, tests, and deploys Render Workflows. Covers first-time scaffolding (via CLI or manual), SDK installation (Python or TypeScript), task patterns (retries, subtasks, fan-out), local development, Dashboard deployment, and troubleshooting. Use when a user wants to set up Render Workflows for the first time, scaffold a workflow service, add or modify workflow tasks, test workflows locally, or deploy workflows to Render.
render-web-services
Configures Render web services—port binding, TLS, health checks, custom domains, auto-deploy, PR previews, persistent disks, and deploy lifecycle. Use when the user needs to set up a web service, fix health check failures, add a custom domain, configure zero-downtime deploys, or troubleshoot port binding issues.
render-static-sites
Deploys and configures static sites on Render's global CDN—build commands, publish paths, SPA routing, redirects, custom headers, and PR previews. Use when the user needs to deploy a static site, set up a React/Vue/Hugo/Gatsby frontend, configure SPA fallback routing, add redirect rules, customize response headers, or choose between a static site and a web service for their frontend. Trigger terms: static site, CDN, SPA, single-page app, React deploy, Vue deploy, Hugo, Gatsby, Docusaurus, Jekyll, staticPublishPath.