A skill your agent uses when the user is working with an Aspire distributed application and needs to operate the AppHost or its resources through the Aspire CLI: start, restart, stop, or wait on the…

MITAuto-check passedTesting & QA

Install Aspire

skills CLI
$ npx skills add SSWConsulting/SSW.VerticalSliceArchitecture --skill aspire -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install SSWConsulting/SSW.VerticalSliceArchitecture aspire --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/SSWConsulting/SSW.VerticalSliceArchitecture.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/aspire .claude/skills/aspire && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
aspire
GitHub stars
407
Used in
1 other repo
Token cost
~2k tokens
SKILL.md length
942 words
Files
10 (incl. references)
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when the user is working with an Aspire distributed application and needs to operate the AppHost or its resources through the Aspire CLI: start, restart, stop, or wait on the…

  • Works in 6 steps: Confirm that the workspace is an Aspire… → Start the app with aspire start. Use… → Use aspire wait before interacting with… → …
  • The user is working with an Aspire distributed application and needs to operate the AppHost
  • SKILL.md covers Use this skill for, Do not use this skill for, Default workflow and C# AppHosts, plus 5 more sections
  • Calls dotnet

What it does

Aspire is an agent skill from SSWConsulting/SSW.VerticalSliceArchitecture. Use this skill when the user is working with an Aspire distributed application and needs to operate the AppHost or its resources through the Aspire CLI: start, restart, stop, or wait on the app; inspect resources, logs, traces, docs, or health; add integrations; manage secrets or config; publish, deploy, or rerun a named pipeline step; initialize Aspire in an existing app; recover missing .modules files in a TypeScript AppHost; discover the right frontend URL for Playwright from Aspire state; expose custom…

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including reference files (for example `references/agent-workflows.md`, `references/app-commands.md` and `references/csharp-apphosts.md`).

It sits in Testing & QA, covering Browser testing. It works with TypeScript, Playwright, C# and .NET. The repository describes itself as: An enterprise ready solution template for Vertical Slice Architecture. This template is just one way to apply the Vertical Slice Architecture. The licence is MIT.

When your agent uses it

  • The user is working with an Aspire distributed application and needs to operate the AppHost
  • Its resources through the Aspire CLI: start
  • Wait on the app
  • Inspect resources

Example prompts

  • “/aspire”

Requirements

  • Docker

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Confirm that the workspace is an Aspire app and identify the AppHost.
  2. Start the app with aspire start. Use --isolated in git worktrees or whenever shared local state would be risky.
  3. Use aspire wait before interacting with a resource that needs to be healthy.
  4. Inspect state with aspire describe, then use aspire otel logs, aspire logs, aspire otel traces, and aspire export before making code…
  5. Before adding an integration, introducing a custom dashboard/resource command, or using an unfamiliar AppHost API, use aspire docs search…
  6. Re-run aspire start after AppHost changes. In git worktrees, re-run aspire start --isolated instead of switching to aspire run.

What it can do on your machine

Read from SKILL.md and the folder at commit 42e7a70. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • dotnet

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Aspire loads about 2k tokens when it runs, and up to ~7.2k if it reads all its reference files. Until then it costs about 245 tokens; SKILL.md has 942 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~245
When it runs · the whole SKILL.md, loaded when a task matches
~2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~7.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from SSWConsulting/SSW.VerticalSliceArchitecture at commit 42e7a70, republished under its MIT licence (© SSWConsulting). 942 words, ~2,035 tokens.

Download SKILL.mdSave it as .claude/skills/aspire/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.
name
aspire
description
Use this skill when the user is working with an Aspire distributed application and needs to operate the AppHost or its resources through the Aspire CLI: start, restart, stop, or wait on the app; inspect resources, logs, traces, docs, or health; add integrations; manage secrets or config; publish, deploy, or rerun a named pipeline step; initialize Aspire in an existing app; recover missing `.modules` files in a TypeScript AppHost; discover the right frontend URL for Playwright from Aspire state; expose custom dashboard/resource commands; or understand unfamiliar Aspire AppHost APIs in C# or TypeScript. Use it even if they describe the task in terms of an AppHost, resources, dashboard, existing app bootstrap, missing generated modules, Playwright URL discovery, C# API understanding, or local distributed app workflow without explicitly naming Aspire. Do not use it for non-Aspire .NET apps, container-only repos with no AppHost, or ordinary build and test tasks.

