Wire an Aspire AppHost by scanning repos, proposing resource graphs, and validating with aspire start.
npx skills add https://github.com/codebytes/btt --skill aspireify-codebytes
Please help me install this Agent Skill. Skill: aspireify Source: https://github.com/codebytes/btt/tree/main/.agents/skills/aspireify Command: npx skills add https://github.com/codebytes/btt --skill aspireify-codebytes
aspire init drops an empty AppHost skeleton, developers must manually figure out how to model their services, databases, and frontends as Aspire resources. This Skill automates that wiring: it scans the repository, proposes a resource graph, edits the AppHost (C#, file-based C#, or TypeScript), wires ServiceDefaults and OpenTelemetry, and validates the result end to end. ## Core Features & Use Cases - Repository Scanning and Resource Graph Proposal: Detects .NET projects, Node/Python services, docker-compose dependencies, and hardcoded connection strings, then proposes a typed Aspire resource graph (Postgres, Redis, RabbitMQ, MongoDB, Next.js, Vite) for user confirmation before editing. - Multi-Language AppHost Authoring: Edits SDK-style C# AppHosts, file-based apphost.cs, and TypeScript apphost.ts using verified APIs from aspire docs, while refusing to edit generated .aspire/modules/ files. - ServiceDefaults and Validation: Wires Aspire.ServiceDefaults for OpenTelemetry, health checks, and service discovery, then validates with aspire start --non-interactive and aspire wait before self-deactivating. - Use Case: You just ran aspire init in a repo with a .NET API, a Redis container in docker-compose, and a Next.js frontend. This Skill detects all three, proposes AddPostgres/AddRedis/AddNextJsApp wiring with WithReference and WaitFor, edits the AppHost, and confirms a clean start. ## Quick Start Ask the assistant to wire up the Aspire AppHost for this repository and connect my frontend, API, and database resources.High-intent search queries and answers about installing and using this skill.
Run this Skill after aspire init drops the skeleton. It scans your repo for projects, compose files, and connection strings, proposes a resource graph for confirmation, edits the AppHost, wires ServiceDefaults, and validates with aspire start and aspire wait.
Use typed integrations like AddPostgres("pg").AddDatabase("db") or AddRedis("cache") instead of raw containers. These auto-generate passwords and manage ports, so do not model connection strings or credentials manually.
No. The .aspire/modules directory is generated from apphost.ts and gets clobbered on every build, aspire add, or aspire start. Make all changes in apphost.ts, which is the only file you should hand-edit in a TypeScript AppHost.
Yes. Use AddNextJsApp for Next.js apps with output: 'standalone' in next.config.js, and AddViteApp for Vite SPAs paired with PublishAsStaticWebsite. Add WithBrowserLogs to surface browser console output in the dashboard.
aspire wait may expect the displayName rather than the resource name. Run aspire ps --format Json to find the correct displayName, and use --include-hidden if the resource does not appear in the list.
Do not use it for dropping the initial skeleton (use aspire-init), day-to-day start/stop/restart operations (use aspire-orchestration), publishing or deploying (use aspire-deployment), or inspecting logs and traces (use aspire-monitoring).
jonathanpottsGenerate an AppHost skeleton and aspire.config.json for repositories lacking Aspire support.
Stavanger-Brass-BandDeploy Aspire AppHost applications to Docker Compose, Kubernetes, Azure, or AWS using the Aspire CLI.
HexalithInspects Aspire application logs, traces, metrics, and resource state via the Aspire CLI.
Maj3D10Orchestrate .NET Aspire AppHost resources with service defaults and service discovery.