aspire

Route Aspire AppHost tasks to sub-skills based on AppHost state.

Updated Nov 11, 2025
One-click install
npx skills add https://github.com/eruvalca/Calcio --skill aspire-eruvalca
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aspire
Source: https://github.com/eruvalca/Calcio/tree/main/.agents/skills/aspire
Command: npx skills add https://github.com/eruvalca/Calcio --skill aspire-eruvalca

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Coordinating Aspire deployments across AppHost states is error-prone without a single routing layer. This Skill detects the AppHost state and directs tasks to the appropriate sub-skill (aspire-init, aspireify, aspire-orchestration, aspire-deployment, or aspire-monitoring), enforcing safety guardrails and reducing misrouting.

Core Features & Use Cases

  • Unified routing to the correct Aspire sub-skill based on AppHost presence and configuration (wired vs unwired).
  • Enforces safety guardrails and lifecycle integrity during bootstrap, wiring, deployment, and monitoring workflows.
  • Applies to both C# and TypeScript AppHosts, seamlessly switching between bootstrap and runtime operations.

Quick Start

Ask this skill to route your project to the correct Aspire sub-skill based on AppHost detection.

Frequently Asked Questions about aspire

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

FAQPage Schema
How do I route Aspire AppHost tasks to the correct workflow stage?

Aspire AppHost tasks are routed by detecting AppHost presence, checking for aspire.config.json, and identifying the .aspire directory to direct operations to the correct sub-skill.

What signals are used to detect Aspire AppHost state in a project?

Aspire AppHost state detection relies on three primary signals: AppHost presence, the existence of an aspire.config.json file, and the presence of a .aspire directory.

Can I use Aspire orchestration workflows with both C# and TypeScript AppHosts?

Yes, Aspire workflow routing applies to both C# and TypeScript AppHosts, seamlessly switching between bootstrap and runtime operations while enforcing safety guardrails.

What's the best way to manage Aspire lifecycle integrity across bootstrap and deployment?

Using a unified routing layer for Aspire lifecycle management enforces safety guardrails and reduces misrouting across bootstrap, wiring, deployment, and monitoring workflows.

Why does my Aspire deployment keep misrouting between wired and unwired AppHost states?

Aspire deployment misrouting occurs without a single routing layer to detect the AppHost state, which this approach resolves by directing tasks to the appropriate sub-skill based on configuration.

Do I need an aspire.config.json file before initializing Aspire workflows?

Detecting an aspire.config.json file is a key routing signal for Aspire workflows, but the bootstrap sub-skill can initialize the project before the configuration is fully wired.