Agent skill
env-standalone
Conditionally generates .env.standalone file for micro-frontend applications only. Enables running micro-frontends in standalone mode without single-spa launcher. Skipped for standalone applications.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/env-standalone
SKILL.md
Environment Standalone Skill
Purpose
Generate .env.standalone file for running micro-frontend applications in standalone mode (without single-spa launcher).
Note: This file should ONLY be created for micro-frontend applications (application_type: "micro-frontend"). Standalone applications do NOT need this file.
Input Parameters
application_type: Should be "micro-frontend" to generate this file
Output
Create the file: .env.standalone (only if application_type === "micro-frontend")
Notes
- Micro-Frontend Only: This file is only relevant for micro-frontend applications
- Standalone Apps: Do NOT create this file for standalone applications
.env.standaloneenables standalone mode for development without the launcher- When
STANDALONE_SINGLE_SPA=true, the micro-frontend app runs independently - Useful for local development and testing without single-spa dependencies
- This file can be committed to the repository (no secrets)
- Use with
npm run dev:standaloneor similar script (if using Vite modes) - The application will mount directly without waiting for single-spa lifecycle
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?