Scaffolds an Aspire AppHost skeleton in repositories using aspire init or aspire new templates.
npx skills add https://github.com/codebytes/btt --skill aspire-init-codebytes
Please help me install this Agent Skill. Skill: aspire-init Source: https://github.com/codebytes/btt/tree/main/.agents/skills/aspire-init Command: npx skills add https://github.com/codebytes/btt --skill aspire-init-codebytes
aspire new (greenfield templates) and aspire init (existing repos), detecting whether an AppHost already exists, and knowing when to hand off wiring to other tools. This Skill guides that first-run flow so the correct skeleton, aspire.config.json, and aspireify skill land in the repo without duplicating an existing AppHost. ## Core Features & Use Cases - AppHost Detection: Checks for C# .csproj with Aspire.AppHost.Sdk, file-based apphost.cs, TypeScript apphost.ts, and aspire.config.json before running init, routing to aspireify or aspire-orchestration when an AppHost already exists. - 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 Workflow: Drops the AppHost skeleton and aspire.config.json, installs the aspireify skill, then hands off resource wiring and validation to downstream skills. - Use Case: A developer has an existing Express API plus React frontend repo and wants Aspire orchestration. The Skill confirms no AppHost exists, runs aspire init --language typescript --non-interactive, and hands off to aspireify to wire the services. ## Quick Start Ask the agent to add Aspire to this repository and it will detect whether an AppHost exists, then run aspire init or aspire new with the right template and language.High-intent search queries and answers about installing and using this skill.
Run aspire init with an explicit language flag, such as aspire init --language csharp --non-interactive. It drops an AppHost skeleton and aspire.config.json next to your existing code, then the aspireify skill wires your services into the AppHost.
aspire new generates a full starter solution from a template for brand-new projects, while aspire init adds a minimal AppHost skeleton to an existing repo without modifying current projects. Use aspire new for greenfield work and aspire init when services already exist.
Templates include aspire-starter (ASP.NET Core/Blazor), aspire-ts-cs-starter (ASP.NET Core/React), aspire-py-starter (FastAPI/React with a TypeScript AppHost), aspire-ts-starter (Express/React), and the minimal aspire-empty and aspire-ts-empty scaffolds.
No. If the repo already contains a .csproj with Aspire.AppHost.Sdk, an apphost.cs, an apphost.ts, or aspire.config.json, do not run aspire init. Route to the aspireify skill for re-wiring or aspire-orchestration for lifecycle operations instead.
aspire init fails in non-interactive mode when multiple language paths are available and no --language flag is passed. Re-run with --language csharp or --language typescript to resolve it.
No. aspire init only drops the AppHost skeleton, aspire.config.json, and the aspireify agent skill. Resource wiring, references, and integrations are handled afterward by the aspireify skill, then validated with aspire start.
HexalithScaffolds an Aspire AppHost skeleton in repositories using aspire init or aspire new.
MarcelMichauRoute Aspire AppHost tasks through the Aspire CLI.
AvanadeOrchestrates Aspire distributed applications using the Aspire CLI for starting, debugging, and managing resources.
spike-land-aiConfigure secure email and password authentication with Better Auth.