What problem does it solve? Legacy Vue/Vite subapps often have inconsistent environment setups: scattered .env files, ad-hoc Vite configs, and unclear local debugging modes. This Skill scans, plans, migrates, and verifies a project into a unified structure with one public .env, five target environments (dev/sit/uat/pre/prd), and three local development modes. ## Core Features & Use Cases - Read-only scanning and planning: Detects whether a project is standard, legacy-direct, legacy-gateway, custom, or unsupported, then produces a file-level migration plan with backups before any write. - Confirmed transactional migration: Applies changes only after explicit confirmation, with automatic backup and rollback if static verification fails. - Five-environment verification: Validates the migrated config and optionally builds all five environments in a temporary copy without touching the real project. - Use Case: A team inherits an old Vite subapp using 172.x/9000 direct API addresses. Run the scan, confirm the walsin profile and module name, apply the migration, and verify all five environment builds pass. ## Quick Start Ask the AI to scan the current project with the standard environment configuration capability, generate a migration plan for the walsin profile, and wait for your confirmation before applying and verifying.
