understanding-mfe-architecture

understanding-mfe-architecture is a skill for Claude Code from lucamezzalira/mfe-skills. It costs 133 tokens per session (896 once invoked), scanned A, original, MIT.

A guide to micro-frontends, an approach where a large web interface is split into smaller front-end applications owned by different teams. It provides terms, design principles, and decision frameworks for deciding whether and how to split the interface.

In plain words
What is it for?
Use it to assess whether micro-frontends fit a project, define or review application boundaries, choose composition and routing approaches, and facilitate a Micro-Frontend Canvas discussion.
Why use it?
It helps avoid splitting a frontend along boundaries that are difficult to own, connect, or maintain. It makes team ownership, routing, composition, and communication part of the architecture decision.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Claude Code.

Part of the mfe-skills plugin — 2 skills shipped together

Good fit Use it to assess whether micro-frontends fit a project, define or review application boundaries, choose composition and routing approaches, and facilitate a Micro-Frontend Canvas discussion.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/lucamezzalira/mfe-skills/understanding-mfe-architecture
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add lucamezzalira/mfe-skills --skill understanding-mfe-architecture
Clone the repo
git clone --depth 1 https://github.com/lucamezzalira/mfe-skills

Made for: Claude Code.

Or install mfe-skills, the plugin that ships this one along with the rest of its 2 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for understanding-mfe-architecture

README.md
[![agentmods](https://agentmods.dev/badge/skills/lucamezzalira/mfe-skills/understanding-mfe-architecture/github.svg)](https://agentmods.dev/skills/lucamezzalira/mfe-skills/understanding-mfe-architecture)
Your own site
<a href="https://agentmods.dev/skills/lucamezzalira/mfe-skills/understanding-mfe-architecture"><img src="https://agentmods.dev/badge/skills/lucamezzalira/mfe-skills/understanding-mfe-architecture/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for understanding-mfe-architecture

Your own site · 80×15
<a href="https://agentmods.dev/skills/lucamezzalira/mfe-skills/understanding-mfe-architecture"><img src="https://agentmods.dev/badge/skills/lucamezzalira/mfe-skills/understanding-mfe-architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 133 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 896 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00133 $0.00896
Opus 5 $0.00067 $0.00448
Sonnet 5 $0.00027 $0.00179
Haiku 4.5 $0.00013 $0.00090

Measured 13d ago against content hash 53b12b5462e5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

understanding-mfe-architecture scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 13d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/understanding-mfe-architecture/SKILL.md · 57 lines

How it starts

The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Micro-frontend core concepts

Canonical vocabulary, principles, and decisions framework for micro-frontend architecture, as defined in Building Micro-Frontends (O'Reilly) and the Micro-Frontend Canvas (buildingmicrofrontends.com).

Task routing

Identify the task type first, then load the appropriate reference file. Do not load all files at once.

Task Load First action
Should we use MFEs? references/boundary-design.md Apply the organisational readiness gate before any implementation advice
Defining or reviewing boundaries references/boundary-design.md Ask about team ownership before discussing technology
Reviewing boundary validity or architecture for principle violations references/rules.md → or load reviewing-mfe-boundaries skill for code-level detail Run the boundary health check for validity; scan against the eight rules for violations
Choosing composition, routing, or communication references/decisions-framework.md Confirm split strategy (vertical vs horizontal) before composition; shell owns first URL segment, MFE owns sub-routes
Micro-Frontend Canvas facilitation Install micro-frontend-canvas skill (see references/canvas-pointer.md) Confirm domain is identified; do not facilitate Canvas from this skill
Generating or reviewing MFE code Load reviewing-mfe-boundaries skill This skill handles code-level boundary enforcement

If the user's terminology differs from the canonical definitions in the reference files, map it once to the canonical term, then continue using theirs.

Do not revert to generic frontend advice once this skill is active. Micro-frontend principles apply at the boundary between independently deployed units — not within a single unit.

When not to activate

Stand down if the question is purely about component composition, state management within a single deployed unit, or build tooling with no independent-deployment or team-scaling angle.


Examples

Read the full file on GitHub · 57 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 13d ago First seen · 57 lines · 133 tokens per session scan A 53b12b5462e5

Subscribe to this mod's changes

understanding-mfe-architecture is a skill published in the GitHub repository lucamezzalira/mfe-skills (51 stars, last pushed 17d ago), licensed MIT. It adds 133 tokens to every session and 896 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

visual-ralph

Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.

Yeachan-Heo/oh-my-codex · 52 tokens

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

create-site

Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…

microsoft/power-platform-skills · 73 tokens

prototype-web

A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.

nexu-io/html-anything · 24 tokens

menu-transitions-rtl

Animate react-horizontal-scrolling-menu scrolling and build right-to-left menus: noPolyfill defaults to true since v8, so transitionDuration (default 500), a custom-easing-function transitionBehavior, and per-call ScrollOptions { duration, boundary } on scrollToItem/scrollNext/scrollPrev are silently ignored unless…

asmyshlyaev177/react-horizontal-scrolling-menu · 137 tokens