aspire-init

por microsoft

**WORKFLOW SKILL** - First-run flow for adding Aspire to a repo. Picks `aspire new` (greenfield) or `aspire init` (existing repo), drops the AppHost skeleton,…

npx skills add https://github.com/microsoft/aspire-skills --skill aspire-init
Descargar ZIPGitHub
87

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
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 prerequisitesaspire 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:

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 current apphost.mts or legacy apphost.ts in the repoOK 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.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)
  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).

In 13.5, a TypeScript init inside a repo that already has a root package.json creates a nested aspire-apphost/ package and points the root aspire.config.json at aspire-apphost/apphost.mts. A solution-backed C# repo can receive a project-based AppHost; new C# AppHosts enable AspireUseCliBundle=true by default. Preserve these generated choices.

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
Existing TypeScript AppHost still uses apphost.tsLegacy entry point and package graphHand off to aspire-orchestration, which owns approval and aspire update --migrate --yes --non-interactive; return to aspireify only for later source authoring

References

Más skills de microsoft

oss-growth
microsoft
Persona de growth hacker de OSS
agent-framework-azure-ai-py
microsoft
Crea agentes de Azure AI Foundry usando el SDK de Python de Microsoft Agent Framework (agent-framework-azure-ai). Úsalo al crear agentes persistentes con AzureAIAgentsProvider, usando herramientas alojadas (intérprete de código, búsqueda de archivos, búsqueda web), integrando servidores MCP, gestionando hilos de conversación o implementando respuestas en streaming. Cubre herramientas de función, salidas estructuradas y agentes con múltiples herramientas.
development
airunway-aks-setup
microsoft
Configura AI Runway en AKS: desde un clúster vacío hasta un modelo en ejecución. Incluye verificación del clúster, instalación del controlador, evaluación de GPU, configuración del proveedor y primer despliegue. CUÁNDO: "configurar AI Runway", "incorporar clúster AKS", "instalar AI Runway", "configuración de airunway", "desplegar modelo en AKS", "inferencia GPU en AKS", "configuración de KAITO en AKS", "ejecutar LLM en AKS", "vLLM en AKS", "configurar servicio de modelos en AKS", "controlador de AI Runway".
devops
appinsights-instrumentation
microsoft
Guía para instrumentar aplicaciones web con Azure Application Insights. Proporciona patrones de telemetría, configuración del SDK y referencias de configuración. CUÁNDO: cómo instrumentar una aplicación, SDK de App Insights, patrones de telemetría, qué es App Insights, guía de Application Insights, ejemplos de instrumentación, mejores prácticas de APM.
devops
applicationinsights-web-ts
microsoft
Instrumenta aplicaciones web/navegador con el SDK de JavaScript de Application Insights (@microsoft/applicationinsights-web). Úsalo para monitoreo de usuarios reales (RUM): vistas de página, clics, dependencias AJAX/fetch, excepciones, eventos personalizados y trazas de agentes GenAI del lado del navegador correlacionadas con trazas de OpenTelemetry del backend. Cubre el script de carga del SDK y la configuración npm, extensiones de frameworks (React, React Native, Angular), Click Analytics, inicializadores de telemetría y convenciones semánticas de GenAI de OTel para spans de agentes/herramientas/modelos emitidos desde el navegador.
devops
azure-ai-anomalydetector-java
microsoft
Cree aplicaciones de detección de anomalías con el SDK de Azure AI Anomaly Detector para Java. Úselo al implementar detección de anomalías univariadas/multivariadas, análisis de series temporales o monitoreo impulsado por IA.
development
azure-ai-language-conversations-py
microsoft
Implementa el reconocimiento del lenguaje conversacional (CLU) utilizando el SDK de Python azure-ai-language-conversations. Úsalo al trabajar con ConversationAnalysisClient para analizar la intención y las entidades de la conversación, crear funciones de NLP o integrar el reconocimiento del lenguaje en aplicaciones.
development
azure-ai-ml-py
microsoft
SDK v2 de Azure Machine Learning para Python. Úselo para áreas de trabajo de ML, trabajos, modelos, conjuntos de datos, cómputo y canalizaciones. Disparadores: "azure-ai-ml", "MLClient", "workspace", "model registry", "training jobs", "datasets".
development