aspire-init

Initialize .NET Aspire AppHost scaffolding for existing repositories.

Updated Jul 14, 2026

Search Tags:#scaffolding #orchestration #dotnet #initialization #aspire #apphost

Ready to run

npx skills add https://github.com/ojrojas/OroIdentityServer --skill aspire-init-ojrojas

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers correctly initialize.NET Aspire support in repositories by selecting the right bootstrap workflow and avoiding incorrect setup on projects that already contain an AppHost.

Core Features & Use Cases

Aspire Initialization Workflow: Guides the choice between creating a new Aspire project and adding Aspire support to an existing repository.
Environment Validation: Checks for existing AppHost files, configuration, and prerequisites before initialization.
Use Case: Add Aspire orchestration scaffolding to an existing application repository, then prepare it for resource wiring through the appropriate follow-up workflow.

Quick Start

Use the aspire-init skill to add Aspire support to this existing repository and determine the correct initialization path.

Frequently Asked Questions about aspire-init

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

FAQPage Schema

How do I add .NET Aspire orchestration to an existing repository?▼

Aspire initialization scaffolds the AppHost project and applies distributed application orchestration to existing codebases. It solves the problem of correctly configuring .NET Aspire support without causing setup conflicts in repositories that already contain AppHost files.

What's the best way to initialize an Aspire AppHost without breaking existing configuration?▼

Validating the environment before initializing Aspire ensures existing AppHost files and prerequisites are detected. This prevents incorrect setup on projects that already contain Aspire configuration and confirms the repository is ready for distributed application orchestration.

Do I need the Aspire CLI installed to bootstrap a new distributed application project?▼

Aspire CLI validation is required to initialize AppHost scaffolding and select starter templates. The CLI checks for existing AppHost files and prerequisites before applying distributed application orchestration to your codebase.

Can I use aspire init to create a new AppHost setup if my repository has no existing Aspire configuration?▼

Yes, aspire init creates new AppHost setups for repositories without existing Aspire configuration. The initialization workflow selects starter templates and provides handoff guidance to subsequent Aspire workflows for resource wiring.

What happens after Aspire initialization scaffolding is complete?▼

After Aspire initialization completes, the workflow provides handoff guidance to subsequent Aspire workflows for resource wiring. This prepares the AppHost project for further distributed application orchestration tasks.