aspire

Routes Aspire AppHost operations to orchestration, deployment, and monitoring sub-skills via the Aspire CLI.

Updated Jan 20, 2021
One-click install
npx skills add https://github.com/Stavanger-Brass-Band/sheetmusic-api --skill aspire-stavanger-brass-band
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aspire
Source: https://github.com/Stavanger-Brass-Band/sheetmusic-api/tree/main/.agents/skills/aspire
Command: npx skills add https://github.com/Stavanger-Brass-Band/sheetmusic-api --skill aspire-stavanger-brass-band

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Working with Aspire distributed applications requires knowing dozens of CLI commands and safety rules; this Skill detects the AppHost, enforces guardrails (never dotnet run on AppHosts, always aspire wait), and routes each task to the correct specialized sub-skill. ## Core Features & Use Cases - AppHost Detection: Identifies C#, file-based C#, and TypeScript AppHosts plus aspire.config.json and .aspire/ signals to decide the right workflow scope. - Task Routing: Directs start/stop/wait to aspire-orchestration, deploy/publish/destroy to aspire-deployment, logs/traces/dashboard to aspire-monitoring, and bootstrap work to aspire-init or aspireify. - Safety Guardrails: Enforces rules such as always using aspire start, --non-interactive for agents, and never editing generated .aspire/modules/ files. - Use Case: You open a repo containing an Aspire AppHost and ask to restart a single failing resource; the Skill routes to aspire-orchestration, waits for health, and avoids restarting the entire AppHost. ## Quick Start Ask the assistant to start the Aspire AppHost in this repository and wait until all resources are healthy.

Frequently Asked Questions about aspire

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start an Aspire AppHost from the command line?▼

Use `aspire start` from the repository root rather than `dotnet run` on the AppHost project. Add `--isolated` when working in worktrees or when shared local state is risky, then run `aspire wait <resource>` before interacting with any resource.

How do I add Aspire to an existing .NET repository?▼

Run `aspire init` to drop the skeleton (aspire.config.json plus an AppHost stub), then use the aspireify flow to scan the repo, propose a resource graph, wire ServiceDefaults and OpenTelemetry, and validate with `aspire start`.

Does this skill work with TypeScript Aspire AppHosts?▼

Yes, it detects `apphost.ts` files and generated `.aspire/modules/` directories as definitive Aspire signals. It never edits generated modules directly and uses the unified `withEnvironment(name, value)` API for TypeScript wiring.

When should I not use the Aspire CLI workflow?▼

Skip it for non-Aspire .NET projects where plain `dotnet` commands suffice, Azure provisioning without Aspire, container-only repos with no AppHost, and ordinary build or test tasks that do not touch the distributed app model.

Why does aspire init leave my AppHost unwired?▼

Since Aspire 13.3, `aspire init` only drops a skeleton and installs the aspireify skill by design. The wiring step—declaring resources, integrations, and ServiceDefaults—must be completed by the aspireify flow afterward.