What problem does it solve? It guides the setup of a micro-frontend architecture where a Main App hosts independent Next.js micro-apps inside sandboxed iframes, sharing one Supabase Auth instance and one DaaS backend without bundling micro-app code. ## Core Features & Use Cases - Iframe Composition: Creates a reusable MicroappIframe component with sandbox permissions, loading skeletons, error boundaries, and strict postMessage origin validation. - Cross-Domain Auth Bridge: Implements a MICROAPP_NEEDS_AUTH / SET_AUTH token handshake so micro-apps deployed on separate Amplify subdomains inherit the host's Supabase session without re-login. - URL Syncing: Syncs allowlisted query params between micro-app and host URL bar via debounced postMessage, plus auto-generated config/app-urls.ts from the get_project_detail MCP tool. - Use Case: A platform team adds a new "users-app" micro-frontend to an existing admin dashboard; the skill scaffolds the host route page, iframe wrapper, auth bridge, environment config, and Playwright tests. ## Quick Start Ask the assistant to add a micro-frontend named users-app hosted at the /admin/users route using the add-microfrontend skill.