skills.rest
Zuul86
Zuul86COMMUNITY
Explore all skills by this author →
GitHub

aspire-init

Initialize .NET Aspire support by adding an AppHost skeleton to a repository.

1|Updated Nov 26, 2021
Search Tags:#microservices#scaffolding#dotnet#initialization#aspire#apphost
One-click install
npx skills add https://github.com/Zuul86/WeatherStation --skill aspire-init-zuul86
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aspire-init
Source: https://github.com/Zuul86/WeatherStation/tree/main/.agents/skills/aspire-init
Command: npx skills add https://github.com/Zuul86/WeatherStation --skill aspire-init-zuul86

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers correctly add.NET Aspire support to new or existing repositories by choosing the right initialization workflow and avoiding duplicate AppHost setup.

Core Features & Use Cases

  • Aspire Project Initialization: Guides the use of aspire new for greenfield projects and aspire init for existing repositories without an AppHost.
  • Environment Validation: Checks prerequisites, detects existing Aspire configurations, and prevents unsafe initialization paths.
  • Workflow Handoff: Prepares the repository for resource wiring by handing off to aspireify after the initial skeleton is created.
  • Use Case: A developer with an existing API and frontend repository can use this Skill to add an Aspire AppHost skeleton, configure the workspace, and continue with service orchestration.

Quick Start

Use the aspire-init skill to add Aspire support to my existing repository and prepare it for resource 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 .NET Aspire to an existing repository?▼

To add .NET Aspire to an existing repository, you use the aspire init workflow to generate an AppHost skeleton, validate prerequisites, and prepare the workspace for subsequent resource orchestration.

What is the difference between aspire new and aspire init for scaffolding?▼

The aspire new workflow scaffolds greenfield Aspire projects from scratch, whereas aspire init bootstraps existing repositories by adding an AppHost skeleton without duplicating existing project configurations.

Do I need an existing AppHost configuration to use aspire init?▼

No, aspire init is designed for environments without an AppHost configuration. It validates prerequisites to prevent unsafe initialization paths and avoids duplicate AppHost setup in repositories.

Can I initialize Aspire for microservices in a greenfield project?▼

Yes, you can initialize Aspire for microservices in greenfield projects by using the aspire new workflow to establish the correct AppHost scaffold and prepare for resource wiring.

What happens after the Aspire AppHost skeleton is created?▼

After the Aspire AppHost skeleton is created, the workflow prepares a handoff to aspireify for subsequent resource orchestration, allowing you to configure service dependencies and microservices wiring.

Why does aspire init require environment validation before scaffolding?▼

Aspire init requires environment validation to detect existing Aspire configurations, verify prerequisites, and prevent unsafe initialization paths that could corrupt your current repository setup.

Related Skills

Explore More Software Engineering Skills→
tomblytombly

aspire-init

Insert an AppHost skeleton and aspire.config.json into repositories.

Community
Intermediate
jonathanpottsjonathanpotts
13

aspire-init

Generate an AppHost skeleton and aspire.config.json for repositories lacking Aspire support.

Community
Advanced
MovchanetsMovchanets

aspireify

Wire Aspire AppHost resources and service references into a runnable local development graph.

Community
Advanced
ojrojasojrojas

aspire-init

Initialize .NET Aspire AppHost scaffolding for existing repositories.

Community
Advanced