What problem does it solve? Working with Aspire 13.4 distributed applications requires knowing which CLI command or workflow applies to each task, and falling back to ad-hoc dotnet, docker, or shell commands often breaks the AppHost model. This Skill detects Aspire projects, enforces safety guardrails, and routes every task to the correct sub-skill. ## Core Features & Use Cases - AppHost Detection: Identifies C#, file-based C#, and TypeScript AppHosts via project files, apphost.cs, apphost.ts, aspire.config.json, and .aspire directories. - Task Routing: Directs lifecycle operations to aspire-orchestration, deployments to aspire-deployment, observability to aspire-monitoring, and bootstrap or wiring work to aspire-init and aspireify. - Safety Guardrails: Enforces rules like always using aspire start instead of dotnet run, aspire wait before interacting with resources, and --non-interactive for agent execution. - Use Case: When you open a repo containing an Aspire AppHost and ask to restart a single failing resource, the Skill detects the AppHost, blocks a full AppHost restart, and routes to aspire-orchestration for a targeted resource command. ## Quick Start Ask the agent to start my Aspire AppHost and wait until the database resource is healthy before running the API.