Search

PythonReactSEOPDF
GitHub Skill

bevy-game-dev

Bevy game development guidance for Rust/Bevy projects, covering ECS architecture, system scheduling, events, helper utilities, project structuring, and build/performance profiles. Use when designing, reviewing, or refactoring Bevy game code; adding systems/components/resources; organizing plugins and states; or tuning build and release workflows.

Stephanvs☆ 6 Repository stars0 Repository forks

Installation

Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.

View source ↗Guides

Skill instructions

Bevy Game Dev

Overview

Use this skill to apply Bevy best practices when designing or reviewing game architecture, ECS patterns, scheduling, and build profiles.

Workflow

  1. Clarify the task goal (feature, refactor, performance, build pipeline).
  2. Identify Bevy version, states, and existing module/plugin layout.
  3. Apply ECS patterns for entities, IDs, and helper utilities.
  4. Define system scheduling with state bounds, sets, and explicit ordering.
  5. Validate project structure (prelude, internal plugins, system grouping).
  6. Adjust build and performance settings when needed.

References

  • Read references/bevy-best-practices.md for patterns, snippets, and build profile blocks.
  • Use the reference as the canonical source for recommendations.

Output Guidance

  • Provide stepwise changes or concrete snippets tailored to the user’s codebase.
  • Call out ordering dependencies between systems, sets, and events.
  • When touching build profiles, include the exact Cargo.toml blocks and commands.

Examples

Read the usage examples in the source repository.

View source ↗

Source history

Indexed on
2026-01-20
Index updated
2026-01-26
Branch
main

Index and sync dates describe this directory. View the source repository for code history.

GitHub ↗

chat Comments (0)

chat_bubble_outline

No comments yet. Be the first to share your thoughts!