ConcertoNotes Rust Bevy State Flow
Use this skill to make Bevy states explicit and reusable. State flow should describe when systems run, what is created on entry, and what is cleaned up on exit.
Core Workflow
- Name the user-visible game phases before adding systems.
- Represent phases with an
AppStateor feature-specific state enum. - Put setup in
OnEnter, cleanup inOnExit, and gameplay in state-filtered update schedules. - Mark state-owned entities with cleanup components.
- Keep transitions event-driven or command-driven, not hidden in rendering systems.
- Test repeated transitions to catch duplicate entities and stale resources.
Read Next
| Task | Load |
|---|---|
| Add a menu, pause, loading, or game-over state | guidelines.md, workflows/add-state-flow.md |
| Review Bevy plugins and state-scoped systems | references/state-flow-patterns.md |
| Debug transition leaks | guidelines.md, references/state-flow-patterns.md |
Source Notes
Guidance is transformed and paraphrased from Herbert Wolverson, Advanced Hands-On Rust, especially Chapter 5 on reusable game state management. Examples are original skeletons adapted for modern Bevy patterns.