vercel / microfrontends

The single skill, vercel-microfrontends, teaches an agent the vocabulary and file shape of Vercel's microfrontends product: writing and editing microfrontends.json, splitting one large app across separate Vercel projects, path-based cross-app routing, fallback environments, asset prefixes, and feature-flag-controlled routes between zones. It does not scaffold a project, run a migration, or call any API — it is documentation turned into a skill so an agent stops guessing at config-file shape and flag names.

This is for a team already committed to Vercel's microfrontends architecture — splitting a large Next.js, SvelteKit, React Router, or Vite app into independently deployed pieces under one domain — who wants an agent that writes correct microfrontends.json and routing config on the first try instead of after a few wrong guesses. If you are not building on Vercel's microfrontends feature specifically, there is nothing else here for you.

READ THE FULL ANALYSIS＋

It is Vercel's own package, and it shows. The README is the product's install and marketing page, not skill-specific material; the skill itself carries no setup steps beyond "read this when the user mentions microfrontends," no credentials, and no dependency on anything but the reader's own repository files.