rust-bevy-state-flow
Design and review Bevy game state flow with plugins, AppState enums, OnEnter and OnExit setup, state-scoped cleanup, menus, pause screens, transitions, and run conditions. Use when adding reusable Bevy game state management, debugging duplicated entities after transitions, or separating menu, loading, playing, paused, and game-over logic.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- rust-bevy-state-flow
- license
- MIT
- metadata
- { "tags": "rust,bevy,gamedev,state-management,plugins", "version": "0.1.0", "category": "Rust", "displayName": "Rust Bevy State Flow" }
- description
- Design and review Bevy game state flow with plugins, AppState enums, OnEnter and OnExit setup, state-scoped cleanup, menus, pause screens, transitions, and run conditions. Use when adding reusable Bevy game state management, debugging duplicated entities after transitions, or separating menu, loading, playing, paused, and game-over logic.
- compatibility
- Codex, Claude Code, and other Agent Skills-compatible clients.
02 资源文件 4
- 参考文档agents/openai.yaml210 B
- 参考文档guidelines.md1.5 KB
- 参考文档references/state-flow-patterns.md2.5 KB
- 参考文档workflows/add-state-flow.md2.1 KB
03 SKILL.md 正文
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.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.