What problem does it solve? AI agents working in Aspire projects frequently cause file locks, orphaned processes, and port conflicts by running dotnet run or dotnet build against a live AppHost. This Skill enforces safe Aspire CLI workflows so agents start, wait on, inspect, and stop distributed applications without corrupting the development environment. ## Core Features & Use Cases - Safe Lifecycle Management: Enforces aspire start, aspire wait, aspire stop, and resource-scoped commands instead of dangerous dotnet run or manual process kills. - File-Lock Recovery: Provides a deterministic recovery sequence for MSB3491 and CS2012 build errors caused by Aspire holding locks on bin/ and obj/ outputs. - Project Detection: Fingerprints C#, file-based C#, and TypeScript AppHosts via SDK references, apphost files, and aspire.config.json. - 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.