Next.js Developer
Jeffallan/claude-skills
Builds Next.js 14+ apps on the App Router with server components, server actions, explicit caching, SEO metadata, loading and error boundaries and Vercel deployment.
Guide for building, configuring, and deploying microfrontends on Vercel.
Install Microfrontends
$ npx skills add vercel/vercel-plugin --skill microfrontends -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vercel/vercel-plugin microfrontends --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/vercel/vercel-plugin.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/microfrontends .claude/skills/microfrontends && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "microfrontends" agent skill from https://github.com/vercel/vercel-plugin/tree/main/skills/microfrontends into .claude/skills/microfrontends/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "microfrontends", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/vercel/vercel-plugin/tree/main/skills/microfrontendsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add vercel/vercel-plugin --skill microfrontends -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vercel/vercel-plugin microfrontends --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel/vercel-plugin.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/microfrontends .agents/skills/microfrontends && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "microfrontends" agent skill from https://github.com/vercel/vercel-plugin/tree/main/skills/microfrontends into .agents/skills/microfrontends/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "microfrontends", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vercel/vercel-plugin --skill microfrontends -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vercel/vercel-plugin microfrontends --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel/vercel-plugin.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/microfrontends .cursor/skills/microfrontends && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "microfrontends" agent skill from https://github.com/vercel/vercel-plugin/tree/main/skills/microfrontends into .cursor/skills/microfrontends/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "microfrontends", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/vercel/vercel-plugin.git --path skills/microfrontends--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add vercel/vercel-plugin --skill microfrontends -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vercel/vercel-plugin microfrontends --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel/vercel-plugin.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/microfrontends .gemini/skills/microfrontends && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "microfrontends" agent skill from https://github.com/vercel/vercel-plugin/tree/main/skills/microfrontends into .gemini/skills/microfrontends/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "microfrontends", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install vercel/vercel-plugin microfrontendsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add vercel/vercel-plugin --skill microfrontends -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/vercel/vercel-plugin.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/microfrontends .github/skills/microfrontends && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "microfrontends" agent skill from https://github.com/vercel/vercel-plugin/tree/main/skills/microfrontends into .github/skills/microfrontends/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "microfrontends", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vercel/vercel-plugin --skill microfrontends -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install vercel/vercel-plugin microfrontends --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel/vercel-plugin.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/microfrontends .opencode/skills/microfrontends && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "microfrontends" agent skill from https://github.com/vercel/vercel-plugin/tree/main/skills/microfrontends into .opencode/skills/microfrontends/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "microfrontends", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
microfrontends- GitHub stars
- 301
- Token cost
- ~1.3k tokens
- SKILL.md length
- 362 words
- Files
- 8 (incl. references)
- Skills in repo
- 38
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Guide for building, configuring, and deploying microfrontends on Vercel.
- The user mentions microfrontends
- Calls vercel
- Splitting an app across teams
- Independent deployments
What it does
Microfrontends is an agent skill from vercel/vercel-plugin, published by the product's own GitHub organization. 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…
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files (for example `references/configuration.md`, `references/local-development.md` and `references/managing-microfrontends.md`).
It sits in Frontend & Design, covering Deployment. It works with Vercel and Next.js. The repository describes itself as: Comprehensive Vercel ecosystem plugin — relational knowledge graph, skills for every major product, specialized agents, and Vercel conventions. Turns any AI agent into a Vercel…
When your agent uses it
- The user mentions microfrontends
- Splitting an app across teams
- Independent deployments
- Cross-app routing
Example prompts
- “/microfrontends”
What it can do on your machine
Read from SKILL.md and the folder at commit 82fa491. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
vercel
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use vercel, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Microfrontends loads about 1.3k tokens when it runs, and up to ~11k if it reads all its reference files. Until then it costs about 150 tokens; SKILL.md has 362 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 362 words (~1,303 tokens).
“Split a large application into independently deployable units that render as one cohesive app. Vercel handles routing on its global network using microfrontends.json.”
- name
- microfrontends
- metadata.priority
- 7
- metadata.docs
- https://vercel.com/docs/microfrontends
- metadata.pathPatterns
- microfrontends.json, microfrontends.jsonc, apps/*/microfrontends.json, apps/*/microfrontends.jsonc
- metadata.bashPatterns
- \bvercel\s+microfrontends\b, \bvercel\s+mf\b, \bnpm\s+(install|i|add)\s+[^\n]*@vercel/microfrontends\b…
- metadata.importPatterns
- @vercel/microfrontends
- retrieval.aliases
- microfrontends, multi-zones, multi zones, mfe, microfrontend routing, cross-zone navigation
- retrieval.intents
- split app into microfrontends, set up microfrontends, configure microfrontends.json, add path routing between projects, share layout across microfrontends
- retrieval.entities
- microfrontends.json, @vercel/microfrontends, default app, child app, asset prefix, microfrontends group
Files
SKILL.md and 7 other files (references) in skills/microfrontends of vercel/vercel-plugin.
- SKILL.md
- .vercel.approvers
- references/configuration.md
- references/local-development.md
- references/managing-microfrontends.md
- references/path-routing.md
- references/security.md
- references/troubleshooting.md
Open the folder on GitHubat commit 82fa491
Compare with similar skills
Microfrontends next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Microfrontends this skillvercel/vercel-plugin | 301 | — | ~1.3k | Automated safety check: Pass | Custom licence | |
| Next.js DeveloperJeffallan/claude-skills | 12k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Env Managerbobmatnyc/claude-mpm | 155 | — | ~2k | Automated safety check: Notes | MIT | |
| Deploy Frontendbutterbase-ai/butterbase-skills | 534 | — | ~2.8k | Automated safety check: Pass | MIT | |
| Deploy Verceljohnku2011/boilerplates-with-ai-skills | 240 | — | ~660 | Automated safety check: Notes | MIT | |
| Vercel Deploymentdavila7/claude-code-templates | 32k | 4 repos | ~534 | Automated safety check: Pass | MIT |
Similar skills
Env Manager
bobmatnyc/claude-mpm
Environment variable validation, synchronization, and management across local development, CI/CD, and deployment platforms
Deploy Frontend
butterbase-ai/butterbase-skills
A skill your agent uses when deploying a frontend (React, Next.js, or static HTML) to a live URL on Butterbase, or when troubleshooting deployment issues like MIME type errors or blank pages
Deploy Vercel
johnku2011/boilerplates-with-ai-skills
A skill your agent uses when deploying or configuring this project on Vercel — env vars, build settings, serverless limits, and production checks for Next.js or Express.
Vercel Deployment
davila7/claude-code-templates
Expert knowledge for deploying to Vercel with Next.js Use when: vercel, deploy, deployment, hosting, production.
Vercel Deployment
sickn33/agentic-awesome-skills
Expert knowledge for deploying to Vercel with Next.js. An agent skill from sickn33/agentic-awesome-skills.
More from vercel/vercel-plugin
All 38 skills in this repo- Official
Deployments Cicd
vercel/vercel-plugin
Vercel deployment and CI/CD expert guidance. An agent skill from vercel/vercel-plugin.
- Official
Plugin Audit
vercel/vercel-plugin
Audit vercel-plugin performance on real-world projects. An agent skill from vercel/vercel-plugin.
- Official
Vercel CLI
vercel/vercel-plugin
Vercel CLI expert guidance. An agent skill from vercel/vercel-plugin.
- Official
AI Gateway
vercel/vercel-plugin
Vercel AI Gateway guidance for setup, model discovery, authentication, routing, fallbacks, virtual models, evaluation models, BYOK, budgets, spend reporting, observability, compatible APIs, and…
- Official
Vercel Services
vercel/vercel-plugin
Configure and troubleshoot Vercel Services for multiple frontends and backends in one project.
- Official
Access Protected Vercel Deployment
vercel/vercel-plugin
Access and test Vercel deployments protected by Vercel Authentication, SSO, or Deployment Protection.
Related
Categories
Questions about Microfrontends
What does Microfrontends do?
Guide for building, configuring, and deploying microfrontends on Vercel. Microfrontends is an agent skill from vercel/vercel-plugin, published by the product's own GitHub organization. Guide for building, configuring, and deploying microfrontends on Vercel.
When should I use Microfrontends?
Microfrontends fits situations like: the user mentions microfrontends; splitting an app across teams; independent deployments; cross-app routing.
How do I install Microfrontends in Claude Code?
Run `npx skills add vercel/vercel-plugin --skill microfrontends -a claude-code`. Or copy the skill folder (skills/microfrontends in vercel/vercel-plugin) into .claude/skills/microfrontends in your project. Claude Code loads it when a task matches its description.
How do I install Microfrontends in Codex?
Run `npx skills add vercel/vercel-plugin --skill microfrontends -a codex`. Or copy the skill folder (skills/microfrontends in vercel/vercel-plugin) into .agents/skills/microfrontends in your project. Codex loads it when a task matches its description.
Can I use Microfrontends in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vercel/vercel-plugin --skill microfrontends -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/microfrontends, .gemini/skills/microfrontends, .github/skills/microfrontends and .opencode/skills/microfrontends in your project.
What does Microfrontends need to run?
Going by SKILL.md and its folder, Microfrontends needs the command-line tools its instructions call (vercel).
Does Microfrontends access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Microfrontends safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Microfrontends use?
Microfrontends has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Microfrontends use?
About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 10k tokens, read only when the agent opens those files.
What are the alternatives to Microfrontends?
Skills that share tags, products or a category with Microfrontends: Next.js Developer (Jeffallan/claude-skills, 12k stars), Env Manager (bobmatnyc/claude-mpm, 155 stars), Deploy Frontend (butterbase-ai/butterbase-skills, 534 stars) and Deploy Vercel (johnku2011/boilerplates-with-ai-skills, 240 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Microfrontends?
vercel (a GitHub organization, an official publisher) maintains it in vercel/vercel-plugin, which has 301 GitHub stars. The repository holds 38 skills in this directory. The repository was last updated on October 6, 2026.
Source: vercel/vercel-plugin on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.