mfe-skills / rules
Cursor rule53 starsChanged 39 days agoMITView on GitHub
Micro-frontend architecture: Micro-Frontend Canvas — external skill. Load when this topic is in scope; part of mfe-skills.
We split this mfe-architecture-canvas-pointer.mdc into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
Use the dedicated micro-frontend-canvas skill (separate repository):
- Distinctive: line 32
Do not load full Canvas facilitation content from this repo.
≈ “Common” is an estimate: at least 1 in 5 of the 6,350 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
--- description: Micro-frontend architecture: Micro-Frontend Canvas — external skill. Load when this topic is in scope; part of mfe-skills. alwaysApply: false --- # Micro-Frontend Canvas — external skill **Version**: 1.0 | **Skill**: understanding-mfe-architecture This repository covers boundary **governance** (eight rules, review, routing, composition decisions). The **Micro-Frontend Canvas** — worksheet structure, facilitation steps, and iteration templates — is maintained in a **separate skill**. ## When to use the Canvas skill (not this repo) - The team has identified a domain but has not documented implementation decisions per MFE - Cold start is blocked: ownership or boundary is unclear before code - You need a facilitated session: one micro-frontend, one canvas iteration ## When to stay in mfe-skills - Adoption and organisational readiness - Boundary validity and the eight rules - Shell/MFE integration review and remediation - URL routing ownership and platform vs domain events ## Install the Canvas skill Use the dedicated **micro-frontend-canvas** skill (separate repository): - Repository: https://github.com/lucamezzalira/mfe-canvas - Learn more: https://www.buildingmicrofrontends.com Do not load full Canvas facilitation content from this repo. If the Canvas skill is not installed, tell the user to install it before running a Canvas session. ## Canvas threshold (defined here) Governance in this repo still uses the **Canvas threshold**: fewer than 5 props exposed to the container, identifiers not domain objects. Validate that in `boundary-design.md` and `reviewing-mfe-boundaries`. The worksheet itself belongs in the Canvas skill.
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 3,978 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/mfe-architecture-boundary-design.mdcCursor rule
- .cursor/rules/mfe-architecture-decisions.mdcCursor rule
- .cursor/rules/mfe-architecture.mdcCursor rule
- .cursor/rules/mfe-architecture-rules-ref.mdcCursor rule
- .cursor/rules/mfe-boundary-code-patterns.mdcCursor rule
- .cursor/rules/mfe-boundary-remediation.mdcCursor rule
- .cursor/rules/mfe-boundary-review.mdcCursor rule
- .cursor/rules/mfe-boundary-routing.mdcCursor rule
- .cursor/rules/mfe-boundary-rules-core-critical.mdcCursor rule
- .cursor/rules/mfe-boundary-rules-core-standard.mdcCursor rule
- .cursor/rules/mfe-boundary-toolchain.mdcCursor rule
- reviewing-mfe-boundariesSkill
- understanding-mfe-architectureSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.