Individual skill
micro-frontends-pro
Architect micro-frontends: module federation, single-spa, routing, shared dependencies, and team autonomy patterns. Use for large apps split across teams.
skills/micro-frontends-pro/SKILL.md
Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 8, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 54
- Repository last updated
- Oct 10, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- ai-agents-automation Repository topic
- ai-skills Repository topic
- awesome Repository topic
- awesome-list Repository topic
- chatgpt Repository topic
- claude-skills Repository topic
- meta-ai Repository topic
- muse-ai Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 5,824 bytes
Read excerpt
# Micro-Frontends Pro
A practical guide to micro-frontends: splitting a large frontend across teams — integration approaches (Module Federation, single-spa, iframes, web components), shared dependencies, routing, and the organizational patterns that make it work.
## Overview
Micro-frontends apply microservices thinking to UI: **independently deployable frontend slices owned by different teams**, composed into one product. The technical challenge is integration (how slices compose at runtime); the real challenge is organizational ( Conway's law, contracts, versioning). Only adopt when team scale demands it — the complexity tax is real.
## When to use
- Large products with multiple teams stepping on each other's deploys.
- Incremental migration (strangler fig) from a legacy frontend.
- Truly independent team ownership of product areas.
- NOT for: small teams, simple products, or "it sounds cool" (a modular monolith is better).