janpereira-dev/ngautopilot/angular-architecture-micro-frontends-communication-patterns
Claude Code and agent skill by janpereira-dev/ngautopilot
- community
Checking that the SKILL.md file is still in the repository.
Evaluates communication patterns between Angular micro-frontends in Nx monorepos, focusing on explicit contracts, low coupling, shared state limits, and safe cross-remote event flow.
Install
npx vskill@latest install janpereira-dev/ngautopilot/angular-architecture-micro-frontends-communication-patternsSKILL.md
The same SKILL.md was published earlier as janpereira-dev/ngautopilot/angular-architecture-micro-frontends-communication-patterns.
Micro-frontends Communication Patterns
Purpose
Use this skill to evaluate or design communication patterns between Angular micro-frontends.
Micro-frontends should communicate through explicit contracts, not accidental shared state. The goal is to keep integrations predictable, typed where possible, and easy to reason about at the shell and remote boundaries.
The core rule is simple:
When to Use
Use this skill when:
- a shell needs to receive events from remotes
- one remote needs to notify the shell about user intent
- two remotes appear to need coordination
- URL state, events, or shared state are being evaluated
- a global event bus or pub/sub system is under consideration
- cross-remote communication is becoming hard to trace
Do
Prefer the narrowest communication mechanism that fits the problem:
Use URL state for navigable or shareable context:
Use custom events for low-coupling intent:
Keep shared state minimal:
Define event contracts explicitly:
Do Not
Avoid a global bus without a contract.
Avoid sharing feature state across remotes.
Avoid direct imports from one remote into another remote.
Avoid using shared state for business rules owned by a single domain.
Avoid communication patterns that cannot be traced in debugging or tests.
Review Checklist
- [ ] The communication mechanism is the simplest one that fits the use case.
- [ ] Events and payloads are documented.
- [ ] Shared state is limited to transversal concerns.
- [ ] Remote-to-remote imports are avoided.
- [ ] The shell remains the coordination point where appropriate.
- [ ] The chosen pattern is testable and observable.
Expected Output
- Classify the communication need.
- Recommend the narrowest viable pattern.
- Define event or URL contracts explicitly.
- Flag hidden coupling or shared-state overreach.
- Suggest fallback and test coverage for the communication path.
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingplugins/ngautopilot-angular/skills/angular--architecture--micro-frontends-communication-patterns/SKILL.md
Popularity
- Repository stars
- 5
- Repository forks
- 1
- 7-day trend score
- 13
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/janpereira-dev/ngautopilot/angular-architecture-micro-frontends-communication-patterns)