Project Migration

This is a strict guideline. Follow these rules exactly.

Migrate an existing project to the host-native toolchain. Unlike project-setup (which scaffolds from scratch), this skill works with existing code — it must be non-destructive and interactive.

The target state is defined in ~/Hermes-Shared/guitarizta/docs/dev-toolchain-architecture.md. Read that document for the canonical reference. This skill is the operational workflow for reaching that state.

Core Principles

• Never overwrite without asking. Present diffs for any file that already exists.
• Work on a branch. All changes happen on chore/migrate-project-setup.
• Ask early, not late. When intent is ambiguous, ask before assuming.
• No devcontainers. Never add or preserve .devcontainer/ config. If it exists, plan to remove it.