env-standalone

Generate a .env.standalone file for micro-frontend applications without the single-spa launcher.

Updated Nov 20, 2025
One-click install
npx skills add https://github.com/sayali-ingle-pdl/adusa-ai-vuejs-app-template --skill env-standalone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: env-standalone
Source: https://github.com/sayali-ingle-pdl/adusa-ai-vuejs-app-template/tree/main/.github/agents/app-starter/agents-context/skills/env-standalone
Command: npx skills add https://github.com/sayali-ingle-pdl/adusa-ai-vuejs-app-template --skill env-standalone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate a dedicated .env.standalone file to run micro-frontend applications in standalone mode without the single-spa launcher, streamlining local development.

Core Features & Use Cases

  • Generates the .env.standalone file when the application_type is set to "micro-frontend".
  • Provides a toggleable setup for standalone development, ensuring micro-frontends mount independently of a launcher.
  • Keeps the file safe to commit (no secrets) and aligns with standard npm/yarn dev workflows.

Quick Start

Set application_type to "micro-frontend" and run your development script to generate the .env.standalone file.

Frequently Asked Questions about env-standalone

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

FAQPage Schema
How do I run a micro-frontend in standalone mode without the single-spa launcher?▼

Generate a .env.standalone file to enable standalone mode for your micro-frontend. This file provides a toggleable setup allowing the application to mount independently of the single-spa launcher during development workflows.

How do I generate a .env.standalone file for my micro-frontend?▼

To generate a .env.standalone file, set application_type to "micro-frontend" and run your development script. The file is output accordingly, enabling standalone mode for local development and testing.

Can I use standalone mode for micro-frontend development and testing workflows?▼

Yes, generating a .env.standalone file enables standalone mode for both development and testing workflows. This allows micro-frontends to mount independently of the single-spa launcher, streamlining local development.

Do I need a specific application_type to enable standalone mode?▼

Yes, application_type must be set to "micro-frontend". The Skill requires this setting to generate the .env.standalone file accordingly, enabling standalone mode for development and testing.

Is the .env.standalone file safe to commit to version control?▼

Yes, the .env.standalone file is safe to commit because it contains no secrets. It aligns with standard npm and yarn dev workflows while providing a toggleable setup for standalone micro-frontend development.

Why does my micro-frontend need a .env.standalone file?▼

Your micro-frontend needs a .env.standalone file to enable standalone mode, allowing it to mount independently without the single-spa launcher. This streamlines local development by providing a toggleable configuration setup.