What problem does it solve? Adding Aspire orchestration to a repository requires choosing between greenfield templates and existing-repo initialization, detecting whether an AppHost already exists, and knowing which follow-up steps to run. This Skill guides that first-run flow so the correct skeleton is dropped without duplicating existing AppHosts. ## Core Features & Use Cases - AppHost Detection: Checks for existing C#, file-based, and TypeScript AppHosts plus aspire.config.json before running any init command. - Template Selection: Chooses between aspire new templates (aspire-starter, aspire-empty, aspire-py-starter, aspire-ts-starter) for new projects or aspire init for existing repositories. - Handoff Orchestration: Routes to the aspireify skill for resource wiring and aspire-orchestration for lifecycle commands after the skeleton is in place. - Use Case: A developer has an existing Express API and .NET service repo with no Aspire support. The Skill confirms no AppHost exists, runs aspire init with the correct language flag, and hands off to aspireify to wire the services. ## Quick Start Add Aspire to my existing repository by scaffolding an AppHost skeleton and then wiring up my services.
