aspire-configuration

Map Aspire resources to explicit environment-variable configuration keys.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/tvcosta/ai-customer-service --skill aspire-configuration-tvcosta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aspire-configuration
Source: https://github.com/tvcosta/ai-customer-service/tree/main/.claude/skills/aspire-configuration
Command: npx skills add https://github.com/tvcosta/ai-customer-service --skill aspire-configuration-tvcosta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configure Aspire AppHost to emit explicit app configuration via environment variables, reducing coupling to Aspire clients and service discovery.

Core Features & Use Cases

  • Explicit resource-to-config mapping: AppHost translates resources into concrete environment variables.
  • Avoids Aspire client packages in application code; keeps apps portable and production-ready.
  • Supports feature toggles, test overrides, and production parity by surfacing all config values as env vars or config files.

Quick Start

Start by wiring AppHost resources and verify each output is exposed as explicit environment variables in the application configuration.

Frequently Asked Questions about aspire-configuration

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

FAQPage Schema
How do I configure Aspire environment variables without coupling my app to Aspire clients?

You can configure Aspire environment variables by using the AppHost to map resources to explicit application configuration keys. This approach removes the need for Aspire client packages in your app code, ensuring it remains portable and production-ready.

What is the best way to achieve production parity with Aspire AppHost configuration?

Achieving production parity with Aspire AppHost involves translating resources into concrete environment variables or config files. This explicit resource-to-config mapping supports feature toggles and test overrides while keeping apps decoupled from service discovery.

Can I use Aspire for local development without adding service discovery dependencies to my production code?

Yes, you can use Aspire for local development without adding service discovery dependencies by requiring explicit environment-variable-based configuration mapping. The AppHost handles the translation, keeping your application code free of Aspire clients.

Why does my Aspire application code require Aspire client packages to resolve resources?

Your application code requires Aspire client packages because it lacks explicit resource-to-config mapping. By configuring the AppHost to emit explicit application configuration via environment variables, you reduce coupling and eliminate the need for these client packages.

How do I wire AppHost resources to output explicit environment variables in Aspire?

To wire AppHost resources, start by configuring the AppHost to translate resources into concrete environment variables. You then verify that each output is exposed as explicit environment variables within your application configuration for production parity.