← ClaudeAtlas

bevylisted

This skill should be used when working on Bevy game engine projects. It provides specialized knowledge for Bevy's Entity Component System (ECS) architecture, component-driven design patterns, system ordering, UI development, build strategies, and common pitfalls. Use this skill when implementing game features, debugging Bevy code, designing component architectures, or working with Bevy's UI system.
smanaton/bevy-skill · ★ 1 · Web & Frontend · score 72
Install: claude install-skill smanaton/bevy-skill
# Bevy Game Development Skill A specialized skill for developing games and applications using the Bevy game engine, based on real-world experience building complex Bevy projects. ## When to Use This Skill Invoke this skill when: - Implementing features in a Bevy game or application - Designing component architectures for ECS - Creating or debugging Bevy systems - Working with Bevy's UI system - Building and testing Bevy projects - Troubleshooting common Bevy issues - Organizing project structure for Bevy applications ## Before You Start: Essential Bevy Tips ### ⚠️ Bevy 0.19 Breaking Changes > This skill targets **Bevy 0.19** (0.19.0, released 2026-06-19) — the current > version. For a project still on 0.18, the items below marked as 0.18-era > (messages, `single()`) still apply; see the migration-gotchas section in > `references/bevy_specific_tips.md` for the 0.18 → 0.19 deltas. **When working with Bevy 0.19**, be aware of these API shapes: - Material handles wrapped in `MeshMaterial3d<T>` (not `Handle<T>`); meshes in `Mesh3d` - Buffered **events are "messages"**: `EventWriter`→`MessageWriter` (`.write()`), `EventReader`→`MessageReader` (`.read()`), `add_event::<T>()`→`add_message::<T>()`, `#[derive(Event)]`→`#[derive(Message)]` - Observers (`commands.trigger()`, `add_observer()`) are a **separate** reactive tool — not a replacement for buffered messages - Queries use `.single()`/`.single_mut()` (both return `Result`); `get_single*` was removed - `TextFont.font_size` i