Aspire Skill

Use this skill when the task is about operating an Aspire distributed application through the Aspire CLI rather than falling back to ad-hoc dotnet, docker, or shell workflows.

Resources are typically defined in an AppHost such as, AppHost.cs, apphost.ts, or AppHost/AppHost.csproj (Program.cs).

Use this skill for

  • Starting, restarting, and stopping AppHosts with aspire start and aspire stop
  • Initializing Aspire in an existing app with aspire init (drops skeleton files; use the aspireify skill to complete wiring)
  • Inspecting resources, logs, traces, and docs
  • Adding integrations with aspire add
  • Recovering missing TypeScript AppHost support files with aspire restore
  • Discovering the correct frontend URL before a Playwright handoff
  • Understanding unfamiliar Aspire AppHost APIs before editing C# or TypeScript AppHosts
  • Managing AppHost secrets and CLI config
  • Publishing and deploying Aspire apps, including single named steps with aspire do
  • Adding custom dashboard or resource commands with docs-backed AppHost patterns

Do not use this skill for

  • Non-Aspire .NET applications
  • Container-only workflows that do not involve an Aspire AppHost
  • Replacing normal build and test commands when the task is just compiling code or running unit tests

Default workflow

  1. Confirm that the workspace is an Aspire app and identify the AppHost.
  2. Start the app with aspire start. Use --isolated in git worktrees or whenever shared local state would be risky.
  3. Use aspire wait <resource> before interacting with a resource that needs to be healthy.
  4. Inspect state with aspire describe, then use aspire otel logs, aspire logs, aspire otel traces, and aspire export before making code changes. Display returned data using the formatting rules in references/monitoring.md.
  5. Before adding an integration, introducing a custom dashboard/resource command, or using an unfamiliar AppHost API, use aspire docs search <topic> and aspire docs get <slug> for workflow guidance, then use aspire docs api search <query> --language csharp|typescript and aspire docs api get <id> when you need the API reference entry itself.
  6. Re-run aspire start after AppHost changes. In git worktrees, re-run aspire start --isolated instead of switching to aspire run.

C# AppHosts

When the AppHost is implemented in C# such as AppHost.cs, apphost.cs, or a Program.cs-based AppHost, use Aspire docs for workflow guidance and Aspire API docs for the reference entry before editing.

  • Use aspire docs search <topic> and aspire docs get <slug> when you need the documented workflow or pattern.
  • Use aspire docs api search <query> --language csharp and aspire docs api get <id> when you need the C# API reference entry for a resource builder, extension method, or member.
  • If the dotnet-inspect skill is available, use it to inspect local C# APIs, overloads, and builder chains when you need help understanding how the API surface is exposed in code.
  • Keep dotnet-inspect scoped to understanding APIs and symbols; use Aspire docs for the documented workflow and recommended pattern.

TypeScript AppHosts

When the AppHost is apphost.ts, the .modules/ folder at the project root contains generated TypeScript modules that expose the Aspire APIs available to the AppHost. Common files include .modules/aspire.ts, base.ts, and transport.ts.

  • Do not edit .modules/ directly.
  • Use aspire add <package> to add integrations and regenerate the available APIs.
  • Inspect .modules/aspire.ts after aspire add to see the refreshed API surface.
  • The local tsconfig.json often includes .modules/**/*.ts in its compilation scope.
Show full SKILL.md (406 more words)Show less

