run-local

Start the Aspire AppHost locally with preflight checks and optional frontend launch.

2|Updated Dec 9, 2025
One-click install
npx skills add https://github.com/signalbeam-io/signalbeam-edge --skill run-local
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-local
Source: https://github.com/signalbeam-io/signalbeam-edge/tree/main/.claude/skills/run-local
Command: npx skills add https://github.com/signalbeam-io/signalbeam-edge --skill run-local

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Start and manage a local development environment for the Aspire AppHost.

Core Features & Use Cases

  • Preflight checks verify Docker and .NET SDK availability.
  • One-command startup flow launches the Aspire AppHost; optionally starts the frontend.
  • Local development validation ensures services are reachable and dashboards can be opened.

Quick Start

Start the local development environment by launching the Aspire AppHost and, if needed, the frontend, then verify services are running.

Frequently Asked Questions about run-local

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

FAQPage Schema
How do I start the local .NET Aspire AppHost development environment?

Running .NET Aspire locally with backend and frontend services uses a one-command startup flow that launches the Aspire AppHost, optionally starts the frontend, and validates that local services are reachable.

Do I need Docker and .NET SDK installed to run the Aspire AppHost locally?

Yes, you need Docker and .NET SDK installed to run the Aspire AppHost locally. The startup process performs preflight checks to verify both Docker and .NET SDK availability before launching the environment.

What preflight checks are required for .NET Aspire local development?

Preflight checks for .NET Aspire local development verify Docker and .NET SDK availability to ensure the local development environment has the required dependencies before attempting to launch the Aspire AppHost.

Why is my local Aspire AppHost not working or exposing services on local ports?

If your local Aspire AppHost is not working, it may be due to failed preflight checks for Docker and .NET SDK, or services not being reachable. The startup flow includes local development validation to ensure services are running and dashboards can be opened.

Can I validate that local Aspire services are reachable and dashboards can be opened?

Yes, you can validate that local Aspire services are reachable and dashboards can be opened. The startup process includes local development validation that ensures exposed services on local ports are running and accessible.