Individual skill

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.

plugins/LVTD-LLC/skills/skills/rust-bevy-asset-pipeline/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 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

1. Inventory images, atlases, fonts, sounds, music, and data files.
2. Create a typed catalog resource that owns paths and loaded handles.
3. Validate paths before gameplay systems depend on the assets.
4. Load assets in a dedicated loading state or plugin.
5. Pass handles through resources/components; avoid reloading from gameplay
   systems.
6. Smoke test release packaging from the same runtime layout users will run.