aspire-init

Initialize Aspire application skeletons and select templates via the Aspire CLI.

Updated May 21, 2026
One-click install
npx skills add https://github.com/nymankla/archery --skill aspire-init-nymankla
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aspire-init
Source: https://github.com/nymankla/archery/tree/main/.agents/skills/aspire-init
Command: npx skills add https://github.com/nymankla/archery --skill aspire-init-nymankla

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires aspire-cli, and includes scripts (resource) and assets (resource) components.

What problem does it solve?

This Skill addresses the initial setup of an Aspire application, guiding users through creating a new project or adding Aspire to an existing repository.

Core Features & Use Cases

  • Initial Setup: Offers two options, 'aspire new' for greenfield projects and 'aspire init' for existing repositories.
  • Skeleton Creation: Provides the basic AppHost skeleton necessary for further development.
  • Template Selection: Allows choosing from a variety of templates depending on the project requirements.
  • Resource Wiring: Handles the basic configuration needed for an Aspire application, preparing for the subsequent steps.

Quick Start

Run 'aspire init' to add Aspire to an existing repository and generate the required AppHost skeleton.

Frequently Asked Questions about aspire-init

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

FAQPage Schema
How do I bootstrap an Aspire application for initial setup?

To bootstrap an Aspire application, run 'aspire init' to generate the AppHost skeleton in an existing repository, or use 'aspire new' for greenfield projects to prepare for resource wiring.

What is the difference between adding Aspire to an existing repo versus a new project?

Adding Aspire to an existing repository uses 'aspire init' to inject the AppHost skeleton, while 'aspire new' bootstraps a complete greenfield project structure from scratch using the Aspire CLI.

Do I need the aspire-cli installed to initialize my AppHost?

Yes, you need the aspire-cli installed because the Skill utilizes it for skeleton drop and template selection to properly prepare the AppHost for resource wiring and development.

How does template selection work when creating an Aspire AppHost?

Template selection during Aspire AppHost creation allows you to choose from various project templates depending on your requirements, configuring the skeleton before final resource configuration.

What is the best way to prepare an Aspire application for resource wiring?

The best way to prepare for resource wiring is initializing the application skeleton and selecting templates via the Aspire CLI, which sets up the AppHost for subsequent 'aspireify' configuration.

Why does my Aspire setup stop after generating the skeleton?

Aspire setup stops after skeleton generation because this first-run flow handles initial setup and template selection, intentionally preparing the AppHost for a subsequent 'aspireify' step to finalize resource configuration.