aspire

Route tasks to Aspire sub-skills for AppHost-based distributed applications.

13|4|Updated Feb 8, 2025

Search Tags:#routing #cli #orchestrator #aspire #apphost #safety-guardrails #distributed-apps

Ready to run

npx skills add https://github.com/jonathanpotts/aspire-nextjs-keycloak --skill aspire-jonathanpotts

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aspire
Source: https://github.com/jonathanpotts/aspire-nextjs-keycloak/tree/main/.agents/skills/aspire
Command: npx skills add https://github.com/jonathanpotts/aspire-nextjs-keycloak --skill aspire-jonathanpotts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Routes tasks to the appropriate Aspire sub-skill (aspire-init, aspireify, aspire-orchestration, aspire-deployment, aspire-monitoring) by detecting an Aspire AppHost and applying safety guardrails, ensuring consistent orchestration across distributed apps.

Core Features & Use Cases

Central routing: directs actions to the correct sub-skill based on repo signals and AppHost presence.
Safety guardrails: enforces safe operating patterns and standard workflows for Aspire-managed projects.
Use cases: bootstrapping new Aspire AppHosts, wiring existing repos, and coordinating multi-skill operations through the Aspire CLI.

Quick Start

Run the Aspire CLI from the repository root and select the aspire skill to begin routing tasks to the appropriate sub-skill.

Frequently Asked Questions about aspire

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

FAQPage Schema

How do I coordinate tasks for .NET Aspire distributed apps?▼

To coordinate tasks for .NET Aspire distributed apps, this top-level router detects the AppHost project and directs actions to the appropriate sub-skill via the Aspire CLI. It validates configuration and enforces safety guardrails for orchestrated workflows.

What is the safest way to manage Aspire AppHost deployments and stop using ad-hoc dotnet commands?▼

The safest way to manage Aspire AppHost deployments is to route operations through the Aspire CLI rather than ad-hoc dotnet or shell workflows. This approach applies safety guardrails and validates configuration before executing start, stop, or deploy commands.

How do I bootstrap and wire an existing repository for Aspire orchestration?▼

To bootstrap and wire an existing repository for Aspire orchestration, run the Aspire CLI from the repository root. The router detects the AppHost presence and directs bootstrapping or wiring tasks to the appropriate initialization sub-skill.

Can I use standard Aspire CLI commands like dashboard and doctor with this orchestrator?▼

Yes, you can use standard Aspire CLI commands like dashboard and doctor with this orchestrator. It supports common Aspire workflows including start, stop, deploy, logs, doctor, and dashboard commands for distributed apps.

Why should I use an AppHost-centric runtime router instead of direct shell workflows for cloud-native .NET deployments?▼

An AppHost-centric runtime router ensures safe, orchestrated actions by validating configuration and enforcing safety guardrails, whereas direct shell workflows bypass these checks and can lead to inconsistent operations across distributed apps.