Skip to content

ecoDriverltd/FoundryAgentsExperiment / .agents/skills/aspire-init

aspire-init

Flagged

**WORKFLOW SKILL** - First-run flow for adding Aspire to a repo. Picks `aspire new` (greenfield) or `aspire init` (existing repo), drops the AppHost skeleton, then hands off to `aspireify` for resource wiring. USE FOR: aspire init, aspire new, aspire-starter, aspire-ts-starter, aspire-py-starter, add Aspire to existing repo, scaffold Aspire app, bootstrap Aspire, no AppHost detected, install aspireify, generated .aspire/modules. DO NOT USE FOR: AppHost wiring on an existing AppHost (use aspireify), start/stop/wait (use aspire-orchestration), deploy/publish (use aspire-deployment), logs/traces (use aspire-monitoring), repo that already has an AppHost. INVOKES: aspire CLI (init, new, doctor), aspireify (handoff after skeleton drop). FOR SINGLE OPERATIONS: Run `aspire init` or `aspire new TEMPLATE` directly.

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

RequirementInstall
.NET 10.0 SDKhttps://dotnet.microsoft.com/download
Aspire CLI (curl installer)curl -sSL https://aspire.dev/install.sh | bash
Aspire CLI (NativeAOT global tool)dotnet tool install -g Aspire.Cli (.NET 10 required)
Diagnose missing prerequisitesaspire doctor

Aspire ships the CLI as a NativeAOT .NET global tool — instant startup, no JIT warmup. The curl/PowerShell installer remains supported for environments without .NET 10.

Detection

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

SignalHow to DetectMeaning
No C# AppHostNo .csproj containing Aspire.AppHost.SdkOK to init
No file-based AppHostNo apphost.cs with #:sdk Aspire.AppHost.SdkOK to init
No TypeScript AppHostNo apphost.ts in repo rootOK to init
No Aspire configNo aspire.config.json in repo rootOK to init
User intentExplicit "add Aspire", "scaffold Aspire", "aspire init"OK to init

If any AppHost signal is already present, do not run aspire init. Route to aspireify (re-wire) or aspire-orchestration (lifecycle).

Decision: aspire new vs aspire init

SituationCommandWhy
Empty directory or brand-new projectaspire new <template>Generates a full starter solution
Existing repo with services to modelaspire initDrops minimal skeleton + aspire.config.json next to existing code
User wants a sample to learn fromaspire new aspire-starterIncludes ApiService + Web + ServiceDefaults
User wants the smallest possible scaffoldaspire new aspire-empty (C#) or aspire new aspire-ts-empty (TS)No resources pre-wired
User wants Python servicesaspire new aspire-py-starter (TypeScript AppHost drives Python)Not dotnet new — that template was removed in 13.3

See references/templates.md for the complete template list and options.

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

For brand-new projects in an empty or non-existent directory:

  1. Confirm prerequisites with aspire doctor if the CLI install is uncertain.
  2. Pick a template from references/templates.md.
  3. Run the template, append --non-interactive for agent flows:
    aspire new aspire-starter --name MyApp --output ./MyApp --non-interactive
    
  4. The new directory is fully wired by the template — no aspireify handoff needed.
  5. Route to aspire-orchestration for first run (aspire start).

Workflow B — aspire init (existing repo)

For repositories that already contain services (Express API, .NET API, Python service, etc.) and need an AppHost added alongside them:

  1. Verify the Detection table — confirm no AppHost is present.
  2. Run aspire init, choosing language explicitly for non-interactive flows:
    aspire init --language csharp --non-interactive
    # or
    aspire init --language typescript --non-interactive
    
  3. aspire init drops:
    • The AppHost skeleton (apphost.cs with #:sdk directives, or apphost.ts 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)
  4. Hand off to aspireify — aspire init does not wire resources, projects, or integrations on its own.
  5. After aspireify finishes wiring, validate via aspire start (aspire-orchestration).

See references/init-workflow.md for the full sequence including what aspire.config.json contains and what to do if aspire init fails partway.

Handoff Rules

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)

Project-Local Skill Override

If .agents/skills/aspire-init/SKILL.md exists project-locally (legacy install from an older aspire init run), warn the user and defer to it. The legacy project-local skill may carry repo-specific guidance that should not be overridden by this in-plugin skill.

The project-local aspireify skill (installed by aspire init) takes precedence over this plugin's in-plugin aspireify for the same reason — defer to the project-local copy and warn.

Error Handling

SymptomCauseAction
aspire init reports AppHost already existsRepo already has an AppHostStop. Route to aspireify (re-wire) or aspire-orchestration (lifecycle)
aspire init fails in non-interactive mode without --languageMultiple language paths availableRe-run with --language csharp or --language typescript
aspire new rejects --output pathPath exists and is non-emptyUse a different --output or empty the directory
aspire command not foundCLI not installeddotnet tool install -g Aspire.Cli (.NET 10) or curl -sSL https://aspire.dev/install.sh | bash
aspire doctor reports missing .NET 10SDK missingInstall .NET 10 SDK before retrying
aspire init succeeded but no aspireify skill installedAgent skill directory not detectedRun aspire agent init to install aspireify, then continue wiring
Skeleton dropped but resources not wiredExpected — aspire init does not wireHand off to aspireify

References

writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 321kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall