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.
Source: hashgraph-online/awesome-codex-plugins → plugins/LVTD-LLC/skills/skills/rust-bevy-asset-pipeline/SKILL.md