All skills
github avatar

/aspire

@e765718 official
by githubgithub/awesome-copilot40k stars
5,040

Aspire skill covering the Aspire CLI, AppHost orchestration, service discovery, integrations, MCP server, VS Code extension, Dev Containers, GitHub Codespaces, templates, dashboard, and deployment. Use when the user asks to create, run, debug, configure, deploy, or troubleshoot an Aspire distributed application.

Use this Skill: https://skilld.dev/gh/github/awesome-copilot/aspire

This session only. Nothing lands on disk.

referencescli-reference.md

≈2.2k tokens on demand. Your agent reads this file only when SKILL.md points to it.

CLI Reference — Complete Command Reference

The Aspire CLI (aspire) is the primary interface for creating, running, and publishing distributed applications. It is cross-platform and installed standalone (not coupled to the .NET CLI, though dotnet commands also work).

Tested against: Aspire CLI 13.1.0


Installation

# Linux / macOS
curl -sSL https://aspire.dev/install.sh | bash

# Windows PowerShell
irm https://aspire.dev/install.ps1 | iex

# Verify
aspire --version

# Update the CLI itself
aspire update --self

Global Options

All commands support these options:

Option Description
-d, --debug Enable debug logging to the console
--non-interactive Disable all interactive prompts and spinners
--wait-for-debugger Wait for a debugger to attach before executing
-?, -h, --help Show help and usage information
--version Show version information

Command Reference

aspire new

Create a new project from a template.

aspire new [<template>] [options]

# Options:
#   -n, --name <name>        Project name
#   -o, --output <dir>       Output directory
#   -s, --source <source>    NuGet source for templates
#   -v, --version <version>  Version of templates to use
#   --channel <channel>      Channel (stable, daily)

# Examples:
aspire new aspire-starter
aspire new aspire-starter -n MyApp -o ./my-app
aspire new aspire-ts-cs-starter
aspire new aspire-py-starter
aspire new aspire-apphost-singlefile

Available templates:

  • aspire-starter — ASP.NET Core/Blazor starter + AppHost + tests
  • aspire-ts-cs-starter — ASP.NET Core/React + AppHost
  • aspire-py-starter — FastAPI/React + AppHost
  • aspire-apphost-singlefile — Empty single-file AppHost

aspire init

Initialize Aspire in an existing project or solution.

aspire init [options]

# Options:
#   -s, --source <source>    NuGet source for templates
#   -v, --version <version>  Version of templates to use
#   --channel <channel>      Channel (stable, daily)

# Example:
cd my-existing-solution
aspire init

Adds AppHost and ServiceDefaults projects to an existing solution. Interactive prompts guide you through selecting which projects to orchestrate.

aspire run

Start all resources locally using the DCP (Developer Control Plane).

aspire run [options] [-- <additional arguments>]

# Options:
#   --project <path>       Path to AppHost project file

# Examples:
aspire run
aspire run --project ./src/MyApp.AppHost

Behavior:

  1. Builds the AppHost project
  2. Starts the DCP engine
  3. Creates resources in dependency order (DAG)
  4. Waits for health checks on gated resources
  5. Opens the dashboard in the default browser
  6. Streams logs to the terminal

Press Ctrl+C to gracefully stop all resources.

aspire add

Add a hosting integration to the AppHost.

aspire add [<integration>] [options]

# Options:
#   --project <path>         Target project file
#   -v, --version <version>  Version of integration to add
#   -s, --source <source>    NuGet source for integration

# Examples:
aspire add redis
aspire add postgresql
aspire add mongodb

aspire publish (Preview)

Generate deployment manifests from the AppHost resource model.

aspire publish [options] [-- <additional arguments>]

# Options:
#   --project <path>                   Path to AppHost project file
#   -o, --output-path <path>           Output directory (default: ./aspire-output)
#   --log-level <level>                Log level (trace, debug, information, warning, error, critical)
#   -e, --environment <env>            Environment (default: Production)
#   --include-exception-details        Include stack traces in pipeline logs

# Examples:
aspire publish
aspire publish --output-path ./deploy
aspire publish -e Staging

aspire config

Manage Aspire configuration settings.

aspire config <subcommand>

# Subcommands:
#   get <key>              Get a configuration value
#   set <key> <value>      Set a configuration value
#   list                   List all configuration values
#   delete <key>           Delete a configuration value

# Examples:
aspire config list
aspire config set telemetry.enabled false
aspire config get telemetry.enabled
aspire config delete telemetry.enabled

aspire cache

Manage disk cache for CLI operations.

aspire cache <subcommand>

# Subcommands:
#   clear                  Clear all cache entries

# Example:
aspire cache clear

aspire deploy (Preview)

Deploy the contents of an Aspire apphost to its defined deployment targets.

aspire deploy [options] [-- <additional arguments>]

