aspire-init

microsoft/aspire-skillsDeveloper ToolsAudit failedSnapshot 852b2ec9923f

Installs: 0

Summary

SKILL.md

Aspire Init

First-run only. This skill owns the skeleton drop and template choice for repositories that do not yet have an Aspire AppHost. Once the skeleton is in place, hand off to aspireify for the actual resource wiring.

Prerequisites

Requirement	Install
.NET 10.0 SDK	https://dotnet.microsoft.com/download
Node.js `^20.19.0`, `^22.13.0`, or `>=24` (TypeScript AppHost)	https://nodejs.org
Aspire CLI (curl installer)	`curl -sSL https://aspire.dev/install.sh \| bash`
Aspire CLI (npm)	`npm install -g @microsoft/aspire-cli`
Aspire CLI (NativeAOT global tool)	`dotnet tool install -g Aspire.Cli` (.NET 10 required)
Diagnose missing prerequisites	`aspire doctor`

Aspire also supports Nix, Homebrew, WinGet, mise, and the curl/PowerShell installers. Use the installation method already owned by the user's environment.

Detection

Activate only when adding Aspire to a workspace that does not yet have one. Confirm ALL of the following before running aspire init:

Signal	How to Detect	Meaning
No C# AppHost	No `.csproj` containing `Aspire.AppHost.Sdk`	OK to init
No file-based AppHost

Situation	Command	Why
Empty directory or brand-new project	`aspire new <template>`	Generates a full starter solution
Existing repo with services to model	`aspire init`	Drops minimal skeleton + `aspire.config.json` next to existing code
User wants a sample to learn from	`aspire new aspire-starter`	Includes ApiService + Web + ServiceDefaults
User wants the smallest possible scaffold	`aspire new aspire-empty` (C#) or `aspire new aspire-ts-empty` (TS)	No resources pre-wired
User wants Python services	`aspire new aspire-py-starter` (TypeScript AppHost drives Python)	Not `dotnet new` — that template was removed in 13.3

Confirm prerequisites with aspire doctor if the CLI install is uncertain.
Pick a template from references/templates.md.

Run the template, append --non-interactive for agent flows:

aspire new aspire-starter --name MyApp --output ./MyApp --non-interactive

The new directory is fully wired by the template — no aspireify handoff needed.
Route to aspire-orchestration for first run (aspire start).

Verify the Detection table — confirm no AppHost is present.

Run aspire init, choosing language explicitly for non-interactive flows:

aspire init --language csharp --non-interactive
# or
aspire init --language typescript --non-interactive

aspire init drops:
- The AppHost skeleton (apphost.cs with #:sdk directives, or apphost.mts with the generated .aspire/modules/ folder)
- AppHost configuration describing language + AppHost path
- The aspireify agent skill into the project's skill directory (same one aspire agent init uses)
Hand off to aspireify — aspire init does not wire resources, projects, or integrations on its own.
After aspireify finishes wiring, validate via aspire start (aspire-orchestration).

After `aspire init` / `aspire new` finishes...	Route To
Skeleton dropped, resources need wiring	→ `aspireify` skill (in-plugin or project-local)
Skeleton dropped, validate it starts	→ `aspire-orchestration` (run `aspire start`)
New project from template, ready to run	→ `aspire-orchestration`
User asks to deploy after init	→ `aspire-deployment`
User asks for logs/traces after init	→ `aspire-monitoring`
Existing AppHost detected — do NOT run init	→ `aspireify` (re-wire) or `aspire-orchestration` (lifecycle)

Symptom	Cause	Action
`aspire init` reports AppHost already exists	Repo already has an AppHost	Stop. Route to `aspireify` (re-wire) or `aspire-orchestration` (lifecycle)
`aspire init` fails in non-interactive mode without `--language`	Multiple language paths available	Re-run with `--language csharp` or `--language typescript`
`aspire new` rejects `--output` path	Path exists and is non-empty	Use a different `--output` or empty the directory
`aspire` command not found	CLI not installed	`dotnet tool install -g Aspire.Cli` (.NET 10) or `curl -sSL https://aspire.dev/install.sh \| bash`
`aspire doctor` reports missing .NET 10	SDK missing	Install .NET 10 SDK before retrying
`aspire init` succeeded but no `aspireify` skill installed	Agent skill directory not detected	Run `aspire agent init` to install `aspireify`, then continue wiring
Skeleton dropped but resources not wired	Expected — `aspire init` does not wire	Hand off to `aspireify`
Existing TypeScript AppHost still uses `apphost.ts`	Legacy entry point and package graph	Hand off to `aspire-orchestration`, which owns approval and `aspire update --migrate --yes --non-interactive`; return to aspireify only for later source authoring

aspire-init

Summary

SKILL.md

Aspire Init

Prerequisites

Detection

Decision: `aspire new` vs `aspire init`

Workflow A — `aspire new <template>` (new project)

Workflow B — `aspire init` (existing repo)

Handoff Rules

Project-Local Skill Override

Error Handling

References

Related skills

aspire-init

Summary

Aspire Init

Prerequisites

Detection

Decision: aspire new vs aspire init

Workflow A — aspire new <template> (new project)

Workflow B — aspire init (existing repo)

Handoff Rules

Project-Local Skill Override

Error Handling

References

Related skills

Decision: `aspire new` vs `aspire init`

Workflow A — `aspire new <template>` (new project)

Workflow B — `aspire init` (existing repo)