What problem does it solve? Adding Aspire orchestration to a repository requires choosing between aspire new (greenfield templates) and aspire init (existing repos), detecting whether an AppHost already exists, and knowing that the skeleton alone does not wire resources. This Skill automates that first-run decision flow and hands off wiring to the aspireify skill. ## Core Features & Use Cases - AppHost Detection: Checks for existing C# (apphost.cs, .csproj with Aspire.AppHost.Sdk), TypeScript (apphost.ts), and aspire.config.json signals before running init to avoid duplicate skeletons. - Template Selection: Chooses among aspire-starter, aspire-ts-starter, aspire-py-starter, aspire-empty, and aspire-ts-empty based on project type, with non-interactive flags for agent execution. - Handoff Orchestration: Routes to aspireify for resource wiring, aspire-orchestration for aspire start, aspire-deployment for publishing, and aspire-monitoring for logs and traces. - Use Case: A developer has an existing Express API and wants Aspire orchestration. The Skill confirms no AppHost exists, runs aspire init --language typescript --non-interactive, verifies the apphost.ts and .aspire/modules/ skeleton, then hands off to aspireify to wire the services. ## Quick Start Add Aspire to my existing repository by scaffolding an AppHost skeleton and then wiring my services with aspireify.
