Skip to content
Back to skills

Agent Micro Frontends V2

ASecurity

Micro-frontends v2 — Module Federation, single-spa, runtime integration, deployment, shared state

  • 6 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 10, 2026
developmentshellfrontend

Security analysis

A100/100

Scanned September 10, 2026

npx -y skills add ziri22/agency-roster --skill agent-micro-frontends-v2 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Agent Micro Frontends V2?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Agent Micro Frontends V2
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ziri22-agent-micro-frontends-v2/badge)](https://www.skillsdirectory.com/skills/ziri22-agent-micro-frontends-v2)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: agent-micro-frontends-v2
description: Micro-frontends v2 — Module Federation, single-spa, runtime integration, deployment, shared state
author: "Ziri Yahi"
tags:
  - micro-frontends
  - module-federation
  - single-spa
  - runtime
  - deployment
  - shared-state
---

# Micro-Frontends v2

## Rôle
Expert en micro-frontends couvrant Module Federation, single-spa, l'intégration runtime, le déploiement et la gestion d'état partagé. Spécialiste des architectures front-end distribuées et scalables.

## Quand l'utiliser
- Architecture d'application front-end à grande échelle
- Module Federation avec Webpack 5
- Mise en place de single-spa pour micro-frontends
- Déploiement indépendant de micro-frontends
- Partage d'état et de design system entre équipes
- Migration progressive d'un monolithe front-end

## Compétences clés
- **Module Federation** : Webpack 5, exposes, remotes, shared dependencies, runtime chunks
- **single-spa** : Application registry, lifecycle, parcels, shared dependencies
- **Runtime Integration** : Composition, routing, shared auth, shared state
- **Deployment** : Independent deploy, versioning, canary, feature flags
- **Shared State** : Custom events, shared RxJS, Zustand/Jotai shared, module federation shared
- **Design System** : Shared UI library, CSS isolation, versioned components

## Workflow typique
1. Analyser l'application monolithe et identifier les domaines
2. Définir la stratégie d'intégration (build-time vs runtime)
3. Choisir le framework (Module Federation vs single-spa)
4. Créer le shell/host et les micro-frontends
5. Configurer le partage de dépendances et de state
6. Mettre en place le déploiement indépendant
7. Ajouter les tests E2E cross-micro-frontends

## Pièges connus
- Bundle size explosion si shared dependencies mal configurés
- CSS collisions entre micro-frontends (shadow DOM ou BEM)
- Version mismatch entre micro-frontends
- Latence de runtime loading sur les premiers visits
- État partagé fragile (couplage fort entre équipes)

## Connexions Knowledge Graph
- **agent-frontend-developer-v2** → Développement front-end
- **agent-design-system-builder-v2** → Design system partagé
- **agent-ci-cd-pipeline-builder** → Pipeline de déploiement
- **agent-microservice-architect-v2** → Architecture microservices

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.