aspire

Orchestrate .NET Aspire AppHost resources with service defaults and service discovery.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/Maj3D10/Training-Platform --skill aspire-maj3d10
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aspire
Source: https://github.com/Maj3D10/Training-Platform/tree/main/.agent/skills/aspire
Command: npx skills add https://github.com/Maj3D10/Training-Platform --skill aspire-maj3d10

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

.NET developers often struggle to coordinate multiple services for local development, including service startup, connectivity, observability, and consistent configuration, which leads to fragile scripts and duplicated setup work.

Core Features & Use Cases

  • AppHost orchestration: Define an AppHost that starts and wires infrastructure (databases, Redis, RabbitMQ, etc.) alongside application services.
  • Service defaults: Centralize OpenTelemetry, health checks, resilience, and service discovery so every service follows consistent conventions.
  • Built-in integrations & discovery: Use Aspire integrations to avoid hardcoded connection strings and enable service-to-service communication via service discovery.
  • Aspire dashboard observability: Inspect traces, logs, and metrics for local development without manually setting up separate tooling.

Quick Start

Load the aspire skill and set up a .NET Aspire AppHost with Postgres, Redis, and RabbitMQ, then connect an API and worker to them using WithReference and service defaults for telemetry and health checks.

Frequently Asked Questions about aspire

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate local .NET services for multi-service development?

Centralize OpenTelemetry, health checks, resilience, and service discovery by adopting shared .NET Aspire service defaults. This ensures every service follows consistent conventions for local development without manually configuring separate observability tooling.

How do I avoid hardcoded connection strings when using .NET Aspire?

Avoid hardcoded connection strings by using built-in .NET Aspire integrations and WithReference. This enables service discovery and automatic service-to-service communication, allowing infrastructure like Postgres and Redis to wire dynamically during local development.

Does .NET Aspire work with OpenTelemetry for local observability?

.NET Aspire works with OpenTelemetry by centralizing it within service defaults. You use the built-in Aspire dashboard to inspect traces, logs, and metrics directly during local development without manually setting up separate observability tooling.

What do I need to set up before configuring .NET Aspire orchestration?

You need an AppHost that references infrastructure and projects before configuring .NET Aspire orchestration. This AppHost acts as the entry point, requiring your application services to adopt shared service defaults for telemetry and health checks.

What are the limitations of using .NET Aspire for service orchestration?

.NET Aspire orchestration is designed for local development of multi-service systems, meaning it coordinates AppHost resources and service defaults for local environments. It relies on Aspire integrations, requiring an AppHost structure and avoiding hardcoded connection strings.