bevy

Guide Bevy ECS projects through patterns, plugin architecture, and UI integration.

52|7|Updated Jul 5, 2025
One-click install
npx skills add https://github.com/bfollington/terma --skill bevy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bevy
Source: https://github.com/bfollington/terma/tree/main/skills/bevy
Command: npx skills add https://github.com/bfollington/terma --skill bevy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Developing games with the Bevy engine, especially with its ECS architecture, can be challenging due to rapid API changes, complex data modeling, and performance considerations. This skill provides up-to-date guidance, architectural patterns, and debugging strategies, helping you navigate Bevy's intricacies and build robust games more efficiently.

Core Features & Use Cases

  • ECS Best Practices: Learn component-driven design, system ordering, and efficient query patterns to build scalable game logic.
  • Bevy 0.17 Migration: Get critical updates and solutions for breaking changes in Bevy 0.17, including material wrappers and the new observer pattern.
  • Optimized Development Workflow: Leverage dynamic linking for faster compile times, understand build management, and follow incremental testing strategies.
  • Use Case: You're implementing a health system for your game. Use this skill to design the Health component, create systems for damage processing and death detection, and integrate a UI health bar, ensuring all components are correctly registered and optimized for performance.

Quick Start

Help me design a basic inventory system for my Bevy game. I need components for Inventory and Item, and a system to add items.

Frequently Asked Questions about bevy

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

FAQPage Schema
How do I design components and systems for Bevy games using ECS architecture?

ECS architecture in Bevy organizes game logic through components (data containers), entities (objects combining components), and systems (functions processing entities). Design by identifying what data your game needs (Health, Position, Velocity as components), then write systems that query and modify those components. This data-driven approach scales from small to large projects and simplifies debugging and reuse.

What changed in Bevy 0.17 and how do I migrate my project?

Bevy 0.17 introduced breaking changes including material wrappers and a new observer pattern for event handling. Migration requires updating component registration, material definitions, and event listeners to the new API. This skill provides targeted solutions for these specific breaking changes to minimize refactoring time.

How do I structure plugins and organize large Bevy projects?

Plugins in Bevy package reusable game systems, components, and configuration into modular units. Structure projects by plugin type—gameplay plugins (health, inventory), UI plugins (menus, HUD), and utility plugins (input, physics). This modular approach reduces coupling, improves testability, and makes features portable across projects.

How do I build a UI system in Bevy and integrate it with game logic?

Bevy's UI layout system uses hierarchical entity structures and bundles to create responsive interfaces. Integrate UI with game logic by spawning UI entities with components linked to game state (like a Health component triggering a health bar update). This skill covers layout practices and system ordering to keep UI synchronized with gameplay.

What compile-time optimizations reduce build times for Bevy development?

Dynamic linking and incremental compilation significantly speed Bevy iteration. Enable dynamic linking in dev builds, use cargo-watch for incremental changes, and organize systems to reload without full recompilation. These workflows let you test gameplay changes in seconds rather than minutes.

How do I debug component queries and system ordering issues in Bevy?

System ordering bugs occur when systems run in wrong sequence, causing stale data or missed updates. Debug by inspecting query results, using Bevy's built-in diagnostics, and validating component registration. Correct ordering ensures systems read the current frame's data and prevents race conditions.