What problem does it solve? AI agents working in .NET Aspire projects frequently cause file locks (MSB3491, CS2012), port conflicts, and orphaned processes by using dotnet run or dotnet build against a running AppHost. This Skill enforces safe Aspire CLI workflows so agents start, wait on, inspect, and stop orchestrated apps without breaking the build or leaving stray processes. ## Core Features & Use Cases - Safe Lifecycle Management: Enforces aspire start / aspire stop / aspire wait instead of dotnet run, curl polling loops, or manual process kills. - File-Lock Recovery: Provides a deterministic recovery sequence (aspire stop first) for MSB3491 and CS2012 build errors caused by Aspire holding output assemblies. - Project Detection: Fingerprints C# AppHosts (Aspire.AppHost.Sdk), file-based AppHosts (apphost.cs), TypeScript AppHosts (apphost.ts), and aspire.config.json to confirm a workspace is Aspire-managed. - Use Case: An agent editing a .NET service while the AppHost runs hits "Cannot open ... for writing"; the Skill directs it to run aspire stop, rebuild, and restart rather than deleting bin//obj/ or declaring the project broken. ## Quick Start Ask the agent to start my Aspire app in the background and wait until the API resource is ready before running any requests against it.