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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.5 KB |
| references/init-workflow.md | markdown | 5.8 KB |
| references/templates.md | markdown | 3.8 KB |
references/templates.md
View on GitHub# `aspire new` Templates
Reference for choosing and invoking templates with `aspire new`. Source:
https://aspire.dev/reference/cli/commands/aspire-new/
## Template List
| Template | Description | AppHost Language |
|----------|-------------|------------------|
| `aspire-starter` | Starter App (ASP.NET Core / Blazor) | C# |
| `aspire-ts-cs-starter` | Starter App (ASP.NET Core / React) | C# |
| `aspire-py-starter` | Starter App (FastAPI / React) | **TypeScript** (drives Python) |
| `aspire-ts-starter` | Starter App (Express / React) | TypeScript |
| `aspire-empty` | Minimal scaffold, no resources pre-wired | C# |
| `aspire-ts-empty` | Minimal scaffold, no resources pre-wired | TypeScript |
> **Important — Python starter changed in 13.3.** `dotnet new aspire-py-starter` was removed.
> The current path is `aspire new aspire-py-starter`, and the AppHost is **TypeScript**, not
> C#. The TypeScript AppHost orchestrates the FastAPI service plus the React frontend.
## Common Options
| Option | Purpose |
|--------|---------|
| `-n, --name` | Name of the project to create |
| `-o, --output` | Output path. Defaults to `./<template-name>` (auto-suffixed if non-empty) |
| `-s, --source` | NuGet source for the project templates |
| `-v, --version` | Version of the project templates to use |
| `--channel` | Template channel: `stable` (default), `staging`, `daily` |
| `--non-interactive` | **Required for agent execution.** Disables prompts and spinners |
| `--nologo` | Suppress startup banner / telemetry notice |
| `--suppress-agent-init` | Skip the post-create prompt to configure AI agent environments |
| `-l, --log-level` | `Critical`, `Debug`, `Error`, `Information`, `None`, `Trace`, `Warning` |
## Template-Specific Options
### `aspire-py-starter`
| Option | Values | Default |
|--------|--------|---------|
| `--use-redis-cache` | `true` / `false` | Prompts interactively |
```bash
aspire new aspire-py-starter --use-redis-cache true --non-interactive
```
## Interactive Prompts (avoid by passing flags)
| Prompt | What It Decides | Skip With |
|--------|------------------|-----------|
| Project name | Output directory name | `--name <value>` |
| Template version | Which release to use | `--version <value>` |
| Output folder | Where files land | `--output <value>` |
| Use `*.dev.localhost` URLs? | HTTPS subdomain launch profile vs `http://localhost:<port>` | Pass `--non-interactive` to take the default (No, standard localhost) |
If a project picks `*.dev.localhost`, the user must trust the developer certificate first:
```bash
aspire certs trust
```
## Output Path Validation
- Invalid characters (e.g., null bytes) are rejected with an error.
- Existing **non-empty** directories are rejected — pick a new `--output` or empty the target.
- When `--output` is omitted, the CLI derives the directory from the template name and
appends a numeric suffix (`./aspire-starter-2`, `./aspire-starter-3`, ...) if the default
already exists.
## Examples
```bash
# Interactive — CLI prompts for name, output, version
aspire new aspire-starter
# Non-interactive C# empty scaffold pinned to a specific version
aspire new aspire-empty --version <version> --name aspireapp --output ./dev --non-interactive
# Pre-release templates from the daily channel
aspire new aspire-starter --channel daily
# TypeScript-AppHost-driven Python starter with Redis cache
aspire new aspire-py-starter --use-redis-cache true --name py-shop --output ./py-shop --non-interactive
```
## When `aspire new` Is Wrong
| Situation | Use Instead |
|-----------|-------------|
| Repo already contains services to model | `aspire init` (Workflow B in [SKILL.md](../SKILL.md)) |
| AppHost already exists in the repo | `aspireify` (re-wire) or `aspire-orchestration` (lifecycle) |
| Need to add an integration to an existing AppHost | `aspire add <package>` (handled by `aspire-orchestration`) |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 119k | Updated | Claude CodeCodex | Verified | Install |
| 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: 118k | Updated | Claude CodeCodex | Verified | Install |