aspire

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

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

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 an Aspire AppHost in a repo, enforces guardrails (never dotnet run on AppHosts, always aspire wait before interacting), and routes each task to the correct specialized sub-skill instead of ad-hoc shell workflows. ## Core Features & Use Cases - AppHost Detection: Identifies C#, file-based C#, and TypeScript AppHosts plus aspire.config.json and .aspire/ signals to decide whether to bootstrap or operate. - Task Routing: Directs lifecycle work to aspire-orchestration, deployments to aspire-deployment, observability to aspire-monitoring, and first-run wiring to aspire-init/aspireify. - Safety Guardrails: Enforces --non-interactive execution, forbids the obsolete Aspire workload, and protects generated .aspire/modules/ files from edits. - Use Case: You open a repo containing an AppHost and ask to restart a failing Redis resource; the Skill confirms the AppHost, runs aspire start, waits on the resource, and hands the restart to the orchestration sub-skill. ## Quick Start Ask the agent 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?▼

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

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 wire resources, ServiceDefaults, and OpenTelemetry through the aspireify flow. In Aspire 13.3, `aspire init` no longer wires the AppHost by itself.

Does the Aspire CLI work with TypeScript AppHosts?▼

Yes, TypeScript AppHosts defined in apphost.ts are fully supported, with generated modules under .aspire/modules/. Never edit those generated files directly, and use the unified withEnvironment(name, value) API since per-kind helpers are deprecated.

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 ships a full scrub list for migration.

When should I not use the Aspire CLI workflow?▼

Skip it for non-Aspire .NET projects (use dotnet directly), Azure provisioning without Aspire, container-only repos with no AppHost, and ordinary build or test tasks. The skill only activates when AppHost or Aspire configuration signals are present.