What problem does it solve? Teams often adopt micro-frontends or complex frontend architectures on hype rather than evidence, then pay for it in coordination overhead, duplicated dependencies, and broken deployability. This Skill reviews a proposed or existing frontend architecture against a twelve-point scale checklist and returns an honest adopt-or-don't-adopt verdict before code is written. ## Core Features & Use Cases - Micro-frontend adoption gate: Defaults against adoption unless three or more independently deploying teams, real coordination pain, and domain-aligned boundaries all exist; otherwise recommends a modular monolith. - Twelve-point architecture checklist: Covers team and domain boundaries, independent deployability, governed shared dependencies, design-system sharing, runtime isolation, cross-app communication, routing and composition tier, rendering strategy, state at scale, performance budgets, and governance with failure handling. - Capability-routed review: Works with any frontend stack, naming frameworks or federation tools only when the task already chose them, and grounding tool-specific claims in captured references rather than memory. - Use Case: Before splitting a growing React monolith into federated remotes, run this review to get a verdict on whether micro-frontends are warranted and findings on each boundary, route, and shared dependency. ## Quick Start Ask the assistant to run frontend-architecture-review on the active task folder to evaluate the proposed frontend architecture and decide whether micro-frontends are justified.
