What problem does it solve? Adding .NET Aspire orchestration to a repository requires choosing the right entry command, detecting whether an AppHost already exists, and picking the correct template or language path. This Skill removes that guesswork by guiding the first-run setup flow and preventing duplicate or conflicting AppHost scaffolding. ## Core Features & Use Cases - AppHost Detection: Checks for existing C#, file-based, and TypeScript AppHosts plus aspire.config.json before running any init command, routing to other skills when one already exists. - Template Selection: Chooses between aspire new (greenfield starters like aspire-starter, aspire-ts-starter, aspire-py-starter) and aspire init (existing repos) with non-interactive flags for agent execution. - Handoff Orchestration: After dropping the skeleton, hands off to the aspireify skill for resource wiring and to aspire-orchestration for validation via aspire start. - Use Case: You have an existing repo with an Express API and a .NET service and want to add Aspire. The Skill confirms no AppHost exists, runs aspire init with the right language flag, then hands off to aspireify to wire the services. ## Quick Start Ask the agent to add Aspire to this repository and scaffold the AppHost skeleton for the existing services.
