What problem does it solve? AI agents working in 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, inspect, and stop orchestrated apps without breaking the developer environment. ## Core Features & Use Cases - Safe Lifecycle Management: Enforces aspire start, aspire wait, aspire stop, and aspire ps instead of dotnet run, curl polling loops, or manual process kills. - File-Lock Recovery: Provides a deterministic recovery sequence (aspire stop first) for MSB3491/CS2012 build errors caused by Aspire holding output assemblies. - Project Detection & Routing: Detects C#, file-based C#, and TypeScript AppHosts via SDK references, apphost.ts, aspire.config.json, and .aspire/ directories, then hands off wiring work to sibling skills like aspireify. - Use Case: An agent hits "error MSB3491: Could not write to output file" while building a service. Instead of deleting bin/ or declaring the project broken, it runs aspire stop, rebuilds, and restarts with aspire start. ## Quick Start Ask the agent to start your Aspire app in the background and wait until the API resource is ready before running any requests against it.