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 handle resource wiring. This Skill automates that first-run decision 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, preventing duplicate skeletons. - Template Selection: Chooses between aspire new templates (aspire-starter, aspire-ts-starter, aspire-py-starter, empty variants) for greenfield projects or aspire init for existing repositories. - Handoff Orchestration: Routes to the aspireify skill for resource wiring and aspire-orchestration for validation after the skeleton is in place. - Use Case: A developer has an existing Express API and .NET backend in one repo and wants Aspire orchestration. The Skill confirms no AppHost exists, runs aspire init with the chosen language, 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.
