Skip to content
Back to skills

Rust Bevy State Flow

ASecurity

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.

  • 3 stars
  • 0 votes
  • 0 copies
  • 9 views
  • Added September 12, 2026
ai-agentsrustgodebugginggit

Security analysis

A100/100

Pro scans all 5 files and shows the line behind each finding

Scanned September 12, 2026

npx -y skills add thedixitjain/the-mega-skill-library --skill rust-bevy-state-flow --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Rust Bevy State Flow?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Rust Bevy State Flow
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/thedixitjain-rust-bevy-state-flow/badge)](https://www.skillsdirectory.com/skills/thedixitjain-rust-bevy-state-flow)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: 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."
category: engineering-core
source_repo: hashgraph-online/awesome-codex-plugins
source_path: "plugins/LVTD-LLC/skills/skills/rust-bevy-state-flow/SKILL.md"
source_url: https://github.com/hashgraph-online/awesome-codex-plugins/blob/HEAD/plugins/LVTD-LLC/skills/skills/rust-bevy-state-flow/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

1. Name the user-visible game phases before adding systems.
2. Represent phases with an `AppState` or feature-specific state enum.
3. Put setup in `OnEnter`, cleanup in `OnExit`, and gameplay in state-filtered
   update schedules.
4. Mark state-owned entities with cleanup components.
5. Keep transitions event-driven or command-driven, not hidden in rendering
   systems.
6. 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.

---

**Source:** [`hashgraph-online/awesome-codex-plugins`](https://github.com/hashgraph-online/awesome-codex-plugins) → `plugins/LVTD-LLC/skills/skills/rust-bevy-state-flow/SKILL.md`

Files in this skill

  • SKILL.md2 KB
  • agents/openai.yaml210 B
  • guidelines.md1.5 KB
  • references/state-flow-patterns.md2.5 KB
  • workflows/add-state-flow.md2.1 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.