aspire

Routes Aspire distributed app tasks to orchestration, deployment, and monitoring sub-skills.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/ecoDriverltd/FoundryAgentsExperiment --skill aspire-ecodriverltd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aspire
Source: https://github.com/ecoDriverltd/FoundryAgentsExperiment/tree/main/.agents/skills/aspire
Command: npx skills add https://github.com/ecoDriverltd/FoundryAgentsExperiment --skill aspire-ecodriverltd

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, and using the wrong command (like dotnet run on an AppHost) can corrupt state or waste time. This Skill detects Aspire projects, enforces safe CLI workflows, and routes each task to the correct specialized sub-skill. ## Core Features & Use Cases - Automatic Detection: Identifies Aspire AppHosts via C# projects, file-based apphost.cs, TypeScript apphost.ts, aspire.config.json, and .aspire/ directories. - Task Routing: Directs lifecycle operations to aspire-orchestration, deployments to aspire-deployment, observability to aspire-monitoring, and first-run setup to aspire-init or aspireify. - Safety Guardrails: Enforces rules like always using aspire start instead of dotnet run, always running aspire wait before interacting with resources, and never editing generated .aspire/modules/ files. - Use Case: You open a repo containing an Aspire AppHost and ask to restart a failing Redis resource. The Skill detects the AppHost, routes to the orchestration sub-skill, and uses aspire resource commands rather than restarting the entire application. ## Quick Start Ask the agent to start my Aspire app and wait until the database resource is ready before running any commands against it.

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, never `dotnet run` on the AppHost project. In worktrees or shared environments, use `aspire start --isolated` to avoid conflicts with shared local state.

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

Run `aspire init` to drop the skeleton (aspire.config.json plus an AppHost stub), then use the aspireify skill to wire resources, integrations, and service defaults. Note that in Aspire 13.3, `aspire init` no longer wires the AppHost automatically.

Does the Aspire CLI work with TypeScript AppHosts?▼

Yes, TypeScript AppHosts defined in `apphost.ts` are fully supported. However, never edit the generated `.aspire/modules/` directory directly, and use the unified `withEnvironment(name, value)` API since per-kind helpers are deprecated in 13.3.

Why should I use aspire wait instead of polling a resource endpoint?▼

The `aspire wait <resource>` command blocks until a resource reaches a ready state using Aspire's own health tracking. Manual HTTP polling can interact with resources before they are fully initialized, causing flaky failures.

What changed in Aspire 13.3 that breaks existing scripts?▼

Key breaking changes include `--log-level` renamed to `--pipeline-log-level`, removal of the dashboard MCP server, `NameOutput` renamed to `NameOutputReference`, and `AddAndPublishPromptAgent` replaced by `AddPromptAgent`. The skill includes a full migration checklist reference.

When should I not use this Aspire skill?▼

Do not use it for non-Aspire .NET projects (use dotnet directly), Azure provisioning without Aspire, container-only repos with no AppHost, or ordinary build and test tasks. It is specifically for operating Aspire distributed applications.