bevy-template/.opencode/skills/bevy-architecture/SKILL.md

name, description, license, compatibility, metadata

name	description	license	compatibility	metadata
bevy-architecture	Review and improve Bevy project structure, plugin boundaries, and feature isolation	MIT	opencode	stack concern bevy architecture

What I do

• review plugin boundaries
• spot ECS smells
• suggest module split
• suggest state/event/resource boundaries
• keep project workshop-fast

Smells to flag

• giant systems
• state hidden in many places
• UI mixed with gameplay
• direct coupling across features
• asset logic spread everywhere

Deliverable

• top strengths
• top risks
• concrete refactor order
• verify commands