bevy-ecs
Structure a Bevy app around its Entity Component System: build the App with plugins, define Component/Resource types, write systems with Query/Res/Commands, filter and order systems, and use the Time resource for frame-rate-independent motion. Use when building or debugging a Bevy game in Rust — when the user mentions Bevy, ECS, App::new, add_systems, Query, Commands, components/systems, or a Cargo.toml depending on bevy.
npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill bevy-ecs --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Bevy ECS Structure a Bevy game in Rust around the Entity Component System: the `App` and plugins, components and resources, systems with queries, scheduling, and frame-rate-independent updates. Pins **Bevy 0.16+** (code targets 0.16; Bevy's API shifts each minor release — match your `Cargo.toml`). ## When to use - Use when wiring a Bevy `App`, defining `Component`/`Resource` types, writing systems that query entities, ordering/filtering systems, or fixing borrow-conflict panics and frame-dependent movement. - Use when `Cargo.toml` depends on `bevy` and code calls `App::new()`, `add_systems`, `Query`, or `Commands`. **When *not* to use:** this is the ECS core. Deep rendering, custom shaders/ pipelines, UI layout, and audio are separate concerns. For engine-agnostic AI or procedural algorithms, pair with `game-ai` / `procedural-gen`. ## Core workflow 1. **Pin the version.** Bevy's API changes every minor release. Set `bevy = "0.16"` (or your target) in `Cargo.toml` and treat the matching docs as truth. Enable `dynamic_linking` in dev for faster iterative builds. 2. **Build the `App`.** `App::new().add_plugins(DefaultPlugins)` gives windowing, input, rendering, time, etc. Register s
- When to use
- Core workflow
- Patterns
- 1. Cargo.toml + minimal App
- 2. Components, resources, and spawning
- 3. A system with a query + the Time resource
- 4. Query filters (With / Without / Changed)
- 5. Resources: read and write
- 6. Ordering, run conditions, and plugins
- Pitfalls
- References
- Related skills
What does the bevy-ecs skill do?
Structure a Bevy app around its Entity Component System: build the App with plugins, define Component/Resource types, write systems with Query/Res/Commands, filter and order systems, and use the Time resource for frame-rate-independent motion. Use when building or debugging a Bevy game in Rust — when the user mentions Bevy, ECS, App::new, add_systems, Query, Commands, components/systems, or a Cargo.toml depending on bevy.
How do I install it?
Run `npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill bevy-ecs --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From gamedev-skills/awesome-gamedev-agent-skills, a repository with 406 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.