Index of every page on this site: llms.txt
All skills
vercel avatar

/microfrontends

@250769d official
by vercelvercel/vercel-plugin340 stars
82
Run it yourself

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.

  • 8 files
  • 45 KB
  • Updated 2 weeks ago
  • GitHub
Use this Skill: https://skilld.dev/gh/vercel/vercel-plugin/microfrontends

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈150 tokens for metadata: the name and description. ≈892 when used: this file. ≈10k more on demand in 6 files.

Description uses 7.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈601 characters, or 7.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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 interactively
  • add-to-group — add the current project to an existing group; always asks for confirmation (there is no --yes), so it needs an interactive terminal, and it refuses to run with --non-interactive when adding would go past the free project limit (options: --group and --default-route pre-fill the prompts)
  • remove-from-group — remove the current project from its group; without --yes it needs an interactive terminal (option: --yes skips the project-link prompt and removal confirmations, including the warning for projects still referenced in microfrontends.json)
  • delete-group — delete a group and all its settings, irreversible; without --yes it needs an interactive terminal (options: --group to pre-select group, --yes skips the deletion confirmation; pass both to delete without prompts)
  • inspect-group — retrieve group metadata (project names, frameworks, git repos, root dirs); useful for automating setup (options: --group, --json (CLI 58.1+; older CLIs use --format=json), --config-file-name)
  • pull — pull remote microfrontends.json for local development (option: --deployment; needs Vercel CLI 65+, older CLIs use --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: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 250769d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 weeks ago
Other metadata
metadata
{
  "priority": 7,
  "docs": [
    "https://vercel.com/docs/microfrontends"
  ],
  "pathPatterns": [
    "microfrontends.json",
    "microfrontends.jsonc",
    "apps/*/microfrontends.json",
    "apps/*/microfrontends.jsonc"
  ],
  "bashPatterns": [
    "\\bvercel\\s+microfrontends\\b",
    "\\bvercel\\s+mf\\b",
    "\\bnpm\\s+(install|i|add)\\s+[^\\n]*@vercel/microfrontends\\b",
    "\\bpnpm\\s+(install|i|add)\\s+[^\\n]*@vercel/microfrontends\\b",
    "\\bbun\\s+(install|i|add)\\s+[^\\n]*@vercel/microfrontends\\b",
    "\\byarn\\s+add\\s+[^\\n]*@vercel/microfrontends\\b"
  ],
  "importPatterns": [
    "@vercel/microfrontends"
  ]
}
retrieval
{
  "aliases": [
    "microfrontends",
    "multi-zones",
    "multi zones",
    "mfe",
    "microfrontend routing",
    "cross-zone navigation"
  ],
  "intents": [
    "split app into microfrontends",
    "set up microfrontends",
    "configure microfrontends.json",
    "add path routing between projects",
    "share layout across microfrontends"
  ],
  "entities": [
    "microfrontends.json",
    "@vercel/microfrontends",
    "default app",
    "child app",
    "asset prefix",
    "microfrontends group"
  ]
}
chainTo
[
  {
    "pattern": "runMicrofrontendsMiddleware|flag.*microfrontend|microfrontend.*flag",
    "targetSkill": "routing-middleware",
    "message": "Flag-controlled microfrontend routing requires middleware in the default app — loading Routing Middleware guidance."
  }
]

README badge

README badge for vercel/vercel-plugin/microfrontends