What problem does it solve? Adding .NET Aspire orchestration to a repository requires choosing the right entry command, template, and language, and running the wrong one on a repo that already has an AppHost breaks the setup. This Skill detects whether a repo is safe to initialize, picks between aspire new (greenfield) and aspire init (existing repo), drops the AppHost skeleton, and hands off wiring to the aspireify skill. ## Core Features & Use Cases - AppHost Detection: Checks for C# AppHost projects, file-based apphost.cs, TypeScript apphost.ts, and aspire.config.json before running any init command, preventing duplicate skeletons. - Template Selection: Chooses among aspire-starter, aspire-ts-starter, aspire-py-starter, aspire-empty, and aspire-ts-empty based on whether the project is greenfield, Python-based, or minimal. - Non-Interactive Agent Flows: Runs aspire init --language csharp|typescript --non-interactive and aspire new <template> --non-interactive so AI agents can scaffold without prompts. - Use Case: A developer has an existing FastAPI plus React repository and wants Aspire orchestration. The Skill confirms no AppHost exists, runs aspire init --language typescript --non-interactive, then hands off to aspireify to wire the services. ## Quick Start Ask the agent to add Aspire to this repository and it will detect the missing AppHost, run the appropriate aspire init or aspire new command, and hand off wiring to aspireify.