Key rules

  • Prefer aspire start over dotnet run for AppHosts. aspire run blocks the terminal and is a poor fit for agent workflows.
  • Re-running aspire start is the restart path. In git worktrees, aspire start --isolated is both the start and restart command. Do not combine aspire stop and aspire run.
  • Use --apphost <path> when the workspace has multiple AppHosts or discovery is ambiguous.
  • Use --format Json when another tool or script needs machine-readable output.
  • Do not guess the integration or command shape for unfamiliar AppHost changes. Use aspire docs search and aspire docs get for the documented pattern, then use aspire docs api search and aspire docs api get when you need the specific reference entry.
  • For unfamiliar C# AppHost APIs, use Aspire API docs as the primary reference and, if available, use dotnet-inspect only to inspect local symbols, overloads, and builder chains.
  • Never install the obsolete Aspire workload.
  • When a TypeScript AppHost uses .modules/, do not edit generated files directly. Use aspire add to regenerate APIs and inspect .modules/aspire.ts afterward.
  • Prefer official docs from aspire.dev.

Common capabilities

  • Use aspire ps when you need to discover running AppHosts before targeting one.
  • Use aspire update when the task is to refresh AppHost package references through the supported CLI workflow.
  • Use aspire doctor as an early diagnostics step when the local Aspire environment looks unhealthy.
  • Use aspire resource, aspire secret, aspire config, aspire publish, aspire deploy, and aspire do when the objective is resource operations, secrets/config management, or deployment.
  • Use aspire restore, aspire cache clear, aspire certs trust, and aspire certs clean when the task is local environment maintenance or recovery.

Playwright CLI

If Playwright CLI is already configured in the environment, use Aspire first to discover the running app and its endpoints, especially when multiple frontends exist. Prefer aspire describe --format Json when the handoff needs to be scriptable or you need to disambiguate which frontend URL Playwright should use, then hand browser testing off to Playwright CLI.

References

© SSWConsulting, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 9 other files (references) in .claude/skills/aspire of SSWConsulting/SSW.VerticalSliceArchitecture.

  • SKILL.md
  • references/agent-workflows.md
  • references/app-commands.md
  • references/csharp-apphosts.md
  • references/deployment.md
  • references/monitoring.md
  • references/playwright-handoff.md
  • references/resource-management.md
  • references/tools-and-configuration.md
  • references/typescript-apphosts.md

Open the folder on GitHubat commit 42e7a70

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in SSWConsulting/SSW.VerticalSliceArchitecture, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Aspire next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Aspire compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Aspire this skillSSWConsulting/SSW.VerticalSliceArchitecture4071 repos~2kAutomated safety check: PassMIT
Playwright Rollmicrosoft/playwright-dotnet3k—~1.9kAutomated safety check: PassMIT
RStudio Selenium to Playwright Migrationrstudio/rstudio5.1k—~3.6kAutomated safety check: PassCustom licence
Playwright Coretestdino-hq/playwright-skill3861 repos~1.4kAutomated safety check: PassMIT
Svelte Testingspences10/sveltest113—~579Automated safety check: PassMIT
API Testingfugazi/test-automation-skills-agents247—~1.5kAutomated safety check: PassMIT

Similar skills

  • Playwright Roll

    microsoft/playwright-dotnet

    Official

    Roll Playwright .NET to a new version

    3k GitHub stars~1.9k tokensUpdated 2 days ago
    Testing & QAAuto-check passed
  • Converts RStudio Python Selenium electron tests into TypeScript Playwright tests, checking each against a live RStudio before counting it as migrated.

    5.1k GitHub stars~3.6k tokensUpdated today
    Testing & QAAuto-check passed
  • Playwright Core

    testdino-hq/playwright-skill

    Battle-tested Playwright patterns for writing and debugging reliable E2E, API, component, visual, accessibility, and security tests.

    386 GitHub starsUsed in 1 repo~1.4k tokens
    Testing & QAAuto-check passed
  • Svelte Testing

    spences10/sveltest

    Fix and create Svelte 5 tests with vitest-browser-svelte and Playwright.

    113 GitHub stars~579 tokensUpdated today
    Testing & QAAuto-check passed
  • API Testing

    fugazi/test-automation-skills-agents

    Test REST and GraphQL endpoint contracts using Playwright request fixture (TypeScript) or REST Assured (Java).

    247 GitHub stars~1.5k tokensUpdated 5 days ago
    Testing & QAAuto-check passed
  • Playwright Login Flows

    andrewyng/context-hub

    Collects reusable Playwright patterns for logging in during end-to-end tests: password forms, OAuth redirects, saved browser state and TOTP two-factor codes.

    14k GitHub stars~715 tokensUpdated 4 mo ago
    Testing & QAAuto-check passed

