g4borg
325e278af1
Add plugin skeleton with versioned skill directories, TODO SKILL.md scaffolds with goals for skill-creator, and copy over bevy-skill-research reports from spacecraft into docs/workpad/research/.
2.0 KiB
2.0 KiB
name, description
| name | description |
|---|---|
| bevy-upgrade | TODO: Use the skill-creator skill to write this. See scaffolding goals below. |
Bevy Upgrade — Version Migration Guide
This skill is a scaffold. Use
/skill-creatorto create the full skill content from the research material.
Scaffolding Goals
- Use the
skill-creator:skill-creatorskill to create the full SKILL.md content - Feed it the version-change annotations from research reports 01-06 in
docs/workpad/research/bevy-skill-research/ - The skill should trigger when the user asks to upgrade/migrate Bevy versions, or when the
bevyskill detects upgrade work - Core content:
- Breaking-change chain from 0.16 through 0.19+
- Rename tables (old name -> new name, which version)
- Semantic shifts (behavior changes, not just renames)
- Step-by-step migration patterns for each version bump
- Common upgrade pitfalls and their fixes
- Populate
references/with per-version-transition files (e.g.,0.17-to-0.18.md,0.18-to-0.19.md) - The skill should be invocable both directly and from the
bevyskill
Reference Material
Same research as the bevy skill — version-change annotations are woven into each report:
- 01-plugins.md — Plugin API changes across versions
- 02-ecs-core.md — ECS API renames and new patterns
- 03-hierarchy.md — Parent->ChildOf transition
- 04-events-observers.md — Event/Message split
- 05-input.md — Input API changes
- 06-camera-gotchas.md — Camera API changes