rust-bevy-asset-pipeline
Build and review Bevy game asset loading pipelines with typed asset catalogs, path validation, loading states, handle ownership, sprite sheets, audio, and runtime resource checks. Use when organizing Bevy assets, replacing hard-coded paths, adding loading screens, diagnosing missing handles, or packaging Rust game resources.
- License 许可
- MIT
- 最近更新
- 2026-06-26
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- rust-bevy-asset-pipeline
- license
- MIT
- metadata
- { "tags": "rust,bevy,gamedev,assets,packaging", "version": "0.1.0", "category": "Rust", "displayName": "Rust Bevy Asset Pipeline" }
- description
- Build and review Bevy game asset loading pipelines with typed asset catalogs, path validation, loading states, handle ownership, sprite sheets, audio, and runtime resource checks. Use when organizing Bevy assets, replacing hard-coded paths, adding loading screens, diagnosing missing handles, or packaging Rust game resources.
- compatibility
- Codex, Claude Code, and other Agent Skills-compatible clients.
02 资源文件 4
- 参考文档agents/openai.yaml223 B
- 参考文档guidelines.md1.5 KB
- 参考文档references/asset-pipeline-patterns.md2.9 KB
- 参考文档workflows/build-asset-pipeline.md2.3 KB
03 SKILL.md 正文
Rust Bevy Asset Pipeline
Use this skill to make Bevy assets explicit, typed, validated, and packageable. The goal is to remove scattered string paths and make loading state observable.
Core Workflow
- Inventory images, atlases, fonts, sounds, music, and data files.
- Create a typed catalog resource that owns paths and loaded handles.
- Validate paths before gameplay systems depend on the assets.
- Load assets in a dedicated loading state or plugin.
- Pass handles through resources/components; avoid reloading from gameplay systems.
- Smoke test release packaging from the same runtime layout users will run.
Read Next
| Task | Load |
|---|---|
| Design a catalog or loading plugin | guidelines.md, references/asset-pipeline-patterns.md |
| Replace scattered asset paths | workflows/build-asset-pipeline.md |
| Diagnose missing assets in packaged builds | guidelines.md, workflows/build-asset-pipeline.md |
Source Notes
Guidance is transformed and paraphrased from Herbert Wolverson, Advanced Hands-On Rust, especially Chapter 6 on game assets and the recurring release-readiness checks across the book. Examples are original skeletons.
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.