aspire

Orchestrate .NET Aspire application lifecycle and observability via the Aspire CLI.

7|3|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/eriklieben/agentic-dev-workflow --skill aspire-eriklieben
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aspire
Source: https://github.com/eriklieben/agentic-dev-workflow/tree/main/.claude/skills/aspire
Command: npx skills add https://github.com/eriklieben/agentic-dev-workflow --skill aspire-eriklieben

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill eliminates the complexity of managing distributed .NET Aspire applications by providing a unified interface for lifecycle management, observability, and integration configuration.

Core Features & Use Cases

  • Lifecycle Management: Start, stop, and restart distributed applications with isolated environments for worktrees.
  • Observability: Access structured logs, console output, and distributed traces directly from the CLI.
  • Integration & MCP: Easily add new integrations and interact with resource-specific MCP tools for tasks like database querying.

Quick Start

Use the aspire skill to start the application in an isolated environment and wait for the primary API resource to become healthy.

Frequently Asked Questions about aspire

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

FAQPage Schema
How do I debug .NET Aspire distributed applications locally?

You can debug .NET Aspire distributed applications by orchestrating the app lifecycle through the Aspire CLI and inspecting structured logs, console output, and distributed traces directly in your local development environment.

What is the best way to monitor .NET Aspire resource status during development?

Monitoring .NET Aspire resource status is handled by the Aspire CLI, which provides a unified interface for tracking the lifecycle and health of distributed application resources in isolated local environments.

Do I need the Aspire CLI installed to manage distributed system observability for .NET?

Yes, the Aspire CLI must be installed and accessible in your development environment path to facilitate local development workflows, resource status monitoring, and distributed trace inspection.

Can I use isolated environments for .NET Aspire worktrees when starting applications?

Yes, you can start, stop, and restart .NET Aspire distributed applications using isolated environments specifically configured to support local development workflows across multiple worktrees.

How do I access structured logs and distributed traces for .NET Aspire apps?

Accessing structured logs and distributed traces for .NET Aspire apps is done through the Aspire CLI, which surfaces observability data including console output and resource-specific telemetry.

Are there limitations when adding integrations to .NET Aspire distributed systems?

Adding integrations to .NET Aspire distributed systems requires using the Aspire CLI to interact with resource-specific MCP tools, though the scope of these integrations is limited to the local development environment.