[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HDKDM4Z1Q8PY5TNP3JS744":3,"skill-same:01M6HDKDM4Z1Q8PY5TNP3JS744":85},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6HDKDM4Z1Q8PY5TNP3JS744","aspire-init",null,"**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, apphost.mts, generated .aspire\u002Fmodules. DO NOT USE FOR: AppHost wiring on an existing AppHost (use aspireify), start\u002Fstop\u002Fwait (use aspire-orchestration), deploy\u002Fpublish (use aspire-deployment), logs\u002Ftraces (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.","microsoft\u002Faspire-skills","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M699Z09A17E8C731AGNTAEVR",94,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire-skills\u002Fblob\u002Fmain\u002Fopencode\u002Fv1\u002Faspire-init\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"init","aspire","aspire init","publish","existing repo","workflow skill","app","drop","modules","install","generated","template","flow","cli","monitoring","logs","run","aspireify","workflow","orchestration","2026-11-10 10:12:30",false,"---\nname: aspire-init\ndescription: >-\n  **WORKFLOW SKILL** - First-run flow for adding Aspire to a repo. Picks `aspire new`\n  (greenfield) or `aspire init` (existing repo), drops the AppHost skeleton, then hands\n  off to `aspireify` for resource wiring.\n  USE FOR: aspire init, aspire new, aspire-starter, aspire-ts-starter, aspire-py-starter,\n  add Aspire to existing repo, scaffold Aspire app, bootstrap Aspire, no AppHost detected,\n  install aspireify, apphost.mts, generated .aspire\u002Fmodules.\n  DO NOT USE FOR: AppHost wiring on an existing AppHost (use aspireify), start\u002Fstop\u002Fwait\n  (use aspire-orchestration), deploy\u002Fpublish (use aspire-deployment), logs\u002Ftraces (use\n  aspire-monitoring), repo that already has an AppHost.\n  INVOKES: aspire CLI (init, new, doctor), aspireify (handoff after skeleton drop).\n  FOR SINGLE OPERATIONS: Run `aspire init` or `aspire new TEMPLATE` directly.\nlicense: MIT\nmetadata:\n  author: Microsoft\n  version: \"0.0.5\"\n---\n\n# Aspire Init\n\n> **First-run only.** This skill owns the skeleton drop and template choice for repositories\n> that do not yet have an Aspire AppHost. Once the skeleton is in place, hand off to\n> [`aspireify`](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire-skills\u002Fblob\u002Fmain\u002Fskills\u002Faspireify\u002FSKILL.md) for the actual resource wiring.\n\n## Prerequisites\n\n| Requirement | Install |\n|-------------|---------|\n| .NET 10.0 SDK | https:\u002F\u002Fdotnet.microsoft.com\u002Fdownload |\n| Node.js `^20.19.0`, `^22.13.0`, or `>=24` (TypeScript AppHost) | https:\u002F\u002Fnodejs.org |\n| Aspire CLI (curl installer) | `curl -sSL https:\u002F\u002Faspire.dev\u002Finstall.sh \\| bash` |\n| Aspire CLI (npm) | `npm install -g @microsoft\u002Faspire-cli` |\n| Aspire CLI (NativeAOT global tool) | `dotnet tool install -g Aspire.Cli` (.NET 10 required) |\n| Diagnose missing prerequisites | `aspire doctor` |\n\n> Aspire also supports Nix, Homebrew, WinGet, mise, and the curl\u002FPowerShell installers.\n> Use the installation method already owned by the user's environment.\n\n## Detection\n\nActivate **only** when adding Aspire to a workspace that does not yet have one. Confirm ALL\nof the following before running `aspire init`:\n\n| Signal | How to Detect | Meaning |\n|--------|---------------|---------|\n| No C# AppHost | No `.csproj` containing `Aspire.AppHost.Sdk` | OK to init |\n| No file-based AppHost | No `apphost.cs` with `#:sdk Aspire.AppHost.Sdk` | OK to init |\n| No TypeScript AppHost | No current `apphost.mts` or legacy `apphost.ts` in the repo | OK to init |\n| No Aspire config | No `aspire.config.json` in repo root | OK to init |\n| User intent | Explicit \"add Aspire\", \"scaffold Aspire\", \"aspire init\" | OK to init |\n\nIf **any** AppHost signal is already present, **do not run `aspire init`**. Route to\n[`aspireify`](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire-skills\u002Fblob\u002Fmain\u002Fskills\u002Faspireify\u002FSKILL.md) (re-wire) or\n[`aspire-orchestration`](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire-skills\u002Fblob\u002Fmain\u002Fskills\u002Faspire-orchestration\u002FSKILL.md) (lifecycle).\n\n## Decision: `aspire new` vs `aspire init`\n\n| Situation | Command | Why |\n|-----------|---------|-----|\n| Empty directory or brand-new project | `aspire new \u003Ctemplate>` | Generates a full starter solution |\n| Existing repo with services to model | `aspire init` | Drops minimal skeleton + `aspire.config.json` next to existing code |\n| User wants a sample to learn from | `aspire new aspire-starter` | Includes ApiService + Web + ServiceDefaults |\n| User wants the smallest possible scaffold | `aspire new aspire-empty` (C#) or `aspire new aspire-ts-empty` (TS) | No resources pre-wired |\n| User wants Python services | `aspire new aspire-py-starter` (TypeScript AppHost drives Python) | **Not** `dotnet new` — that template was removed in 13.3 |\n\nSee [references\u002Ftemplates.md](references\u002Ftemplates.md) for the complete template list and\noptions.\n\n## Workflow A — `aspire new \u003Ctemplate>` (new project)\n\nFor brand-new projects in an empty or non-existent directory:\n\n1. Confirm prerequisites with `aspire doctor` if the CLI install is uncertain.\n2. Pick a template from [references\u002Ftemplates.md](references\u002Ftemplates.md).\n3. Run the template, append `--non-interactive` for agent flows:\n   ```bash\n   aspire new aspire-starter --name MyApp --output .\u002FMyApp --non-interactive\n   ```\n4. The new directory is fully wired by the template — **no aspireify handoff needed**.\n5. Route to [`aspire-orchestration`](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire-skills\u002Fblob\u002Fmain\u002Fskills\u002Faspire-orchestration\u002FSKILL.md) for first run\n   (`aspire start`).\n\n## Workflow B — `aspire init` (existing repo)\n\nFor repositories that already contain services (Express API, .NET API, Python service, etc.)\nand need an AppHost added alongside them:\n\n1. Verify the [Detection](#detection) table — confirm **no** AppHost is present.\n2. Run `aspire init`, choosing language explicitly for non-interactive flows:\n   ```bash\n   aspire init --language csharp --non-interactive\n   # or\n   aspire init --language typescript --non-interactive\n   ```\n3. `aspire init` drops:\n   - The AppHost skeleton (`apphost.cs` with `#:sdk` directives, **or** `apphost.mts` with the\n     generated `.aspire\u002Fmodules\u002F` folder)\n   - AppHost configuration describing language + AppHost path\n   - The **`aspireify`** agent skill into the project's skill directory (same one\n     `aspire agent init` uses). In 13.6+, the chained agent setup preselects the\n     recommended skills, including `aspireify`, and does **not** offer Aspire MCP server\n     configuration. If MCP config is missing after a successful init, that is expected and\n     isn't a defect. MCP is a separate opt-in; see the `aspire` router's *Skills vs. MCP*\n     guidance.\n4. **Hand off to `aspireify`** — `aspire init` does **not** wire resources, projects, or\n   integrations on its own.\n5. After `aspireify` finishes wiring, validate via `aspire start`\n   ([`aspire-orchestration`](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire-skills\u002Fblob\u002Fmain\u002Fskills\u002Faspire-orchestration\u002FSKILL.md)).\n\nIn 13.5, a TypeScript init inside a repo that already has a root `package.json` creates a\nnested `aspire-apphost\u002F` package and points the root `aspire.config.json` at\n`aspire-apphost\u002Fapphost.mts`. A solution-backed C# repo can receive a project-based AppHost;\nnew C# AppHosts enable `AspireUseCliBundle=true` by default. Preserve these generated choices.\n\nSee [references\u002Finit-workflow.md](references\u002Finit-workflow.md) for the full sequence\nincluding what `aspire.config.json` contains and what to do if `aspire init` fails partway.\n\n## Handoff Rules\n\n| After `aspire init` \u002F `aspire new` finishes... | Route To |\n|------------------------------------------------|----------|\n| Skeleton dropped, resources need wiring | → `aspireify` skill (in-plugin or project-local) |\n| Skeleton dropped, validate it starts | → `aspire-orchestration` (run `aspire start`) |\n| New project from template, ready to run | → `aspire-orchestration` |\n| User asks to deploy after init | → `aspire-deployment` |\n| User asks for logs\u002Ftraces after init | → `aspire-monitoring` |\n| Existing AppHost detected — do NOT run init | → `aspireify` (re-wire) or `aspire-orchestration` (lifecycle) |\n\n## Project-Local Skill Override\n\nIf `.agents\u002Fskills\u002Faspire-init\u002FSKILL.md` exists project-locally (legacy install from an\nolder `aspire init` run), **warn the user and defer to it**. The legacy project-local skill\nmay carry repo-specific guidance that should not be overridden by this in-plugin skill.\n\nThe project-local `aspireify` skill (installed by `aspire init`) takes precedence\nover this plugin's in-plugin `aspireify` for the same reason — defer to the project-local\ncopy and warn.\n\n## Error Handling\n\n| Symptom | Cause | Action |\n|---------|-------|--------|\n| `aspire init` reports AppHost already exists | Repo already has an AppHost | Stop. Route to `aspireify` (re-wire) or `aspire-orchestration` (lifecycle) |\n| `aspire init` fails in non-interactive mode without `--language` | Multiple language paths available | Re-run with `--language csharp` or `--language typescript` |\n| `aspire new` rejects `--output` path | Path exists and is non-empty | Use a different `--output` or empty the directory |\n| `aspire` command not found | CLI not installed | `dotnet tool install -g Aspire.Cli` (.NET 10) or `curl -sSL https:\u002F\u002Faspire.dev\u002Finstall.sh \\| bash` |\n| `aspire doctor` reports missing .NET 10 | SDK missing | Install .NET 10 SDK before retrying |\n| `aspire init` succeeded but no `aspireify` skill installed | Agent skill directory not detected, or `aspireify` not selected (13.5 doesn't preselect it) | Run `aspire agent init --non-interactive --skills aspireify` (append `aspireify` to any explicit `--skills` list, keep any `--skill-locations`, and don't add `--mcp`), then continue wiring |\n| `aspire init` succeeded but no MCP config was written | Expected in 13.6+ — chained agent setup does not offer MCP | Don't repair it. Configure MCP only when the user explicitly asks for it (`aspire agent init --mcp` on 13.6+) |\n| Skeleton dropped but resources not wired | Expected — `aspire init` does not wire | Hand off to `aspireify` |\n| 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 |\n\n## References\n\n- [templates.md](references\u002Ftemplates.md) — `aspire new` templates and options\n- [init-workflow.md](references\u002Finit-workflow.md) — `aspire init` flow, `aspire.config.json`\n  layout, and `aspireify` handoff\n- [aspire-13-5-breaking-changes.md](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire-skills\u002Fblob\u002Fmain\u002Fskills\u002Faspire\u002Freferences\u002Faspire-13-5-breaking-changes.md) —\n  13.5 migrations, CLI-bundle behavior, and fixes for affected releases\n","# Aspire Init\n\n> **First-run only.** This skill owns the skeleton drop and template choice for repositories\n> that do not yet have an Aspire AppHost. Once the skeleton is in place, hand off to\n> [`aspireify`](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire-skills\u002Fblob\u002Fmain\u002Fskills\u002Faspireify\u002FSKILL.md) for the actual resource wiring.\n\n## Prerequisites\n\n| Requirement | Install |\n|-------------|---------|\n| .NET 10.0 SDK | https:\u002F\u002Fdotnet.microsoft.com\u002Fdownload |\n| Node.js `^20.19.0`, `^22.13.0`, or `>=24` (TypeScript AppHost) | https:\u002F\u002Fnodejs.org |\n| Aspire CLI (curl installer) | `curl -sSL https:\u002F\u002Faspire.dev\u002Finstall.sh \\| bash` |\n| Aspire CLI (npm) | `npm install -g @microsoft\u002Faspire-cli` |\n| Aspire CLI (NativeAOT global tool) | `dotnet tool install -g Aspire.Cli` (.NET 10 required) |\n| Diagnose missing prerequisites | `aspire doctor` |\n\n> Aspire also supports Nix, Homebrew, WinGet, mise, and the curl\u002FPowerShell installers.\n> Use the installation method already owned by the user's environment.\n\n## Detection\n\nActivate **only** when adding Aspire to a workspace that does not yet have one. Confirm ALL\nof the following before running `aspire init`:\n\n| Signal | How to Detect | Meaning |\n|--------|---------------|---------|\n| No C# AppHost | No `.csproj` containing `Aspire.AppHost.Sdk` | OK to init |\n| No file-based AppHost | No `apphost.cs` with `#:sdk Aspire.AppHost.Sdk` | OK to init |\n| No TypeScript AppHost | No current `apphost.mts` or legacy `apphost.ts` in the repo | OK to init |\n| No Aspire config | No `aspire.config.json` in repo root | OK to init |\n| User intent | Explicit \"add Aspire\", \"scaffold Aspire\", \"aspire init\" | OK to init |\n\nIf **any** AppHost signal is already present, **do not run `aspire init`**. Route to\n[`aspireify`](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire-skills\u002Fblob\u002Fmain\u002Fskills\u002Faspireify\u002FSKILL.md) (re-wire) or\n[`aspire-orchestration`](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire-skills\u002Fblob\u002Fmain\u002Fskills\u002Faspire-orchestration\u002FSKILL.md) (lifecycle).\n\n## Decision: `aspire new` vs `aspire init`\n\n| Situation | Command | Why |\n|-----------|---------|-----|\n| Empty directory or brand-new project | `aspire new \u003Ctemplate>` | Generates a full starter solution |\n| Existing repo with services to model | `aspire init` | Drops minimal skeleton + `aspire.config.json` next to existing code |\n| User wants a sample to learn from | `aspire new aspire-starter` | Includes ApiService + Web + ServiceDefaults |\n| User wants the smallest possible scaffold | `aspire new aspire-empty` (C#) or `aspire new aspire-ts-empty` (TS) | No resources pre-wired |\n| User wants Python services | `aspire new aspire-py-starter` (TypeScript AppHost drives Python) | **Not** `dotnet new` — that template was removed in 13.3 |\n\nSee [references\u002Ftemplates.md](references\u002Ftemplates.md) for the complete template list and\noptions.\n\n## Workflow A — `aspire new \u003Ctemplate>` (new project)\n\nFor brand-new projects in an empty or non-existent directory:\n\n1. Confirm prerequisites with `aspire doctor` if the CLI install is uncertain.\n2. Pick a template from [references\u002Ftemplates.md](references\u002Ftemplates.md).\n3. Run the template, append `--non-interactive` for agent flows:\n   ```bash\n   aspire new aspire-starter --name MyApp --output .\u002FMyApp --non-interactive\n   ```\n4. The new directory is fully wired by the template — **no aspireify handoff needed**.\n5. Route to [`aspire-orchestration`](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire-skills\u002Fblob\u002Fmain\u002Fskills\u002Faspire-orchestration\u002FSKILL.md) for first run\n   (`aspire start`).\n\n## Workflow B — `aspire init` (existing repo)\n\nFor repositories that already contain services (Express API, .NET API, Python service, etc.)\nand need an AppHost added alongside them:\n\n1. Verify the [Detection](#detection) table — confirm **no** AppHost is present.\n2. Run `aspire init`, choosing language explicitly for non-interactive flows:\n   ```bash\n   aspire init --language csharp --non-interactive\n   # or\n   aspire init --language typescript --non-interactive\n   ```\n3. `aspire init` drops:\n   - The AppHost skeleton (`apphost.cs` with `#:sdk` directives, **or** `apphost.mts` with the\n     generated `.aspire\u002Fmodules\u002F` folder)\n   - AppHost configuration describing language + AppHost path\n   - The **`aspireify`** agent skill into the project's skill directory (same one\n     `aspire agent init` uses). In 13.6+, the chained agent setup preselects the\n     recommended skills, including `aspireify`, and does **not** offer Aspire MCP server\n     configuration. If MCP config is missing after a successful init, that is expected and\n     isn't a defect. MCP is a separate opt-in; see the `aspire` router's *Skills vs. MCP*\n     guidance.\n4. **Hand off to `aspireify`** — `aspire init` does **not** wire resources, projects, or\n   integrations on its own.\n5. After `aspireify` finishes wiring, validate via `aspire start`\n   ([`aspire-orchestration`](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire-skills\u002Fblob\u002Fmain\u002Fskills\u002Faspire-orchestration\u002FSKILL.md)).\n\nIn 13.5, a TypeScript init inside a repo that already has a root `package.json` creates a\nnested `aspire-apphost\u002F` package and points the root `aspire.config.json` at\n`aspire-apphost\u002Fapphost.mts`. A solution-backed C# repo can receive a project-based AppHost;\nnew C# AppHosts enable `AspireUseCliBundle=true` by default. Preserve these generated choices.\n\nSee [references\u002Finit-workflow.md](references\u002Finit-workflow.md) for the full sequence\nincluding what `aspire.config.json` contains and what to do if `aspire init` fails partway.\n\n## Handoff Rules\n\n| After `aspire init` \u002F `aspire new` finishes... | Route To |\n|------------------------------------------------|----------|\n| Skeleton dropped, resources need wiring | → `aspireify` skill (in-plugin or project-local) |\n| Skeleton dropped, validate it starts | → `aspire-orchestration` (run `aspire start`) |\n| New project from template, ready to run | → `aspire-orchestration` |\n| User asks to deploy after init | → `aspire-deployment` |\n| User asks for logs\u002Ftraces after init | → `aspire-monitoring` |\n| Existing AppHost detected — do NOT run init | → `aspireify` (re-wire) or `aspire-orchestration` (lifecycle) |\n\n## Project-Local Skill Override\n\nIf `.agents\u002Fskills\u002Faspire-init\u002FSKILL.md` exists project-locally (legacy install from an\nolder `aspire init` run), **warn the user and defer to it**. The legacy project-local skill\nmay carry repo-specific guidance that should not be overridden by this in-plugin skill.\n\nThe project-local `aspireify` skill (installed by `aspire init`) takes precedence\nover this plugin's in-plugin `aspireify` for the same reason — defer to the project-local\ncopy and warn.\n\n## Error Handling\n\n| Symptom | Cause | Action |\n|---------|-------|--------|\n| `aspire init` reports AppHost already exists | Repo already has an AppHost | Stop. Route to `aspireify` (re-wire) or `aspire-orchestration` (lifecycle) |\n| `aspire init` fails in non-interactive mode without `--language` | Multiple language paths available | Re-run with `--language csharp` or `--language typescript` |\n| `aspire new` rejects `--output` path | Path exists and is non-empty | Use a different `--output` or empty the directory |\n| `aspire` command not found | CLI not installed | `dotnet tool install -g Aspire.Cli` (.NET 10) or `curl -sSL https:\u002F\u002Faspire.dev\u002Finstall.sh \\| bash` |\n| `aspire doctor` reports missing .NET 10 | SDK missing | Install .NET 10 SDK before retrying |\n| `aspire init` succeeded but no `aspireify` skill installed | Agent skill directory not detected, or `aspireify` not selected (13.5 doesn't preselect it) | Run `aspire agent init --non-interactive --skills aspireify` (append `aspireify` to any explicit `--skills` list, keep any `--skill-locations`, and don't add `--mcp`), then continue wiring |\n| `aspire init` succeeded but no MCP config was written | Expected in 13.6+ — chained agent setup does not offer MCP | Don't repair it. Configure MCP only when the user explicitly asks for it (`aspire agent init --mcp` on 13.6+) |\n| Skeleton dropped but resources not wired | Expected — `aspire init` does not wire | Hand off to `aspireify` |\n| 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 |\n\n## References\n\n- [templates.md](references\u002Ftemplates.md) — `aspire new` templates and options\n- [init-workflow.md](references\u002Finit-workflow.md) — `aspire init` flow, `aspire.config.json`\n  layout, and `aspireify` handoff\n- [aspire-13-5-breaking-changes.md](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire-skills\u002Fblob\u002Fmain\u002Fskills\u002Faspire\u002Freferences\u002Faspire-13-5-breaking-changes.md) —\n  13.5 migrations, CLI-bundle behavior, and fixes for affected releases\n",{"name":5,"license":15,"metadata":49,"description":7},{"author":12,"version":50},"0.0.5","main","1117facb04b403dd2fc15f048bc0e63fc67c502f","opencode\u002Fv1\u002Faspire-init",12,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire-skills","https:\u002F\u002Faspire.dev\u002Fget-started\u002Faspire-skills\u002F","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-11 08:52:06",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add microsoft\u002Faspire-skills --skill aspire-init",{"tool":67,"command":68},"bunx","bunx skills add microsoft\u002Faspire-skills --skill aspire-init",{"tool":70,"command":71},"pnpm","pnpm dlx skills add microsoft\u002Faspire-skills --skill aspire-init","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire-skills\u002Fblob\u002Fmain\u002Fopencode\u002Fv1\u002Faspire-init\u002FSKILL.md",true,[75,81],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Finit-workflow.md","REFERENCE","参考文档",8063,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire-skills\u002Fblob\u002Fmain\u002Fopencode\u002Fv1\u002Faspire-init\u002Freferences\u002Finit-workflow.md",{"path":82,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Ftemplates.md",4161,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire-skills\u002Fblob\u002Fmain\u002Fopencode\u002Fv1\u002Faspire-init\u002Freferences\u002Ftemplates.md",[86,111,133,151,158,177],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":98,"publishedAt":44},"01M6HDNG43XGF64N14PV9VGGKB","aspire-terminals","**WORKFLOW SKILL** - Author and automate Aspire terminals. USE FOR: WithTerminal, withTerminal, TerminalService, TerminalLaunchOptions, docked terminals, terminal prompts, PromptTerminalAsync, TerminalPlacement, AspireTerminalKey, WithRepl, withRepl, aspire terminal ps\u002Fattach\u002Ftape play, VHS tapes for Aspire, or terminal screen\u002Finput automation. DO NOT USE FOR: generic shell commands, ordinary AppHost resource wiring (aspireify), start\u002Fstop\u002Fwait (aspire-orchestration), logs\u002Ftraces or browser telemetry (aspire-monitoring), deployment (aspire-deployment), or nonterminal Interaction Service prompts (aspireify). INVOKES: Aspire docs\u002FAPI lookup, AppHost edits, Aspire terminal CLI; aspire-orchestration for lifecycle validation. FOR SINGLE OPERATIONS: Choose the terminal owner and lifetime first, then read the matching reference.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire-skills\u002Fblob\u002Fmain\u002Fskills\u002Faspire-terminals\u002FSKILL.md",[92,93],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":94,"categoryName":95,"taxonomyType":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[25,99,37,100,43,42,41,101,39,38,102,103,104,105,106,107,108,109,110,29],"aspire terminals","terminal","browser","start","api","choose","read","attach","commands","interaction","screen","input",{"skillNo":112,"name":41,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":121,"publishedAt":44},"01M6HDMDCMMBTXTWKBVGJM0615","**WORKFLOW SKILL** - Wire Aspire AppHosts or repair TypeScript AppHost toolchains. Scans the repo, proposes a resource graph, edits C#, file-based C#, or TypeScript AppHosts, wires ServiceDefaults + OTel, validates with `aspire start`, then stops. USE FOR: wire\u002Fscaffold AppHost, add Postgres\u002FRedis\u002FRabbit\u002FMongo, connect frontend to API, after `aspire init`, AddNextJsApp, AddViteApp, WithBrowserLogs, Interaction Service, command arguments, apphost.cs, apphost.mts, unified withEnvironment, .aspire\u002Fmodules refusal, config\u002Fsecrets, TS dependency restore, pnpm\u002Fyarn\u002Fbun, or Yarn Classic. DO NOT USE FOR: skeleton drop (aspire-init), lifecycle-only start\u002Fstop\u002Fwait\u002Frestart or `aspire update --migrate` (aspire-orchestration), publish\u002Fdeploy\u002Fdestroy (aspire-deployment), logs\u002Ftraces (aspire-monitoring), terminal authoring or automation (aspire-terminals). INVOKES: aspire CLI, AppHost source edits, ServiceDefaults wiring. FOR SINGLE OPERATIONS: Run `aspire add PACKAGE` directly for a one-off integration.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire-skills\u002Fblob\u002Fmain\u002Fopencode\u002Fv1\u002Faspireify\u002FSKILL.md",[116,119,120],{"categoryNo":117,"categoryName":118,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":94,"categoryName":95,"taxonomyType":96,"taxonomyTypeDesc":97},[41,122,100,123,124,125,40,126,127,39,38,102,128,129,32,130,70,131,108,132],"frontend","typescript","config","connect","update","yarn","migrate","command","stop","authoring","wait",{"skillNo":134,"name":25,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":142,"publishedAt":44},"01M6HDM7MR6SFZHAM32RNM2MKB","**WORKFLOW SKILL** - Aspire router. Detects AppHosts, enforces guardrails, and selects the right sub-skill. USE FOR: Aspire AppHost, Aspire CLI, distributed app, cloud-native .NET, aspire start\u002Fstop\u002Fresource\u002Fdeploy\u002Fdestroy\u002Fpublish\u002Finit\u002Fnew\u002Fadd\u002Fwait\u002Fdescribe\u002Fps\u002Flogs\u002Fotel, aspire agent init, WithBrowserLogs, WithTerminal, TerminalService, terminal prompts, WithRepl, tapes, Interaction Service, apphost.mts, TS package managers, Yarn Classic, custom resource commands, .aspire\u002Fmodules recovery, ProjectResource to DotnetProjectResource migration, or Playwright URL discovery. DO NOT USE FOR: non-Aspire projects or ordinary build\u002Ftest tasks. INVOKES: aspire-init, aspireify, aspire-project-v2-migration, aspire-orchestration, aspire-deployment, aspire-monitoring, aspire-terminals. FOR SINGLE OPERATIONS: Route directly to the matching sub-skill.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire-skills\u002Fblob\u002Fmain\u002Fopencode\u002Fv1\u002Faspire\u002FSKILL.md",[138,141],{"categoryNo":139,"categoryName":140,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[25,43,42,24,41,143,39,38,27,144,145,146,32,147,148,30,108,29,149,150],"tasks","Guardrails","projects","router","route","project","URL","managers",{"skillNo":152,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":157,"publishedAt":44},"01M6HDM2RMF6Q15YHYTS7G9SWZ","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire-skills\u002Fblob\u002Fmain\u002Fopencode\u002Fv1\u002Faspire-terminals\u002FSKILL.md",[155,156],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":94,"categoryName":95,"taxonomyType":96,"taxonomyTypeDesc":97},[25,99,37,100,43,42,41,101,39,38,102,103,104,105,106,107,108,109,110,29],{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":165,"publishedAt":44},"01M6HDKY1PNCDYBC317440ZHZ0","aspire-project-v2-migration","**WORKFLOW SKILL** - Safely migrates eligible Aspire 13.6+ AppHosts from legacy ProjectResource APIs to experimental DotnetProjectResource APIs after a per-resource assessment and explicit approval of exact edits. USE FOR: assess or migrate existing AddProject, addProject, AddCSharpApp, addCSharpApp, or AddBlazorGateway resources to Project v2; migrate ProjectResource to DotnetProjectResource; clean up the resulting obsolete AppHost ProjectReference edges. DO NOT USE FOR: upgrading Aspire versions, creating\u002Fwiring a new AppHost, Azure Functions migration, generic source modernization, ordinary C# resource wiring or adding a new AddProject resource (use aspireify), publishing, or build\u002Flifecycle diagnostics. INVOKES: Aspire docs\u002FAPI lookup, aspire add\u002Frestore\u002Fstart\u002Fwait, AppHost and package edits. FOR SINGLE OPERATIONS: Assess first; never edit from a generic migration request alone.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire-skills\u002Fblob\u002Fmain\u002Fopencode\u002Fv1\u002Faspire-project-v2-migration\u002FSKILL.md",[164],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[25,166,167,148,42,41,168,169,170,102,103,128,171,172,173,174,132,29,175,176],"aspire project v2 migration","migration","diagnostics","modernization","assessment","edit","never","up","clean","resources","source",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":185,"publishedAt":44},"01M6HDKQX187B70G2MK589KWC7","aspire-orchestration","**WORKFLOW SKILL** — Manage Aspire lifecycle in VS Code or the CLI. WHEN: \"start or stop my Aspire app\", \"aspire_apphost_start\", \"aspire_apphost_stop\", \"notEditorOwned\", \"ambiguousSession\", \"aspire start\", \"aspire stop\", \"aspire wait\", resource restart, file-lock errors (MSB3491 or CS2012), port conflicts, git worktrees, \"--isolated\", \"aspire update --self\", \"aspire update --migrate\", \"aspire describe --include-hidden\", \"aspire stop --force\", \"aspire stop --force --volumes\", integration discovery, default watch, or hot reload. INVOKES: VS Code lifecycle tools first when exposed; Aspire CLI for readiness, inspection, resource operations, isolated worktree starts, and allowed fallbacks. DO NOT USE FOR: deploy\u002Fpublish\u002Fdestroy (aspire-deployment), logs\u002Ftraces\u002Fmetrics (aspire-monitoring), terminal authoring\u002Fattach\u002Ftapes (aspire-terminals), or AppHost code and resource wiring (aspireify). FOR SINGLE OPERATIONS: Load the matching editor tool first; follow exact-target, worktree-isolation, and stop-result rules.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire-skills\u002Fblob\u002Fmain\u002Fopencode\u002Fv1\u002Faspire-orchestration\u002FSKILL.md",[183,184],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":94,"categoryName":95,"taxonomyType":96,"taxonomyTypeDesc":97},[43,25,186,42,41,187,39,38,27,128,188,189,190,106,191,30,29,192,193,194],"aspire orchestration","code","git worktrees","default","conflicts","self","port","errors","lock"]