aspireify

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

2|Updated Jul 24, 2026
One-click install
npx skills add https://github.com/elbruno/ElBruno.MagenticUI --skill aspireify-elbruno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aspireify
Source: https://github.com/elbruno/ElBruno.MagenticUI/tree/main/.agents/skills/aspireify
Command: npx skills add https://github.com/elbruno/ElBruno.MagenticUI --skill aspireify-elbruno

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 repository, proposes a resource graph, edits the AppHost (C#, file-based C#, or TypeScript), wires ServiceDefaults with OpenTelemetry, and validates everything with aspire start. ## 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 integration 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 with correct API shapes verified via aspire docs api search, while refusing to edit generated .aspire/modules/ files. - End-to-End Validation and Self-Deactivation: Runs aspire start --non-interactive, waits on each resource, checks the graph with aspire describe, then hands off to orchestration skills once healthy. - Use Case: You just ran aspire init in a repo with a .NET API, a Next.js frontend, and a docker-compose file defining Postgres and Redis. This Skill scans the repo, proposes AddPostgres/AddRedis/AddNextJsApp wiring with service discovery, edits the AppHost, and validates the full stack starts cleanly. ## Quick Start Ask the assistant to wire up the Aspire AppHost for this repository and validate it with aspire start.

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?▼

Scan the repo for .csproj files, package.json services, and docker-compose dependencies, then propose a resource graph mapping each to typed integrations like AddPostgres or AddNextJsApp. After user confirmation, edit the AppHost and validate with aspire start and aspire wait.

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

Use typed integrations such as AddPostgres("pg").AddDatabase("db") or AddRedis("cache") instead of 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. The .aspire/modules directory is generated by Aspire 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.

Does Aspire support Next.js and Vite frontends?▼

Yes. Use AddNextJsApp for Next.js with output set to standalone in next.config.js, and AddViteApp for Vite SPAs paired with PublishAsStaticWebsite. Add WithBrowserLogs to surface browser console output and screenshots in the dashboard.

Why does aspire wait reject my resource name?▼

The aspire wait command may expect the displayName rather than the resource name. Run aspire ps --format Json to find the correct displayName value, and retry the wait command with that identifier.

When should I not use this AppHost wiring workflow?▼

Do not use it for dropping the initial skeleton (that is aspire init's job), day-to-day start/stop/restart operations, publishing or deployment, or log and trace inspection. Those belong to separate orchestration, deployment, and monitoring workflows.