# Options:
#   --project <path>                   Path to AppHost project file
#   -o, --output-path <path>           Output path for deployment artifacts
#   --log-level <level>                Log level (trace, debug, information, warning, error, critical)
#   -e, --environment <env>            Environment (default: Production)
#   --include-exception-details        Include stack traces in pipeline logs
#   --clear-cache                      Clear deployment cache for current environment

# Example:
aspire deploy --project ./src/MyApp.AppHost

aspire do (Preview)

Execute a specific pipeline step and its dependencies.

aspire do <step> [options] [-- <additional arguments>]

# Options:
#   --project <path>                   Path to AppHost project file
#   -o, --output-path <path>           Output path for artifacts
#   --log-level <level>                Log level (trace, debug, information, warning, error, critical)
#   -e, --environment <env>            Environment (default: Production)
#   --include-exception-details        Include stack traces in pipeline logs

# Example:
aspire do build-images --project ./src/MyApp.AppHost

aspire update (Preview)

Update integrations in the Aspire project, or update the CLI itself.

aspire update [options]

# Options:
#   --project <path>       Path to AppHost project file
#   --self                 Update the Aspire CLI itself to the latest version
#   --channel <channel>    Channel to update to (stable, daily)

# Examples:
aspire update                          # Update project integrations
aspire update --self                   # Update the CLI itself
aspire update --self --channel daily   # Update CLI to daily build

aspire mcp

Manage the MCP (Model Context Protocol) server.

aspire mcp <subcommand>

# Subcommands:
#   init    Initialize MCP server configuration for detected agent environments
#   start   Start the MCP server
aspire mcp init
aspire mcp init

# Interactive — detects your AI environment and creates config files.
# Supported environments:
# - VS Code (GitHub Copilot)
# - Copilot CLI
# - Claude Code
# - OpenCode

Generates the appropriate configuration file for your detected AI tool. See MCP Server for details.

aspire mcp start
aspire mcp start

# Starts the MCP server using STDIO transport.
# This is typically invoked by your AI tool, not run manually.

Commands That Do NOT Exist

The following commands are not valid in Aspire CLI 13.1. Use alternatives:

Invalid Command Alternative
aspire build Use dotnet build ./AppHost
aspire test Use dotnet test ./Tests
aspire dev Use aspire run (includes file watching)
aspire list Use aspire new --help for templates, aspire add for integrations

.NET CLI equivalents

The dotnet CLI can perform some Aspire tasks:

Aspire CLI .NET CLI Equivalent
aspire new aspire-starter dotnet new aspire-starter
aspire run dotnet run --project ./AppHost
N/A dotnet build ./AppHost
N/A dotnet test ./Tests

The Aspire CLI adds value with publish, deploy, add, mcp, config, cache, do, and update — commands that have no direct dotnet equivalent.

Source: SKILL.md on GitHub

1 warning16d5 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    The skill provides comprehensive documentation and tools for using .NET Aspire, a distributed application orchestration tool. It includes official installation methods from trusted sources and describes standard development workflows. No malicious patterns or security risks were identified.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

  • Runlayer7mo

    10/10 files flagged

  • ZeroLeaks5mo

    1 finding · Score: 82/100

Signed by skilld at e765718. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 20 hours ago.

Activeupdated 8 months ago
  • aspire
  • dotnet
  • distributed-applications
  • orchestration
  • containers
  • polyglot
  • service-discovery
  • docker
  • kubernetes

README badge

README badge for github/awesome-copilot/aspire

Orchestrates polyglot distributed applications from a single .NET AppHost project, managing containers, executables, and cloud resources regardless of whether workloads are C#, Python, JavaScript, Go, Java, Rust, or other languages. Use when building, running, debugging, or deploying multi-service applications with automatic service discovery and observability via the built-in dashboard.

Generated from the current SKILL.md.

Does Aspire only work with .NET services?
No. Aspire is polyglot — the AppHost itself is .NET, but it orchestrates services written in Python, Go, Java, JavaScript/TypeScript, Rust, Bun, Deno, and PowerShell as containers or executables.
What do I need to install to use Aspire?
.NET SDK 10.0+, a container runtime (Docker Desktop, Podman, or Rancher Desktop), and optionally an IDE like VS Code with C# Dev Kit or Visual Studio 2022.
How do services discover each other in Aspire?
Automatic service discovery happens via environment variables like `ConnectionStrings__<name>` and `services__<name>__http__0`, set by the AppHost at runtime.
Can I test an Aspire application without running it manually?
Yes. The `Aspire.Hosting.Testing` package lets you spin up the full AppHost in xUnit, MSTest, or NUnit for integration tests.
What is the difference between aspire run and aspire publish?
`aspire run` starts all resources locally using the DCP engine and automatically launches the dashboard. `aspire publish` generates deployment manifests for Docker, Kubernetes, Azure Container Apps, or App Service.

Generated from the current SKILL.md. These answers refresh after source changes.