add-microfrontend

Create micro-frontend components with iframe composition and shared Supabase authentication.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/Alif-N/fe-sima-arome --skill add-microfrontend
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-microfrontend
Source: https://github.com/Alif-N/fe-sima-arome/tree/main/.agents/skills/add-microfrontend
Command: npx skills add https://github.com/Alif-N/fe-sima-arome --skill add-microfrontend

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires next, supabase, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the setup of a micro-frontend architecture using client-side iframe composition, allowing for seamless integration of independent apps with shared authentication, backend, and rendering.

Core Features & Use Cases

  • Micro-Frontend Architecture: Set up a micro-frontend architecture with a Main App hosting micro-apps via iframes.
  • Shared Backend: Utilize a single shared DaaS backend for all apps, simplifying data management and access control.
  • Shared Authentication: Share authentication state between the Main App and micro-apps using Supabase session cookies.
  • URL Synchronization: Keep the Main App's URL in sync with micro-app changes using postMessage communication.
  • Use Case: Ideal for organizations looking to build a scalable, modular application interface, particularly useful for embedding third-party services or integrating separate team projects.

Quick Start

Use the add-microfrontend skill to create a new micro-frontend within the existing application architecture.

Frequently Asked Questions about add-microfrontend

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a micro-frontend architecture with shared authentication in Next.js?

To set up a micro-frontend architecture with shared authentication in Next.js, this Skill automates client-side iframe composition and shares Supabase session cookies between the Main App and micro-apps.

What is client-side iframe composition for micro-frontends?

Client-side iframe composition is an architectural approach where a Main App hosts independent micro-apps within iframes, enabling seamless integration, shared backend data, and independent deployments without complex build configurations.

Do I need Supabase to share authentication state across micro-apps?

Yes, you need Supabase to share authentication state across micro-apps. The architecture relies on Supabase session cookies to maintain a unified authentication flow between the Main App and its embedded iframe components.

How do I synchronize the main app URL with micro-frontend iframe changes?

To synchronize the main app URL with micro-frontend iframe changes, the architecture uses postMessage communication, ensuring the Main App's URL stays updated when users navigate within the embedded micro-apps.

Can I use a single backend for multiple independent Next.js micro-apps?

Yes, you can use a single shared DaaS backend for multiple independent Next.js micro-apps. This approach simplifies data management and access control across all integrated applications.

What are the limitations of using iframe composition for Next.js micro-frontends?

Iframe composition for Next.js micro-frontends requires client-side rendering and postMessage communication for URL synchronization, making it less suitable for applications needing server-side rendering or complex native cross-app state sharing.