What problem does it solve? Working with Aspire distributed applications requires knowing which CLI command and workflow fits each task, and falling back to ad-hoc dotnet, docker, or shell commands causes errors and unsafe operations. This Skill detects an Aspire AppHost in the repository, enforces safety guardrails, and routes every task to the correct specialized sub-skill. ## Core Features & Use Cases - AppHost Detection: Identifies C# (.csproj with Aspire.AppHost.Sdk), file-based C# (apphost.cs), and TypeScript (apphost.ts) AppHosts, plus aspire.config.json and .aspire/ directory signals. - Task Routing: Directs lifecycle operations to aspire-orchestration, deployments to aspire-deployment, observability to aspire-monitoring, and first-run setup to aspire-init or aspireify. - Safety Guardrails: Enforces rules such as always using aspire start instead of dotnet run, always using aspire wait before interacting with resources, and always passing --non-interactive for agent execution. - Use Case: You open a repository containing an Aspire AppHost and ask to restart a single Redis resource. The Skill detects the AppHost, routes to aspire-orchestration, and uses aspire resource commands instead of restarting the entire application. ## Quick Start Ask the assistant to start the Aspire AppHost in this repository and wait until all resources are healthy before making changes.