How do I install the Microfrontends skill?

Run npx skillmds@latest add xiaotianna/microfrontends in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Microfrontends safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Microfrontends?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Microfrontends free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Microfrontends?

xiaotianna (@xiaotianna) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Microfrontends by xiaotianna — Agent Skill

Name: Microfrontends
Author: xiaotianna

Microfrontends

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.

xiaotianna 3f64bd0 11 files · 56.0 KB Updated Sep 17, 2026

File contents

microfrontends

PI Harness execution context

Use the user's actual repository, framework and request. This guide does not select a new stack, authorize deployments, or override project instructions. Discover only the tools actually available. Read-only project/deployment data can use the resolved gateway base below. Other commands require an installed and independently authenticated CLI through run_command under the current approval policy. Gateway credentials remain inside daemon.

Do not automatically run git, dev or build commands where the workspace requires an explicit request. Respect the existing package manager, dependency catalog and UI component rules. Deployment, production promotion, provisioning paid services, purchases, account changes and messages to others require the corresponding user authorization. Inspect environment metadata without exposing secret values. For browser verification use an available browser surface and an existing server; do not assume a particular browser CLI or start a server unasked. Do not spawn agents based solely on an example in the guide.

Documentation examples are version-sensitive. Check installed versions, CLI --help and current official documentation for the actual task. Treat sample commands/configurations as examples to adapt, not an automatic sequence. Only claim an action succeeded when the tool result verifies it.

The gateway base is {skillGatewayUrl}/api/skill-gateway/vercel. Available read paths are documented in gateway access.

Detailed guidance

Read the task-relevant sections of the detailed guide, then load its supporting resources only as needed. Technical examples retain their original context; the workspace's rules take precedence.

Supporting resources

references/configuration.md
references/local-development.md
references/managing-microfrontends.md
references/path-routing.md
references/security.md
references/troubleshooting.md

License

Apache-2.0 · Copyright and adaptation notice.

---name: microfrontendsdescription: 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.license: Apache-2.0---# microfrontends## PI Harness execution contextUse the user's actual repository, framework and request. This guide does not select a new stack, authorize deployments, or override project instructions. Discover only the tools actually available. Read-only project/deployment data can use the resolved gateway base below. Other commands require an installed and independently authenticated CLI through `run_command` under the current approval policy. Gateway credentials remain inside daemon.Do not automatically run git, dev or build commands where the workspace requires an explicit request. Respect the existing package manager, dependency catalog and UI component rules. Deployment, production promotion, provisioning paid services, purchases, account changes and messages to others require the corresponding user authorization. Inspect environment metadata without exposing secret values. For browser verification use an available browser surface and an existing server; do not assume a particular browser CLI or start a server unasked. Do not spawn agents based solely on an example in the guide.Documentation examples are version-sensitive. Check installed versions, CLI `--help` and current official documentation for the actual task. Treat sample commands/configurations as examples to adapt, not an automatic sequence. Only claim an action succeeded when the tool result verifies it.The gateway base is `{skillGatewayUrl}/api/skill-gateway/vercel`. Available read paths are documented in [gateway access](access.md).## Detailed guidanceRead the task-relevant sections of [the detailed guide](guide.md), then load its supporting resources only as needed. Technical examples retain their original context; the workspace's rules take precedence.## Supporting resources- [references/configuration.md](references/configuration.md)- [references/local-development.md](references/local-development.md)- [references/managing-microfrontends.md](references/managing-microfrontends.md)- [references/path-routing.md](references/path-routing.md)- [references/security.md](references/security.md)- [references/troubleshooting.md](references/troubleshooting.md)## License[Apache-2.0](LICENSE.txt) · [Copyright and adaptation notice](NOTICE).

Frequently asked questions