Expecho/Agent42 / .claude/skills/aspire
aspire
VerifiedUse this skill when the user is working with an Aspire distributed application and needs to operate the AppHost or its resources through the Aspire CLI: start, restart, stop, or wait on the app; inspect resources, logs, traces, docs, or health; add integrations; manage secrets or config; publish, deploy, or rerun a named pipeline step; initialize Aspire in an existing app; recover missing `.modules` files in a TypeScript AppHost; discover the right frontend URL for Playwright from Aspire state; expose custom dashboard/resource commands; or understand unfamiliar Aspire AppHost APIs in C# or TypeScript. Use it even if they describe the task in terms of an AppHost, resources, dashboard, existing app bootstrap, missing generated modules, Playwright URL discovery, C# API understanding, or local distributed app workflow without explicitly naming Aspire. Do not use it for non-Aspire .NET apps, container-only repos with no AppHost, or ordinary build and test tasks.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.9 KB |
| references/agent-workflows.md | markdown | 3.5 KB |
| references/app-commands.md | markdown | 2.5 KB |
| references/csharp-apphosts.md | markdown | 1.4 KB |
| references/deployment.md | markdown | 1.4 KB |
| references/monitoring.md | markdown | 3.3 KB |
| references/playwright-handoff.md | markdown | 963 B |
| references/resource-management.md | markdown | 1.5 KB |
| references/tools-and-configuration.md | markdown | 2.6 KB |
| references/typescript-apphosts.md | markdown | 1.4 KB |
references/app-commands.md
View on GitHub# App Commands
Use this when the task is about app-level lifecycle, bootstrap, or AppHost-wide maintenance.
## Scenario: Start The App Safely In The Background
Use these commands when the user wants the AppHost running, needs a safe worktree session, or wants to pick up AppHost changes.
```bash
aspire start
aspire start --isolated
aspire stop
```
Keep these points in mind:
- Use `aspire start` for normal background AppHost execution.
- In git worktrees or when another local instance may already be running, use `aspire start --isolated`.
- If the CLI shape may have changed or the skill instructions look older than the local CLI, confirm the exact command form with `aspire --help` or the relevant subcommand help before executing.
- To restart after AppHost changes, rerun the same start command. In a worktree, rerun `aspire start --isolated`.
- Use `aspire stop` only when the ask is explicitly to stop the app or clean up a running AppHost.
- Avoid `aspire run` in normal agent workflows because it blocks the terminal.
## Scenario: Create A New Aspire App Or Add Aspire To An Existing App
Use these commands when the task is to bootstrap Aspire support.
```bash
aspire new
aspire init
aspire init --language typescript
```
Keep these points in mind:
- Use `aspire new` when creating a brand-new Aspire app from scratch.
- Use `aspire init` when adding Aspire to an existing application.
- If you are unsure which arguments are supported by the installed CLI, check `aspire init --help` (or the parent help) before running it.
- If the existing app flow needs a specific AppHost language, choose it explicitly rather than inventing unrelated scaffolding.
## Scenario: Find The Right AppHost Or Refresh AppHost-Wide Support
Use these commands when multiple AppHosts may be running locally, when the AppHost needs an integration, or when local AppHost support files need refresh or restore.
```bash
aspire ps
aspire add <package>
aspire update
aspire restore
```
Keep these points in mind:
- Use `aspire ps` first when you need to discover which AppHost is already running.
- If command arguments may differ across CLI versions, verify the current shape with `aspire <command> --help` before execution.
- Use `aspire add <package>` when the task is to add a supported integration or regenerate AppHost APIs.
- Use `aspire update` when the ask is specifically to refresh AppHost package references through the supported CLI workflow.
- Use `aspire restore` after pulls, cleans, or missing generated files when the AppHost needs its local support restored before running again.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |