What problem does it solve? AI agents working in Aspire projects often 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 orchestrated apps without breaking the build or leaving stray processes. ## 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: Diagnoses MSB3491 and CS2012 build errors as Aspire-held locks and prescribes aspire stop as the single correct recovery step. - Project Detection & Routing: Fingerprints C#, file-based, and TypeScript AppHosts, then hands off AppHost wiring to the aspireify skill and deployment to aspire-deployment. - Use Case: An agent hits "error MSB3491: Could not write to output file" while building a service. Instead of deleting bin/obj or declaring the project broken, it runs aspire stop, rebuilds, and restarts with aspire start. ## Quick Start Start my Aspire app in the background and wait until the API resource is ready before running any requests against it.
