What problem does it solve? After aspire init drops an empty AppHost skeleton, developers must manually figure out how to model their services, databases, and frontends as Aspire resources. This Skill automates that wiring: it scans the repo, proposes a resource graph, edits the AppHost (C#, file-based C#, or TypeScript), wires ServiceDefaults and OpenTelemetry, and validates everything with aspire start. ## Core Features & Use Cases - Repo Scanning & Resource Graph Proposal: Detects .NET projects, Node/Python services, docker-compose dependencies, and hardcoded connection strings, then proposes a resource graph for user confirmation before editing. - Multi-Language AppHost Authoring: Edits SDK-style C# (Program.cs), file-based C# (apphost.cs), or TypeScript (apphost.ts) AppHosts using verified APIs from aspire docs lookups, with a hard refusal to edit generated .aspire/modules/ files. - End-to-End Validation & Self-Deactivation: Runs aspire start --non-interactive, waits on each resource, and hands off to orchestration skills once the app starts cleanly. - Use Case: You just ran aspire init in a repo with a .NET API, a Next.js frontend, and Postgres in docker-compose. This Skill detects all three, proposes AddPostgres + AddProject + AddNextJsApp wiring with WithReference and WaitFor, migrates your .env connection strings into Aspire parameters, and validates the full stack starts healthy. ## Quick Start Ask the assistant to wire up the Aspire AppHost for this repository and scaffold the resource graph after aspire init.