What problem does it solve? Splitting a large frontend application into independently deployable units that render as one cohesive app requires complex routing, asset isolation, and local development orchestration. This Skill guides you through building, configuring, and deploying microfrontends on Vercel so multiple teams can ship independently under one domain. ## Core Features & Use Cases - Routing Configuration: Define microfrontends.json with default apps, child apps, path expressions, asset prefixes, and flag-controlled routing handled at Vercel's network layer. - Framework Integration: Wire up Next.js (App and Pages Router), SvelteKit, React Router, or Vite via the @vercel/microfrontends package and its config wrappers. - Local Development Proxy: Run only the microfrontend you are working on while the local proxy routes other paths to production fallbacks, with Turborepo and polyrepo support. - Use Case: A platform team splits a monolithic Next.js app into web, docs, and dashboard projects, configures path routing in microfrontends.json, and uses the CLI (vercel mf create-group, inspect-group, pull) to manage the group across deployments. ## Quick Start Ask the assistant to set up a Vercel microfrontends group and generate a microfrontends.json routing your docs app under the /docs path.
