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.
git clone --depth 1 https://github.com/lucamezzalira/mfe-skillsWrote 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.
[](https://agentmods.dev/rules/lucamezzalira/mfe-skills/mfe-architecture-boundary-design)<a href="https://agentmods.dev/rules/lucamezzalira/mfe-skills/mfe-architecture-boundary-design"><img src="https://agentmods.dev/badge/rules/lucamezzalira/mfe-skills/mfe-architecture-boundary-design/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.
<a href="https://agentmods.dev/rules/lucamezzalira/mfe-skills/mfe-architecture-boundary-design"><img src="https://agentmods.dev/badge/rules/lucamezzalira/mfe-skills/mfe-architecture-boundary-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.01781 | $0.01781 |
| Opus 5.5 | $0.00712 | $0.00712 |
| Sonnet 5.5 | $0.00356 | $0.00356 |
| Haiku 4.5 | $0.00178 | $0.00178 |
Grade A, and why
mfe-architecture-boundary-design 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Boundary design
Contents
- The canonical definition
- The seven principles
- Organisational readiness gate
- Identifying boundaries with domain-driven design
- Boundary testing heuristic
- Additional boundary guardrails
- The Micro-Frontend Canvas
Version: 1.2 | Skill: understanding-mfe-architecture | Source: Building Micro-Frontends (O'Reilly) and the Micro-Frontend Canvas
The canonical definition
A micro-frontend represents a business subdomain that is autonomous, independently deliverable, with the same or different technology, with a low degree of coupling, and owned by a single team.
Six characteristics follow directly from this definition:
- Business domain representation — models a subdomain, not a technical layer or UI component type
- Autonomous codebase — built and maintained without coordinating with other teams
- Independent deployment — shipped without requiring other teams to act
- Low coupling — minimal external dependencies; changes inside do not cascade outside
- Optimised for fast flow — team can iterate and release at its own cadence
- Single-team ownership — one team owns design, development, deployment, and operations end-to-end
The critical distinction from components: a component addresses a technical challenge through abstraction and reusability. A micro-frontend completely owns a business domain and is not designed for reuse. If you can reuse it everywhere, it is probably a component. If it represents a domain and can live on its own, it is a micro-frontend.
The seven principles
Adapted from microservices architecture. When reviewing or generating architecture, check it against each one.
1. Modelled around business domains — identify boundaries by user journey steps (checkout, search, profile) or business capabilities, not by technical framework types or component categories. DDD event storming is the recommended technique for identifying subdomains.
2. Culture of automation — a poor automation culture makes micro-frontends a nightmare. Every independent unit needs solid CI/CD pipelines with a fast feedback loop. Automation also enforces guardrails: bundle size limits, dependency alignment, design system version enforcement, and architecture fitness functions (for example no cross-MFE imports except explicit shared allowlists).
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.
- 1mo ago Changed · +10 lines · +47 tokens per session 5b12a94b4770
- 2mo ago First seen · 120 lines · 1,734 tokens per session scan A d0ed9760e2fa
mfe-architecture-boundary-design is a cursor rule published in the GitHub repository lucamezzalira/mfe-skills (53 stars, last pushed 1mo ago), licensed MIT. It adds 1,781 tokens to every session, about $0.0071 per session on Opus 5.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.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.