microfrontend-architectlisted

# Microfrontend Architect Microfrontends solve an organizational problem with a technical mechanism. Most failed implementations fail because someone applied the mechanism without having the problem. The first job of this skill is therefore to check the fit, and the second is to build the thing properly if the fit is real. ## Step 1 — Check whether microfrontends are the right answer Ask about, or infer from the repo: | Signal | Microfrontends help | Microfrontends hurt | |---|---|---| | Team count | 3+ teams shipping independently | 1 team, one release train | | Deploy coupling | Release blocked waiting on other teams | Deploys are already fast and independent | | Domain edges | Clear bounded contexts (checkout, search, admin) | Heavy shared state across every screen | | Tech drift | Legacy Angular/React mix to strangle incrementally | Uniform stack, no migration pressure | | Ops maturity | Can run several pipelines and CDNs | No CI budget, one deploy pipeline | If most signals sit in the right-hand column, say so directly and propose the cheaper alternative — an Nx monorepo with enforced module boundaries and lazy-loaded routes gives most of the code-ownership benefit at a fraction of the runtime cost. Recommending against microfrontends when they do not fit is a correct outcome for this skill, not a failure to complete the task. ## Step 2 — Choose the composition model Three models, and the choice drives everything downstream: **Build-time composition** — remotes p