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-06-26
- Stars
- ★ 0
- Forks
- 0
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
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.