More from SSWConsulting/SSW.VerticalSliceArchitecture

  • Add Entity

    SSWConsulting/SSW.VerticalSliceArchitecture

    Scaffold a new domain entity or aggregate in this Vertical Slice Architecture template — the entity itself, its strongly typed ID, errors, specification, EF Core configuration, DbSet, the mandatory…

    407 GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Add Slice

    SSWConsulting/SSW.VerticalSliceArchitecture

    Scaffold a slice in this Vertical Slice Architecture template — one use case in its own folder, with its FastEndpoints endpoint, request, response, validator, and summary, plus the Feature and Group…

    407 GitHub stars~2.3k tokensUpdated today
    Auto-check passed
  • Add Adr

    SSWConsulting/SSW.VerticalSliceArchitecture

    Write an Architectural Decision Record in this repo's docs/adr/ following its Log4brains conventions — filename, title, metadata, and the sections that are required versus optional.

    407 GitHub stars~1.5k tokensUpdated today
    Auto-check passed
  • Bump Version

    SSWConsulting/SSW.VerticalSliceArchitecture

    Bump the SSW.VerticalSliceArchitecture.Template NuGet package version to cut a new release.

    407 GitHub stars~841 tokensUpdated today
    Auto-check passed

Categories

Questions about Aspire

What does Aspire do?

A skill your agent uses when the user is working with an Aspire distributed application and needs to operate the AppHost or its resources through the Aspire CLI: start, restart, stop, or wait on the…. VerticalSliceArchitecture.

When should I use Aspire?

Aspire fits situations like: the user is working with an Aspire distributed application and needs to operate the AppHost; its resources through the Aspire CLI: start; wait on the app; inspect resources.

How do I install Aspire in Claude Code?

Run `npx skills add SSWConsulting/SSW.VerticalSliceArchitecture --skill aspire -a claude-code`. Or copy the skill folder (.claude/skills/aspire in SSWConsulting/SSW.VerticalSliceArchitecture) into .claude/skills/aspire in your project. Claude Code loads it when a task matches its description.

How do I install Aspire in Codex?

Run `npx skills add SSWConsulting/SSW.VerticalSliceArchitecture --skill aspire -a codex`. Or copy the skill folder (.claude/skills/aspire in SSWConsulting/SSW.VerticalSliceArchitecture) into .agents/skills/aspire in your project. Codex loads it when a task matches its description.

Can I use Aspire in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add SSWConsulting/SSW.VerticalSliceArchitecture --skill aspire -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/aspire, .gemini/skills/aspire, .github/skills/aspire and .opencode/skills/aspire in your project.

What does Aspire need to run?

Going by SKILL.md and its folder, Aspire needs the command-line tools its instructions call (dotnet). Our summary lists: Docker.

Does Aspire access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Aspire safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Aspire use?

Aspire is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Aspire use?

About 2k tokens (SKILL.md is roughly 8.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.1k tokens, read only when the agent opens those files.

What are the alternatives to Aspire?

Skills that share tags, products or a category with Aspire: Playwright Roll (microsoft/playwright-dotnet, 3k stars), RStudio Selenium to Playwright Migration (rstudio/rstudio, 5.1k stars), Playwright Core (testdino-hq/playwright-skill, 386 stars) and Svelte Testing (spences10/sveltest, 113 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Aspire?

SSWConsulting (a GitHub organization) maintains it in SSWConsulting/SSW.VerticalSliceArchitecture, which has 407 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 8, 2026.

Source: SSWConsulting/SSW.VerticalSliceArchitecture on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.