Skip to content

Expecho/Agent42 / .claude/skills/aspire

aspire

Verified

Use 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.

references/tools-and-configuration.md

View on GitHub
# Tools And Configuration

Use this when the task is about docs lookup, API reference lookup, secrets, CLI configuration, diagnostics, cache cleanup, or local certificates.

## Scenario: I Need Docs Or API Reference Before I Change The AppHost

Use these commands when the task is to confirm the right Aspire workflow before editing code or retrieve a specific API reference entry.

```bash
aspire docs search <query>
aspire docs get <slug>
aspire docs api search <query> --language csharp|typescript
aspire docs api list <scope>
aspire docs api get <id>
```

Keep these points in mind:

- Use docs commands before changing integrations when you need to confirm the supported path or recommended workflow.
- Use docs commands before implementing custom resource commands or unfamiliar AppHost patterns such as `WithCommand`.
- Use `aspire docs api` when the user needs the C# or TypeScript reference entry for a specific Aspire API.
- Use `aspire docs api list <scope>` to browse children under a language, package, module, type, or symbol.

## Scenario: I Need To Inspect Or Change AppHost Secrets

Use these commands when the task is about AppHost user secrets such as connection strings, passwords, or API keys.

```bash
aspire secret set <key> <value>
aspire secret get <key>
aspire secret list
aspire secret path
aspire secret delete <key>
```

Keep these points in mind:

- Use `aspire secret` for AppHost user secrets instead of inventing another storage path.
- Use `aspire secret path` when the task is to locate the backing store without opening it manually.

## Scenario: I Need To Explain Where Aspire CLI Settings Came From

Use these commands when the question is about effective Aspire CLI configuration or conflicting local versus global settings.

```bash
aspire config set <key> <value>
aspire config get <key>
aspire config list
aspire config delete <key>
aspire config info
```

Keep these points in mind:

- Use `aspire config info` when the user wants to know where settings come from, which settings files are in play, or why the CLI is behaving a certain way locally.

## Scenario: My Local Aspire Setup Feels Broken

Use these commands when the local Aspire environment looks unhealthy and needs recovery steps rather than AppHost code changes.

```bash
aspire doctor
aspire cache clear
aspire certs trust
aspire certs clean
```

Keep these points in mind:

- Use `aspire doctor` early when the symptoms suggest local environment drift rather than an app bug.
- Use `aspire cache clear` when cached state is stale or interfering with normal operation.
- Use `aspire certs trust` and `aspire certs clean` when local certificate state is part of the problem.
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall