42 lines
785 B
Markdown
42 lines
785 B
Markdown
---
|
|
name: bevy-ecs
|
|
description: Design clean Bevy ECS layouts with components, resources, events, systems, and states
|
|
license: MIT
|
|
compatibility: opencode
|
|
metadata:
|
|
stack: bevy
|
|
language: rust
|
|
---
|
|
|
|
## What I do
|
|
|
|
- turn game idea into ECS parts
|
|
- split data across components, resources, and events
|
|
- propose system boundaries
|
|
- suggest state flow
|
|
- keep Bevy code idiomatic and small
|
|
|
|
## When to use me
|
|
|
|
Use when:
|
|
- new mechanic starts
|
|
- code feels like one giant system
|
|
- feature needs plugin split
|
|
- event vs resource choice unclear
|
|
|
|
## Output shape
|
|
|
|
1. goal
|
|
2. ECS map
|
|
3. file plan
|
|
4. patch order
|
|
5. verify commands
|
|
|
|
## Rules
|
|
|
|
- prefer Bevy built-ins before extra crates
|
|
- keep `main.rs` thin
|
|
- prefer events for loose coupling
|
|
- prefer states for app flow
|
|
- keep names specific
|