vibegame-edit

# VibeGame Edit For reworking an existing game, for example: - **Style migration**: pixel art to hand-drawn, or one IP to another. - **Genre migration**: real-time combat to turn-based tactics. - **Rule migration**: changing a core rule, such as swapping the player and boss roles. An edit is not a local substitution bounded by file type. Start from game design, and keep the reworked mechanics, controls, feedback, and art adding up to one coherent experience. Change whatever that requires — code, assets, config, project structure. ## Phase 1: Establish a baseline Before editing: 1. Run `vibegame check` and record the existing project's static check results. 2. Commit the existing project files, saving the pre-edit state as a baseline commit. Do not start a playtest, runtime API test, or review pass just to establish the baseline. ## Phase 2: Enter the general build workflow Invoke the `vibegame-build` SKILL and follow its plan-run workflow for planning, implementation, testing, and review. Do not build a separate approval, implementation, or verification flow for edits. In `vibegame-build`'s Plan phase, inspect the current project and understand the existing design this request touches, and how its parts connect: core loop, rules, controls, character behavior, animation, collision, feedback, UI, art style. Ask follow-up questions grounded in that existing design and the direction the user gave, until the preferences and goals that shape the approach are clear. When ...