bevy

Guide Bevy developers to migrate to idiomatic Bevy 0.18 ECS code.

3|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/pavlov-net/claude-plugins --skill bevy-pavlov-net
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bevy
Source: https://github.com/pavlov-net/claude-plugins/tree/main/bevy/skills/bevy
Command: npx skills add https://github.com/pavlov-net/claude-plugins --skill bevy-pavlov-net

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bevy 0.18 idioms guide helps developers migrate to and write idiomatic Bevy 0.18 ECS code, reducing debugging time and architectural drift.

Core Features & Use Cases

  • ECS data design: components, required components, queries, change detection, and relationships.
  • Communication patterns: Event, Message, Observer, and EntityEvent lifecycles to wire systems cleanly.
  • Scheduling and organization: System sets, run conditions, OnEnter/OnExit hooks, and fixed-timestep strategies for deterministic gameplay.
  • Migration & best practices: Bevy 0.18 rename rules, pitfall avoidance, and performance-oriented guidance.

Quick Start

Read the idioms guide and start applying 0.18 Bevy patterns to your project, focusing on data design, event wiring, and centralized scheduling.

Frequently Asked Questions about bevy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate my Rust game codebase to Bevy 0.18 ECS idioms?

Idiomatic Bevy 0.18 ECS data design uses components, required components, queries, change detection, and relationships to structure game state robustly while avoiding architectural drift during upgrades.

What is the best way to wire ECS communication patterns in Bevy 0.18?

The best way to wire Bevy 0.18 ECS communication is using Event, Message, Observer, and EntityEvent lifecycles to connect systems cleanly and manage game logic interactions.

How do I organize scheduling and system sets in Bevy 0.18 for deterministic gameplay?

Organize Bevy 0.18 scheduling by applying system sets, run conditions, OnEnter/OnExit hooks, and fixed-timestep strategies to achieve deterministic gameplay and centralized system organization.

Does this Bevy 0.18 migration guide cover performance and testing considerations?

Yes, the Bevy 0.18 migration guide covers performance-oriented guidance and testing strategies alongside ECS data design, plugin organization, and error handling for robust game development.

What are common pitfalls when upgrading to Bevy 0.18?

Common Bevy 0.18 upgrade pitfalls involve breaking changes from outdated ECS patterns, which you can avoid by following the 0.18 rename rules and adopting updated event wiring and scheduling practices.