skills.rest
Movchanets
MovchanetsCOMMUNITY
Explore all skills by this author →
GitHub

aspire-init

Initialize Aspire AppHost support in repositories lacking apphost.cs or apphost.ts.

Updated May 5, 2026
Search Tags:#typescript#microservices#scaffolding#dotnet#aspire#apphost#service wiring
One-click install
npx skills add https://github.com/Movchanets/Microservices_Learning --skill aspire-init-movchanets
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aspire-init
Source: https://github.com/Movchanets/Microservices_Learning/tree/main/.agents/skills/aspire-init
Command: npx skills add https://github.com/Movchanets/Microservices_Learning --skill aspire-init-movchanets

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It removes the friction of adding Aspire to a repository that does not yet have an AppHost, so you can bootstrap orchestration without manually assembling the starter structure.

Core Features & Use Cases

  • First-run Aspire setup: Chooses the right path for a brand-new workspace or an existing service repository.
  • Skeleton generation: Creates the minimal AppHost entrypoint and Aspire configuration needed to begin wiring a system.
  • Workflow handoff: Directs the next step to Aspire wiring and orchestration skills after the scaffold is in place.
  • Use case: A team with several services in a mature repo can add Aspire support quickly, then continue with resource integration and startup validation.

Quick Start

Ask the assistant to add Aspire to this repository by initializing the appropriate AppHost and then handing off to Aspire wiring.

Frequently Asked Questions about aspire-init

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

FAQPage Schema
How do I add Aspire orchestration to an existing repository that does not have an AppHost?▼

Aspire setup for an existing repository detects missing AppHost artifacts and creates the minimal apphost.cs or apphost.ts entrypoint along with aspire.config.json. This scaffolds the starter structure automatically so you can begin wiring services.

What is the best way to bootstrap Aspire for a mature microservices repo?▼

The best way to bootstrap Aspire for a mature microservices repo is to use a first-run initialization workflow that selects the right scaffold path and creates the minimal AppHost artifacts before handing off to resource wiring.

Can I set up Aspire in a repository with both TypeScript and .NET services?▼

Yes, you can set up Aspire in a repository with both TypeScript and .NET services. The initialization workflow creates either an apphost.cs or apphost.ts file based on your service stack and generates the required aspire.config.json.

What do I need to do after the Aspire AppHost scaffold is generated?▼

After the Aspire AppHost scaffold is generated, you need to hand off to Aspire wiring and orchestration workflows to connect your system resources and complete the service integration and startup validation.

Does initializing Aspire on an existing service repository require manual configuration of the aspire.config.json?▼

No, initializing Aspire on an existing service repository does not require manual configuration of aspire.config.json. The setup process automatically detects missing AppHost artifacts and creates the minimal configuration file for you.

Related Skills

Explore More Software Engineering Skills→
dotnetdotnet
13

ci-crash-dump

Identify crashed Helix work items and retrieve crash artifacts from dotnet CI runs.

Official
Advanced
elbrunoelbruno
46

aspire-init

Scaffold an Aspire AppHost skeleton and generate aspire.config.json.

Community
Advanced
MarcelMichauMarcelMichau
1

aspire

Route Aspire AppHost tasks through the Aspire CLI.

Community
Advanced
AndreKuraitAndreKurait

agents-get-started

Scaffold and deploy a new AgentCore project across supported agent frameworks.

Community
Intermediate