aspireify

Wire an Aspire AppHost by scanning repos, proposing resource graphs, and validating with aspire start.

25|4|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/thangchung/agent-engineering-experiment --skill aspireify-thangchung
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aspireify
Source: https://github.com/thangchung/agent-engineering-experiment/tree/main/agentgateway-entraid-obo/.claude/skills/aspireify
Command: npx skills add https://github.com/thangchung/agent-engineering-experiment --skill aspireify-thangchung

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? After 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 repo, proposes a resource graph, edits the AppHost (C#, file-based C#, or TypeScript), wires ServiceDefaults and OpenTelemetry, and validates everything with aspire start. ## Core Features & Use Cases - Repo Scanning & Resource Graph Proposal: Detects .NET projects, Node/Python services, docker-compose dependencies, and hardcoded connection strings, then proposes a resource graph for user confirmation before editing. - Multi-Language AppHost Authoring: Edits SDK-style C# (Program.cs), file-based C# (apphost.cs), or TypeScript (apphost.ts) AppHosts using verified APIs from aspire docs lookups, with a hard refusal to edit generated .aspire/modules/ files. - End-to-End Validation & Self-Deactivation: Runs aspire start --non-interactive, waits on each resource, and hands off to orchestration skills once the app starts cleanly. - Use Case: You just ran aspire init in a repo with a .NET API, a Next.js frontend, and Postgres in docker-compose. This Skill detects all three, proposes AddPostgres + AddProject + AddNextJsApp wiring with WithReference and WaitFor, migrates your .env connection strings into Aspire parameters, and validates the full stack starts healthy. ## Quick Start Ask the assistant to wire up the Aspire AppHost for this repository and scaffold the resource graph after aspire init.

Frequently Asked Questions about aspireify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I wire an Aspire AppHost after running aspire init?▼

Run a scan of the repo to inventory .NET projects, Node services, and docker-compose dependencies, then propose a resource graph before editing. The AppHost is edited using verified APIs from aspire docs, wired with ServiceDefaults, and validated with aspire start and aspire wait.

How do I add Postgres or Redis to an Aspire AppHost?▼

Use typed integrations like AddPostgres("pg").AddDatabase("db") in C# or addPostgres('pg') in TypeScript rather than raw AddContainer calls. These integrations auto-generate passwords and manage ports, so do not model connection strings or credentials manually.

Can I edit files in the .aspire/modules directory of a TypeScript AppHost?▼

No, .aspire/modules/ is generated by the TypeScript AppHost and any edits are clobbered on the next build, aspire add, or aspire start. Make all changes in apphost.ts instead, or run aspire add <package> to regenerate the modules.

Does Aspire support TypeScript AppHosts and JavaScript frontends?▼

Yes, Aspire supports apphost.ts AppHosts with a unified withEnvironment(name, value) API, plus AddNextJsApp, AddViteApp, and AddNodeApp for JavaScript services. Publish helpers like PublishAsStaticWebsite and PublishAsNodeServer replace hand-rolled Dockerfiles.

Why does aspire wait reject my resource name?▼

aspire wait may reject the declared resource name because it expects the displayName instead. Run aspire ps --format Json to find the correct displayName, and re-run aspire wait with that value.

When should I not use this AppHost wiring workflow?▼

Do not use it for dropping the initial skeleton (use aspire init), day-to-day start/stop/restart operations, publish/deploy tasks, or log and trace inspection. It is a one-time wiring workflow that self-deactivates after a clean aspire start.