aspire

Orchestrate local cloud-native .NET services with AppHost resources and service discovery.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/shahdanish/vibepos --skill aspire-shahdanish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aspire
Source: https://github.com/shahdanish/vibepos/tree/main/skills/aspire
Command: npx skills add https://github.com/shahdanish/vibepos --skill aspire-shahdanish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the friction of coordinating multiple .NET services locally by giving you a consistent way to start dependencies, configure observability, and enable service-to-service discovery.

Core Features & Use Cases

  • AppHost orchestration: Define infrastructure resources (databases, caches, message brokers) and wire application projects into a single run configuration.
  • Service defaults for consistency: Apply OpenTelemetry, health checks, and resilience behaviors across services without repeating boilerplate.
  • Service discovery and integrations: Use built-in Aspire integrations so services can discover each other and receive connection configuration automatically.
  • Observability via the Aspire dashboard: Centralize local tracing, logging, and metrics for faster debugging.

Quick Start

Load the aspire skill and configure your AppHost Program.cs to create an AppHost builder, add your infrastructure resources, reference your application projects, and run the dashboard-backed local orchestration.

Frequently Asked Questions about aspire

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

FAQPage Schema
How do I orchestrate multiple .NET microservices locally for development?

Local .NET microservices orchestration coordinates AppHost resources and service startup flows to manage dependencies. It wires infrastructure resources and application projects into a single run configuration.

What is .NET Aspire AppHost and how does it handle service discovery?

AppHost orchestration defines infrastructure resources like databases and caches, wiring application projects into a single run configuration. It leverages built-in Aspire integrations so services can discover each other and receive connection configuration automatically without hardcoded connection strings.

How do I configure OpenTelemetry and health checks across multiple .NET services?

Configuring OpenTelemetry and health checks across multiple .NET services uses ServiceDefaults to apply consistent observability. This applies resilience behaviors and health monitoring across services without repeating boilerplate configuration code.

How do I avoid hardcoded connection strings when coordinating local .NET application dependencies?

Avoiding hardcoded connection strings in local .NET applications leverages built-in Aspire integrations for service discovery. These integrations allow services to discover each other and automatically receive connection configuration for resources like databases and message brokers.

Can I centralize local tracing, logging, and metrics for my .NET cloud-native applications?

Centralizing local tracing, logging, and metrics for .NET cloud-native applications is achieved via the Aspire dashboard. It provides a centralized interface for local observability data, enabling faster debugging of coordinated microservices.

Does local .NET service orchestration require defining infrastructure resources in AppHost?

Local .NET service orchestration requires defining infrastructure resources and project references in AppHost. You must configure the AppHost builder with your application projects and dependencies to run the dashboard-backed local orchestration.