skills.rest
wshaddix
wshaddixCOMMUNITY
Explore all skills by this author →
Website𝕏@wshaddixGitHub

aspire-service-defaults

Generate a shared ServiceDefaults project for .NET Aspire applications.

71|10|Updated Feb 11, 2026
Search Tags:#configuration#resilience#observability#.net#aspire#service defaults
One-click install
npx skills add https://github.com/wshaddix/dotnet-skills --skill aspire-service-defaults-wshaddix
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aspire-service-defaults
Source: https://github.com/wshaddix/dotnet-skills/tree/main/skills/aspire-service-defaults
Command: npx skills add https://github.com/wshaddix/dotnet-skills --skill aspire-service-defaults-wshaddix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill centralizes common configuration for .NET Aspire applications, ensuring consistent observability, health checks, and resilience across all microservices.

Core Features & Use Cases

  • Unified Configuration: Centralizes OpenTelemetry, health checks, service discovery, and HTTP resilience.
  • Cross-Service Consistency: Ensures all services in an Aspire application share the same foundational configuration.
  • Use Case: When building a distributed application with .NET Aspire, use this skill to create a shared ServiceDefaults project that all your microservices (API, Worker, etc.) will reference for consistent telemetry and resilience.

Quick Start

Use the aspire-service-defaults skill to create a new shared ServiceDefaults project for your Aspire application.

Frequently Asked Questions about aspire-service-defaults

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

FAQPage Schema
How do I centralize OpenTelemetry and health checks in a .NET Aspire distributed application?▼

Create a shared ServiceDefaults project that centralizes OpenTelemetry, health checks, service discovery, and HTTP resilience configuration, ensuring all microservices in your .NET Aspire application share consistent foundational settings.

What is the best way to configure HTTP resilience for microservices in .NET Aspire?▼

The best way to configure HTTP resilience is by using a shared ServiceDefaults project to centralize resilience configurations, which all microservices in the .NET Aspire application reference for consistent behavior.

Do I need .NET 9 to set up service defaults for Aspire?▼

Yes, you need .NET 9 and the Aspire SDK to set up and integrate the shared ServiceDefaults project for centralizing service discovery, health checks, and observability in your application.

How does a shared ServiceDefaults project work in .NET Aspire?▼

A shared ServiceDefaults project works by acting as a centralized reference for all microservices, providing unified configuration for OpenTelemetry, health checks, service discovery, and HTTP resilience across distributed systems.

Can I use this approach to standardize service discovery across all my Aspire microservices?▼

Yes, you can standardize service discovery by generating a shared ServiceDefaults project that centralizes service discovery configuration alongside observability and resilience settings for all microservices to reference.

Related Skills

Explore More Software Engineering Skills→
seiggyseiggy
57

aspire-service-defaults

Create a shared .NET Aspire ServiceDefaults project for OpenTelemetry, health checks, service discovery, and HTTP resilience.

Community
Intermediate
roanbrasilroanbrasil
5

service-mesh

Configure Istio and Linkerd service meshes for mTLS, traffic splitting, and tracing.

Community
Advanced
congiuluccongiuluc

aspire-otel

Configure Aspire dashboard and OpenTelemetry for local .NET observability.

Community
Advanced
devingobledevingoble

aspire-service-defaults

Centralize OpenTelemetry, health checks, resilience, and service discovery in .NET Aspire projects.

Community
Intermediate