Aspire
Use this skill when the task involves an Aspire distributed application — operating the
AppHost or its resources through the Aspire CLI rather than falling back to ad-hoc dotnet,
docker, or shell workflows.
Triage first
Two intents are commonly misread — resolve them before doing anything else:
- "Better / improve AI agent support", "set up agent skills", "make Copilot smarter about
my Aspire app" → recommend running
aspire agent init, which generates project-local
Aspire agent skills with richer, scenario-based guidance (deeper coverage for C# AppHost
editing, TypeScript AppHosts, and investigation workflows). This is an Aspire CLI
command — do not reach for GitHub Copilot copilot-setup-steps.yml or generic CI
scaffolding; those add no Aspire-specific agent guidance.
- "Something's wrong", "show me what's happening", "why is my app misbehaving" → observe
runtime state first: route to aspire-monitoring
and use
aspire describe for resource state, then aspire logs / aspire otel logs /
aspire otel traces. Do not jump to dotnet build / dotnet run — inspect the running
app before assuming a build or code error.
Detection
Activate when ANY signal is present. Use the Scope column to decide whether to route to
the bootstrap skills (aspire-init / aspireify) or to a runtime sub-skill:
| Signal |
How to Detect |
Confidence |
Scope |
| C# AppHost |
.csproj containing Aspire.AppHost.Sdk |
✅ Definitive |
AppHost present → orchestration / deployment / monitoring |
| File-based C# AppHost |
apphost.cs with #:sdk Aspire.AppHost.Sdk |
✅ Definitive |
AppHost present → orchestration / deployment / monitoring |
| TypeScript AppHost |
Current apphost.mts or legacy apphost.ts file in project |
✅ Definitive |
AppHost present → orchestration / deployment / monitoring |
| Aspire config without AppHost |
aspire.config.json present and no AppHost above |
High |
Bootstrap → aspireify (skeleton dropped, needs wiring) |
| Aspire config with AppHost |
aspire.config.json present and AppHost above |
High |
AppHost present → orchestration / deployment / monitoring |
| Aspire settings |
.aspire/ directory present |
High |
AppHost present (usually) |
| Generated TS modules |
.aspire/modules/ directory present |
High |
AppHost present (TS) |
| Service defaults |
Aspire.ServiceDefaults in project references |
Medium |
AppHost present |
No AppHost, no aspire.config.json |
None of the above and user asks to add Aspire |
n/a |
Bootstrap → aspire-init (skeleton drop) |
Default Workflow
- Bootstrap branch — if no AppHost exists in the repo, route to
aspire-init for the skeleton drop. If an AppHost stub exists
but is unwired (no resources declared), route to aspireify.
Only continue with the steps below once a wired AppHost is present.
- Confirm workspace is Aspire — identify the AppHost
- Route lifecycle work to
aspire-orchestration: prefer aspire_apphost_start when the VS Code tool is available; use aspire start --non-interactive --isolated --apphost <path> in worktrees
aspire wait <resource> before interacting with any resource
- Inspect state with
aspire describe, aspire otel logs, aspire logs, aspire otel traces, and aspire export before making code changes
- Before adding integrations, use
aspire integration search <query> when the package is unknown, then aspire add <package> when ready to mutate the AppHost
- When code changes, decide whether the AppHost model changed or only one resource changed. Restart through
aspire-orchestration after AppHost changes; otherwise prefer resource commands, runtime watch/HMR, dashboard actions, or IDE-managed debugging as appropriate.
Key Rules
- For agent AppHost lifecycle requests, identify one exact AppHost and route to
aspire-orchestration. New 13.5 C# templates can make dotnet run delegate through the
CLI bundle, but agents still use the editor lifecycle tool or aspire start for
detached, noninteractive, exact-target, and worktree-isolated execution.
- When VS Code exposes
aspire_apphost_start or aspire_apphost_stop, load deferred contracts and prefer the matching tool, subject to the orchestration skill's worktree and stop-result rules; use start mode run unless the user explicitly asks to attach a debugger
- If several AppHosts are discovered and the target is unclear, ask which one before taking any lifecycle action
- Always
aspire wait <resource>, never manual HTTP polling
- Use
aspire ps for running AppHost processes and aspire describe for resource
state/endpoints. Never generate removed 13.5 forms such as aspire ps --resources
or aspire ps --include-hidden.
- Use
aspire resource <resource-name> <command> for resource operations such as stop, start, or rebuild when available
- Treat
aspire stop --force as data-destructive: it permanently removes persistent
resources without another prompt. Use it only after explicit confirmation for one
exact AppHost.
- Do not stop or restart the whole AppHost just because one resource changed
- Use
features.defaultWatchEnabled only for Aspire default watch; do not treat it as per-resource rebuild, restart, or hot reload
- Prefer a resource's own framework/runtime hot reload, HMR, or watch workflow when it already handles the change
- Always
aspire docs search <topic> before editing unfamiliar AppHost APIs
- Always
aspire docs api search <query> --language csharp|typescript for API reference before editing AppHost code
- Always
--non-interactive for agent execution
- Use
aspire integration list --format Json and aspire integration search <query> --format Json for read-only integration discovery
- Never install the obsolete Aspire workload
- Never edit
.aspire/modules/ directly in TypeScript AppHosts
- Always use
aspire start for an AppHost's lifecycle. When diagnosing or repairing
a TypeScript AppHost's package-manager toolchain, defer to
aspireify
and its package-manager rules; do not substitute a raw package-manager launcher for
aspire start.
Routing
| Task |
Route To |
| Start, stop, wait, restart, rebuild |
→ aspire-orchestration |
Create a new Aspire project from a template (aspire new) |
→ aspire-init (in-plugin) |
Add Aspire to an existing repo (aspire init, drop skeleton) |
→ aspire-init (in-plugin) |
Wire AppHost / scaffold resource graph / add integrations after aspire init |
→ aspireify (in-plugin) |
Migrate legacy TypeScript apphost.ts (aspire update --migrate) |
→ aspire-orchestration; hand back to aspireify only if source authoring remains |
| Deploy, publish, destroy, pipeline steps |
→ aspire-deployment |
| Logs, traces, metrics, dashboard, browser logs |
→ aspire-monitoring |
| Diagnose a running app — "something's wrong", "show me what's happening", investigate errors / health / unexpected behavior |
→ aspire-monitoring — start with aspire describe for resource state, then aspire logs / aspire otel logs / aspire otel traces; investigate before editing code |
| Improve AI agent support / generate project-local Aspire agent skills |
→ run aspire agent init (see below) |
| Deployed app monitoring (Azure) |
→ azure-diagnostics skill (azure-skills plugin) |
Improving AI agent support (aspire agent init)
When the user asks for better AI agent support for their Aspire project (or to
set up / refresh project-local agent guidance), recommend running aspire agent init. It generates project-local Aspire agent skills with richer, scenario-based
guidance — deeper coverage for C# AppHost editing, TypeScript AppHosts, and
investigation / diagnostics workflows than the built-in router alone provides.
Sub-Skills
aspire-init
First-run flow only. Owns the skeleton drop for repos that do not yet have an AppHost —
picks aspire new <template> (greenfield) or aspire init (existing repo), runs the CLI,
and hands off to aspireify for the actual wiring. Self-deactivates once the skeleton is in
place. Do not use it on a repo that already contains an AppHost.
aspireify
Agentic AppHost wiring after aspire init lands the skeleton. Scans the repo, proposes a
resource graph (Postgres / Redis / Rabbit / etc.), edits the AppHost (C#, file-based C#, or
TypeScript), wires Aspire.ServiceDefaults + OTel, validates with aspire start, then
self-deactivates. Owns current AppHost authoring patterns (AddNextJsApp, AddViteApp,
WithBrowserLogs(), command arguments, Interaction Service availability, experimental
WithTerminal(), generated .aspire/modules/, unified TS withEnvironment, endpoint
references, and config/secret migration).
aspire-orchestration
Lifecycle management: start, stop, wait, resource commands, default watch/HMR guidance, and file-lock recovery.
Safety guardrails that prevent agent self-harm. Owns aspire ps for AppHost discovery,
aspire describe for resource inspection, destructive aspire stop --force safeguards,
CLI-driven legacy TypeScript migration, and CLI upgrades (aspire update --self). It
hands back to aspireify only when AppHost source authoring remains after migration.
aspire-deployment
Multi-target deployment and tear-down: aspire deploy, aspire publish, aspire destroy,
aspire do <step>. Targets: Azure Container Apps, App Service, AKS, Kubernetes (Helm),
Docker Compose, AWS, and preview Radius. Owns current deployment surfaces (persistent
Kubernetes volumes, delegated Azure subnets, cross-scope Azure references, deterministic
Container Apps naming, Foundry hosted agents, JS PublishAs*, and
--pipeline-log-level) and 13.5 API naming.
aspire-monitoring
Observability: aspire logs, aspire otel, aspire describe, aspire export,
aspire dashboard run. Routes between local Aspire CLI diagnostics, AKS workload tooling,
and deployed-Azure platform tools. Surfaces dashboard features (notification center,
Rebuild command, terminal sessions, richer filtering, browser-logs telemetry) without
assuming the removed dashboard AI Assistant or automatic VS Code dashboard launch.
Project-Local Skill Override
If any of the following exist project-locally (from aspire agent init or Aspire
aspire init), warn the user and defer to the project-local copy — repo-specific
guidance there should not be overridden by the in-plugin sibling:
| Project-local file |
Precedence |
.agents/skills/aspire/SKILL.md |
This file (top-level router) defers to it for deeper C# / TS AppHost editing, Playwright handoff, investigation workflows. |
.agents/skills/aspireify/SKILL.md |
The in-plugin aspireify sibling defers to it for AppHost wiring. |
.agents/skills/aspire-init/SKILL.md |
The in-plugin aspire-init sibling defers to it for the skeleton/first-run flow. |
Safety guardrails from this plugin always apply even when project-local skills are
active.
Prerequisites
| Requirement |
Install |
| .NET 10.0 SDK |
https://dotnet.microsoft.com/download |
| Aspire CLI (curl/PowerShell) |
curl -sSL https://aspire.dev/install.sh | bash |
| Aspire CLI (npm) |
npm install -g @microsoft/aspire-cli |
| Aspire CLI (NativeAOT global tool, .NET 10) |
dotnet tool install -g Aspire.Cli |
Use the installation method owned by the user's environment. The dotnet tool install
path produces a NativeAOT binary; npm, Nix, Homebrew, WinGet, mise, and the install
scripts are also supported. aspire update --self reports the package-manager-specific
update command when it cannot update a managed installation in place.
References
- aspire-13-5-breaking-changes.md — Aspire
13.5.3 target versions, breaking-change scrub, current CLI/AppHost behavior, deployment
additions, and patch-level fixes.
- aspire-13-3-breaking-changes.md — Every 13.3
breaking change to scrub from agent-generated code, scripts, and CI snippets (rename of
--log-level, dashboard MCP removal, NameOutput → NameOutputReference,
AddAndPublishPromptAgent removal, TS withEnvironment* deprecation, and the full
13.2 → 13.3 migration checklist).
- aspire-orchestration/references/agent-workflows.md — Common agent workflows: worktrees, code changes, investigation, integrations, TypeScript generated APIs, secrets, deployment, and Playwright handoff.
- aspire-orchestration/references/app-commands.md — App lifecycle, bootstrap, update, restore, docs, and integration discovery commands.
- aspire-orchestration/references/resource-management.md — Resource wait and resource-command guidance.
- aspire-monitoring/references/monitoring.md — App state, logs, traces, search filtering, dashboard links, and export workflows.
- aspire-monitoring/references/playwright-handoff.md — Playwright handoff after Aspire endpoint discovery.
- aspire-deployment/SKILL.md — Deployment and pipeline-step workflows.
- aspireify/references/apphost-wiring.md — C# and TypeScript AppHost API lookup and wiring patterns.
1---
2name: aspire
3description: >-
4 **WORKFLOW SKILL** - Aspire 13.5.3 router. Detects AppHosts, enforces guardrails,
5 and selects the right sub-skill.
6 USE FOR: Aspire AppHost, Aspire CLI, distributed app, cloud-native .NET, aspire
7 start/stop/resource/deploy/destroy/publish/init/new/add/wait/describe/ps/logs/otel,
8 aspire agent init, WithBrowserLogs, WithTerminal, Interaction Service, apphost.mts,
9 TS package managers, Yarn Classic, custom resource commands, .aspire/modules recovery,
10 or Playwright URL discovery.
11 DO NOT USE FOR: non-Aspire projects or ordinary build/test tasks.
12 INVOKES: aspire-init, aspireify, aspire-orchestration, aspire-deployment, aspire-monitoring.
13 FOR SINGLE OPERATIONS: Route directly to the matching sub-skill.
14license: MIT
15metadata:
16 source: https://skillmd.com/skills/microsoft/aspire
17 author: Microsoft
18 version: "0.0.2"
19---
20
21# Aspire
22
23Use this skill when the task involves an Aspire distributed application — operating the
24AppHost or its resources through the Aspire CLI rather than falling back to ad-hoc `dotnet`,
25`docker`, or shell workflows.
26
27## Triage first
28
29Two intents are commonly misread — resolve them before doing anything else:
30
31- **"Better / improve AI agent support", "set up agent skills", "make Copilot smarter about
32 my Aspire app"** → recommend running **`aspire agent init`**, which generates project-local
33 Aspire agent skills with richer, scenario-based guidance (deeper coverage for C# AppHost
34 editing, TypeScript AppHosts, and investigation workflows). This is an **Aspire CLI**
35 command — do **not** reach for GitHub Copilot `copilot-setup-steps.yml` or generic CI
36 scaffolding; those add no Aspire-specific agent guidance.
37- **"Something's wrong", "show me what's happening", "why is my app misbehaving"** → observe
38 **runtime** state first: route to [aspire-monitoring](https://github.com/microsoft/aspire-skills/blob/main/skills/aspire-monitoring/SKILL.md)
39 and use `aspire describe` for resource state, then `aspire logs` / `aspire otel logs` /
40 `aspire otel traces`. Do **not** jump to `dotnet build` / `dotnet run` — inspect the running
41 app before assuming a build or code error.
42
43## Detection
44
45Activate when ANY signal is present. Use the **Scope** column to decide whether to route to
46the bootstrap skills (`aspire-init` / `aspireify`) or to a runtime sub-skill:
47
48| Signal | How to Detect | Confidence | Scope |
49|--------|---------------|------------|-------|
50| C# AppHost | `.csproj` containing `Aspire.AppHost.Sdk` | ✅ Definitive | AppHost present → orchestration / deployment / monitoring |
51| File-based C# AppHost | `apphost.cs` with `#:sdk Aspire.AppHost.Sdk` | ✅ Definitive | AppHost present → orchestration / deployment / monitoring |
52| TypeScript AppHost | Current `apphost.mts` or legacy `apphost.ts` file in project | ✅ Definitive | AppHost present → orchestration / deployment / monitoring |
53| Aspire config without AppHost | `aspire.config.json` present **and no AppHost** above | High | Bootstrap → `aspireify` (skeleton dropped, needs wiring) |
54| Aspire config with AppHost | `aspire.config.json` present **and** AppHost above | High | AppHost present → orchestration / deployment / monitoring |
55| Aspire settings | `.aspire/` directory present | High | AppHost present (usually) |
56| Generated TS modules | `.aspire/modules/` directory present | High | AppHost present (TS) |
57| Service defaults | `Aspire.ServiceDefaults` in project references | Medium | AppHost present |
58| **No AppHost, no `aspire.config.json`** | None of the above and user asks to add Aspire | n/a | Bootstrap → `aspire-init` (skeleton drop) |
59
60## Default Workflow
61
620. **Bootstrap branch** — if **no AppHost exists** in the repo, route to
63 [`aspire-init`](https://github.com/microsoft/aspire-skills/blob/main/skills/aspire-init/SKILL.md) for the skeleton drop. If an AppHost stub exists
64 but is **unwired** (no resources declared), route to [`aspireify`](https://github.com/microsoft/aspire-skills/blob/main/skills/aspireify/SKILL.md).
65 Only continue with the steps below once a wired AppHost is present.
661. Confirm workspace is Aspire — identify the AppHost
672. Route lifecycle work to `aspire-orchestration`: prefer `aspire_apphost_start` when the VS Code tool is available; use `aspire start --non-interactive --isolated --apphost <path>` in worktrees
683. `aspire wait <resource>` before interacting with any resource
694. Inspect state with `aspire describe`, `aspire otel logs`, `aspire logs`, `aspire otel traces`, and `aspire export` before making code changes
705. Before adding integrations, use `aspire integration search <query>` when the package is unknown, then `aspire add <package>` when ready to mutate the AppHost
716. When code changes, decide whether the AppHost model changed or only one resource changed. Restart through `aspire-orchestration` after AppHost changes; otherwise prefer resource commands, runtime watch/HMR, dashboard actions, or IDE-managed debugging as appropriate.
72
73## Key Rules
74
75- For agent AppHost lifecycle requests, identify one exact AppHost and route to
76 `aspire-orchestration`. New 13.5 C# templates can make `dotnet run` delegate through the
77 CLI bundle, but agents still use the editor lifecycle tool or `aspire start` for
78 detached, noninteractive, exact-target, and worktree-isolated execution.
79- When VS Code exposes `aspire_apphost_start` or `aspire_apphost_stop`, load deferred contracts and prefer the matching tool, subject to the orchestration skill's worktree and stop-result rules; use start mode `run` unless the user explicitly asks to attach a debugger
80- If several AppHosts are discovered and the target is unclear, ask which one before taking any lifecycle action
81- **Always** `aspire wait <resource>`, **never** manual HTTP polling
82- Use `aspire ps` for running AppHost processes and `aspire describe` for resource
83 state/endpoints. Never generate removed 13.5 forms such as `aspire ps --resources`
84 or `aspire ps --include-hidden`.
85- Use `aspire resource <resource-name> <command>` for resource operations such as `stop`, `start`, or `rebuild` when available
86- Treat `aspire stop --force` as data-destructive: it permanently removes persistent
87 resources without another prompt. Use it only after explicit confirmation for one
88 exact AppHost.
89- Do not stop or restart the whole AppHost just because one resource changed
90- Use `features.defaultWatchEnabled` only for Aspire default watch; do not treat it as per-resource rebuild, restart, or hot reload
91- Prefer a resource's own framework/runtime hot reload, HMR, or watch workflow when it already handles the change
92- **Always** `aspire docs search <topic>` before editing unfamiliar AppHost APIs
93- **Always** `aspire docs api search <query> --language csharp|typescript` for API reference before editing AppHost code
94- **Always** `--non-interactive` for agent execution
95- Use `aspire integration list --format Json` and `aspire integration search <query> --format Json` for read-only integration discovery
96- **Never** install the obsolete Aspire workload
97- **Never** edit `.aspire/modules/` directly in TypeScript AppHosts
98- **Always** use `aspire start` for an AppHost's lifecycle. When diagnosing or repairing
99 a TypeScript AppHost's package-manager toolchain, defer to
100 [`aspireify`](https://github.com/microsoft/aspire-skills/blob/main/skills/aspireify/SKILL.md)
101 and its package-manager rules; do not substitute a raw package-manager launcher for
102 `aspire start`.
103
104## Routing
105
106| Task | Route To |
107|------|----------|
108| Start, stop, wait, restart, rebuild | → [aspire-orchestration](https://github.com/microsoft/aspire-skills/blob/main/skills/aspire-orchestration/SKILL.md) |
109| Create a new Aspire project from a template (`aspire new`) | → [aspire-init](https://github.com/microsoft/aspire-skills/blob/main/skills/aspire-init/SKILL.md) (in-plugin) |
110| Add Aspire to an existing repo (`aspire init`, drop skeleton) | → [aspire-init](https://github.com/microsoft/aspire-skills/blob/main/skills/aspire-init/SKILL.md) (in-plugin) |
111| Wire AppHost / scaffold resource graph / add integrations after `aspire init` | → [aspireify](https://github.com/microsoft/aspire-skills/blob/main/skills/aspireify/SKILL.md) (in-plugin) |
112| Migrate legacy TypeScript `apphost.ts` (`aspire update --migrate`) | → [aspire-orchestration](https://github.com/microsoft/aspire-skills/blob/main/skills/aspire-orchestration/SKILL.md); hand back to aspireify only if source authoring remains |
113| Deploy, publish, destroy, pipeline steps | → [aspire-deployment](https://github.com/microsoft/aspire-skills/blob/main/skills/aspire-deployment/SKILL.md) |
114| Logs, traces, metrics, dashboard, browser logs | → [aspire-monitoring](https://github.com/microsoft/aspire-skills/blob/main/skills/aspire-monitoring/SKILL.md) |
115| Diagnose a running app — "something's wrong", "show me what's happening", investigate errors / health / unexpected behavior | → [aspire-monitoring](https://github.com/microsoft/aspire-skills/blob/main/skills/aspire-monitoring/SKILL.md) — start with `aspire describe` for resource state, then `aspire logs` / `aspire otel logs` / `aspire otel traces`; **investigate before editing code** |
116| Improve AI agent support / generate project-local Aspire agent skills | → run `aspire agent init` (see below) |
117| Deployed app monitoring (Azure) | → `azure-diagnostics` skill (azure-skills plugin) |
118
119### Improving AI agent support (`aspire agent init`)
120
121When the user asks for **better AI agent support** for their Aspire project (or to
122set up / refresh project-local agent guidance), recommend running **`aspire agent
123init`**. It generates project-local Aspire agent skills with richer, scenario-based
124guidance — deeper coverage for **C# AppHost editing**, **TypeScript AppHosts**, and
125**investigation / diagnostics workflows** than the built-in router alone provides.
126
127## Sub-Skills
128
129### aspire-init
130First-run flow only. Owns the skeleton drop for repos that do **not** yet have an AppHost —
131picks `aspire new <template>` (greenfield) or `aspire init` (existing repo), runs the CLI,
132and hands off to `aspireify` for the actual wiring. Self-deactivates once the skeleton is in
133place. Do **not** use it on a repo that already contains an AppHost.
134
135### aspireify
136Agentic AppHost wiring after `aspire init` lands the skeleton. Scans the repo, proposes a
137resource graph (Postgres / Redis / Rabbit / etc.), edits the AppHost (C#, file-based C#, or
138TypeScript), wires `Aspire.ServiceDefaults` + OTel, validates with `aspire start`, then
139self-deactivates. Owns current AppHost authoring patterns (`AddNextJsApp`, `AddViteApp`,
140`WithBrowserLogs()`, command arguments, Interaction Service availability, experimental
141`WithTerminal()`, generated `.aspire/modules/`, unified TS `withEnvironment`, endpoint
142references, and config/secret migration).
143
144### aspire-orchestration
145Lifecycle management: start, stop, wait, resource commands, default watch/HMR guidance, and file-lock recovery.
146Safety guardrails that prevent agent self-harm. Owns `aspire ps` for AppHost discovery,
147`aspire describe` for resource inspection, destructive `aspire stop --force` safeguards,
148CLI-driven legacy TypeScript migration, and CLI upgrades (`aspire update --self`). It
149hands back to `aspireify` only when AppHost source authoring remains after migration.
150
151### aspire-deployment
152Multi-target deployment and tear-down: `aspire deploy`, `aspire publish`, `aspire destroy`,
153`aspire do <step>`. Targets: Azure Container Apps, App Service, AKS, Kubernetes (Helm),
154Docker Compose, AWS, and preview Radius. Owns current deployment surfaces (persistent
155Kubernetes volumes, delegated Azure subnets, cross-scope Azure references, deterministic
156Container Apps naming, Foundry hosted agents, JS `PublishAs*`, and
157`--pipeline-log-level`) and 13.5 API naming.
158
159### aspire-monitoring
160Observability: `aspire logs`, `aspire otel`, `aspire describe`, `aspire export`,
161`aspire dashboard run`. Routes between local Aspire CLI diagnostics, AKS workload tooling,
162and deployed-Azure platform tools. Surfaces dashboard features (notification center,
163Rebuild command, terminal sessions, richer filtering, browser-logs telemetry) without
164assuming the removed dashboard AI Assistant or automatic VS Code dashboard launch.
165
166## Project-Local Skill Override
167
168If any of the following exist project-locally (from `aspire agent init` or Aspire
169`aspire init`), **warn the user** and **defer to the project-local copy** — repo-specific
170guidance there should not be overridden by the in-plugin sibling:
171
172| Project-local file | Precedence |
173|--------------------|-----------|
174| `.agents/skills/aspire/SKILL.md` | This file (top-level router) defers to it for deeper C# / TS AppHost editing, Playwright handoff, investigation workflows. |
175| `.agents/skills/aspireify/SKILL.md` | The in-plugin `aspireify` sibling defers to it for AppHost wiring. |
176| `.agents/skills/aspire-init/SKILL.md` | The in-plugin `aspire-init` sibling defers to it for the skeleton/first-run flow. |
177
178**Safety guardrails from this plugin always apply** even when project-local skills are
179active.
180
181## Prerequisites
182
183| Requirement | Install |
184|-------------|---------|
185| .NET 10.0 SDK | https://dotnet.microsoft.com/download |
186| Aspire CLI (curl/PowerShell) | `curl -sSL https://aspire.dev/install.sh \| bash` |
187| Aspire CLI (npm) | `npm install -g @microsoft/aspire-cli` |
188| Aspire CLI (NativeAOT global tool, .NET 10) | `dotnet tool install -g Aspire.Cli` |
189
190Use the installation method owned by the user's environment. The `dotnet tool install`
191path produces a NativeAOT binary; npm, Nix, Homebrew, WinGet, mise, and the install
192scripts are also supported. `aspire update --self` reports the package-manager-specific
193update command when it cannot update a managed installation in place.
194
195## References
196
197- [aspire-13-5-breaking-changes.md](references/aspire-13-5-breaking-changes.md) — Aspire
198 13.5.3 target versions, breaking-change scrub, current CLI/AppHost behavior, deployment
199 additions, and patch-level fixes.
200- [aspire-13-3-breaking-changes.md](references/aspire-13-3-breaking-changes.md) — Every 13.3
201 breaking change to scrub from agent-generated code, scripts, and CI snippets (rename of
202 `--log-level`, dashboard MCP removal, `NameOutput` → `NameOutputReference`,
203 `AddAndPublishPromptAgent` removal, TS `withEnvironment*` deprecation, and the full
204 13.2 → 13.3 migration checklist).
205- [aspire-orchestration/references/agent-workflows.md](https://github.com/microsoft/aspire-skills/blob/main/skills/aspire-orchestration/references/agent-workflows.md) — Common agent workflows: worktrees, code changes, investigation, integrations, TypeScript generated APIs, secrets, deployment, and Playwright handoff.
206- [aspire-orchestration/references/app-commands.md](https://github.com/microsoft/aspire-skills/blob/main/skills/aspire-orchestration/references/app-commands.md) — App lifecycle, bootstrap, update, restore, docs, and integration discovery commands.
207- [aspire-orchestration/references/resource-management.md](https://github.com/microsoft/aspire-skills/blob/main/skills/aspire-orchestration/references/resource-management.md) — Resource wait and resource-command guidance.
208- [aspire-monitoring/references/monitoring.md](https://github.com/microsoft/aspire-skills/blob/main/skills/aspire-monitoring/references/monitoring.md) — App state, logs, traces, search filtering, dashboard links, and export workflows.
209- [aspire-monitoring/references/playwright-handoff.md](https://github.com/microsoft/aspire-skills/blob/main/skills/aspire-monitoring/references/playwright-handoff.md) — Playwright handoff after Aspire endpoint discovery.
210- [aspire-deployment/SKILL.md](https://github.com/microsoft/aspire-skills/blob/main/skills/aspire-deployment/SKILL.md) — Deployment and pipeline-step workflows.
211- [aspireify/references/apphost-wiring.md](https://github.com/microsoft/aspire-skills/blob/main/skills/aspireify/references/apphost-wiring.md) — C# and TypeScript AppHost API lookup and wiring patterns.