Vercel Microfrontends
Split a large application into independently deployable units that render as one cohesive app. Vercel handles routing on its global network using microfrontends.json.
Core concepts: default app (has microfrontends.json, serves unmatched requests) · child apps (have routing path patterns) · asset prefix (prevents static-asset collisions) · independent deployments.
Frameworks: Next.js (App Router + Pages Router), SvelteKit, React Router, Vite — all via @vercel/microfrontends.
CLI (vercel microfrontends / vercel mf):
create-group — create a new group; interactive by default, or fully non-interactive with --non-interactive (options: --name, --project (repeatable), --default-app, --default-route, --project-default-route (repeatable, format: <project>=<route>, required for each non-default project in non-interactive mode), --yes to skip confirmation prompt); note: --non-interactive is blocked if adding the projects would exceed the free tier limit — the user must confirm billing changes interactivelyadd-to-group — add the current project to an existing group; requires interactive terminal (options: --group, --default-route)remove-from-group — remove the current project from its group; requires interactive terminal (option: --yes skips project-link prompt only)delete-group — delete a group and all its settings, irreversible; requires interactive terminal (option: --group to pre-select group)pull — pull remote microfrontends.json for local development (option: --dpl)microfrontends proxy — local dev proxy · microfrontends port — print auto-assigned port
Finding Detailed Information
This skill includes detailed reference docs in the references/ directory. Do not read all references upfront. Instead, search or grep the relevant file when the user asks about a specific topic:
| Topic |
Reference file |
Getting started, quickstart, framework setup, microfrontends.json schema, fields, naming, examples |
references/configuration.md |
| Path expressions, asset prefixes, flag-controlled routing, middleware |
references/path-routing.md |
| Local proxy setup, polyrepo config, Turborepo, ports, deployment protection |
references/local-development.md |
Inspecting groups (inspect-group), adding/removing projects, fallback environments, navigation, observability |
references/managing-microfrontends.md |
Testing utilities (validateMiddlewareConfig, validateRouting, etc.), debug headers, common issues |
references/troubleshooting.md |
| Deployment protection, Vercel Firewall, WAF rules for microfrontends |
references/security.md |
When the user asks about a specific topic, use grep or search over the relevant reference file to find the answer without loading all references into context.
Source: vercel/microfrontends — distributed by TomeVault.
1---2name: vercel-microfrontends3description: Guide for building, configuring, and deploying microfrontends on Vercel. Use this skill when the user mentions microfrontends, multi-zones, splitting an app across teams, independent deployments, cross-app routing, incremental migration, composing multiple frontends under one domain, microfrontends.json, @vercel/microfrontends, the microfrontends local proxy, or path-based routing between Vercel projects. Also use when the user asks about shared layouts across projects, navigation between microfrontends, fallback environments, asset prefixes, or feature flag controlled routing. Use when this capability is needed.4---56# Vercel Microfrontends7Split a large application into independently deployable units that render as one cohesive app. Vercel handles routing on its global network using `microfrontends.json`.89**Core concepts:** default app (has `microfrontends.json`, serves unmatched requests) · child apps (have `routing` path patterns) · asset prefix (prevents static-asset collisions) · independent deployments.1011**Frameworks:** Next.js (App Router + Pages Router), SvelteKit, React Router, Vite — all via `@vercel/microfrontends`.1213**CLI (`vercel microfrontends` / `vercel mf`):**14- `create-group` — create a new group; interactive by default, or fully non-interactive with `--non-interactive` (options: `--name`, `--project` (repeatable), `--default-app`, `--default-route`, `--project-default-route` (repeatable, format: `<project>=<route>`, required for each non-default project in non-interactive mode), `--yes` to skip confirmation prompt); note: `--non-interactive` is blocked if adding the projects would exceed the free tier limit — the user must confirm billing changes interactively15- `add-to-group` — add the current project to an existing group; requires interactive terminal (options: `--group`, `--default-route`)16- `remove-from-group` — remove the current project from its group; requires interactive terminal (option: `--yes` skips project-link prompt only)17- `delete-group` — delete a group and all its settings, irreversible; requires interactive terminal (option: `--group` to pre-select group)18- `pull` — pull remote `microfrontends.json` for local development (option: `--dpl`)19- `microfrontends proxy` — local dev proxy · `microfrontends port` — print auto-assigned port2021## Finding Detailed Information2223This skill includes detailed reference docs in the `references/` directory. **Do not read all references upfront.** Instead, search or grep the relevant file when the user asks about a specific topic:2425| Topic | Reference file |26|---|---|27| Getting started, quickstart, framework setup, `microfrontends.json` schema, fields, naming, examples | `references/configuration.md` |28| Path expressions, asset prefixes, flag-controlled routing, middleware | `references/path-routing.md` |29| Local proxy setup, polyrepo config, Turborepo, ports, deployment protection | `references/local-development.md` |30| Inspecting groups (`inspect-group`), adding/removing projects, fallback environments, navigation, observability | `references/managing-microfrontends.md` |31| Testing utilities (`validateMiddlewareConfig`, `validateRouting`, etc.), debug headers, common issues | `references/troubleshooting.md` |32| Deployment protection, Vercel Firewall, WAF rules for microfrontends | `references/security.md` |3334When the user asks about a specific topic, use grep or search over the relevant reference file to find the answer without loading all references into context.3536---37> Source: [vercel/microfrontends](https://github.com/vercel/microfrontends) — distributed by [TomeVault](https://tomevault.io).38<!-- tomevault:4.0:skill_md:2026-06-17 -->
tomevault-io