agentleFS
Sign inStart free
VercelKnown publishervercel/microfrontends/skills/vercel-microfrontends/SKILL.md

vercel-microfrontends

Skill45 starsChanged 7 months agoMITView on GitHub

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.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Core concepts: default app (has microfrontends.json, serves unmatched requests) · child apps (have routing path patterns) · asset prefix …

    line 13
  2. Distinctive:

    When the user asks about a specific topic, use grep or search over the relevant reference file to find the answer without loading all …

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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; 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:

TopicReference file
Getting started, quickstart, framework setup, microfrontends.json schema, fields, naming, examplesreferences/configuration.md
Path expressions, asset prefixes, flag-controlled routing, middlewarereferences/path-routing.md
Local proxy setup, polyrepo config, Turborepo, ports, deployment protectionreferences/local-development.md
Inspecting groups (inspect-group), adding/removing projects, fallback environments, navigation, observabilityreferences/managing-microfrontends.md
Testing utilities (validateMiddlewareConfig, validateRouting, etc.), debug headers, common issuesreferences/troubleshooting.md
Deployment protection, Vercel Firewall, WAF rules for microfrontendsreferences/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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free