aspire

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

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/Hexalith/Hexalith.Parties --skill aspire-hexalith
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aspire
Source: https://github.com/Hexalith/Hexalith.Parties/tree/main/.agents/skills/aspire
Command: npx skills add https://github.com/Hexalith/Hexalith.Parties --skill aspire-hexalith

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Operating an Aspire distributed application requires knowing dozens of Aspire CLI commands and safety rules; this Skill detects the AppHost, enforces guardrails (never dotnet run on AppHosts, always aspire wait before interacting), and routes each task to the correct specialized sub-skill. ## Core Features & Use Cases - AppHost Detection: Identifies C#, file-based C#, and TypeScript AppHosts via Aspire.AppHost.Sdk, apphost.cs, apphost.ts, aspire.config.json, and .aspire/ signals. - Task Routing: Directs lifecycle work to aspire-orchestration, deployments to aspire-deployment, observability to aspire-monitoring, and first-run setup to aspire-init/aspireify. - Safety Guardrails: Enforces --non-interactive execution, forbids editing .aspire/modules/, and blocks obsolete patterns like the Aspire workload install. - Use Case: You open a repo containing an Aspire AppHost and ask to restart a failing Redis resource; the Skill routes to aspire-orchestration, runs aspire start, waits on the resource, and issues the resource command instead of restarting the whole AppHost. ## Quick Start Ask the assistant to start your Aspire AppHost and check the status of its resources using the Aspire CLI.

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 repo 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 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 the Aspire CLI support TypeScript AppHosts?

Yes, TypeScript AppHosts are detected via an apphost.ts file and use generated modules under .aspire/modules/. Never edit .aspire/modules/ 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 checklist in its references.

When should I not use the Aspire CLI workflow?

Skip it for non-Aspire .NET projects (use dotnet directly), Azure provisioning without Aspire, and container-only repos with no AppHost. The skill explicitly routes those cases to other tools.