What problem does it solve? Setting up a legacy Angular to React Router v7 migration requires knowing the monorepo layout, app surfaces, routing flip mechanisms, and i18n configuration — gathering all of this manually into a consistent plugin config is error-prone and easy to get wrong. ## Core Features & Use Cases - Automatic Layout Detection: Scans the repository for legacy Angular apps (angular.json), React Router v7 targets, shared packages, and backend API contract directories. - Guided Configuration: Walks through per-app settings (domain, ports, SSR mode, webview, SSO, nginx vs CloudFront flip mechanism) and writes .claude/frontend-migration-plugin.json plus a migration tracker. - External Skill Installation: Vendors React Router framework-mode, Vitest, and React best-practices skills into .claude/skills/ and verifies Playwright for E2E gates. - Use Case: A team starting a Strangler Fig migration from Angular to React Router v7 runs this once to bootstrap the plugin config, tracker, and gate infrastructure before analyzing the first page. ## Quick Start Run the fm-init skill to detect my monorepo layout and initialize the frontend migration plugin configuration and tracker.