aspire
/aspire
Obsługuje aplikacje rozproszone Aspire z poziomu CLI: uruchamianie, zatrzymywanie, logi, integracje i dashboard.
- Autor
- nikiforovall ↗
- Repozytorium
- keycloak-authorization-services-dotnet ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 02.06.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 02.06.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Obsługuje aplikacje rozproszone Aspire z poziomu CLI: uruchamianie, zatrzymywanie, logi, integracje i dashboard.
Oryginalny opis (EN)
Orchestrates Aspire distributed applications using the Aspire CLI for running, debugging, and managing distributed apps. USE FOR: aspire start, aspire stop, start aspire app, aspire describe, list aspire integrations, debug aspire issues, view aspire logs, add aspire resource, aspire dashboard, update aspire apphost. DO NOT USE FOR: non-Aspire .NET apps (use dotnet CLI), container-only deployments (use docker/podman), Azure deployment after local testing (use azure-deploy skill). INVOKES: Aspire CLI commands (aspire start, aspire describe, aspire otel logs, aspire docs search, aspire add), bas
Jak działa
- CLI command reference
- Key workflows
- Important rules
- Playwright CLI
Podgląd SKILL.md
---
name: aspire
description: "Orchestrates Aspire distributed applications using the Aspire CLI for running, debugging, and managing distributed apps. USE FOR: aspire start, aspire stop, start aspire app, aspire describe, list aspire integrations, debug aspire issues, view aspire logs, add aspire resource, aspire dashboard, update aspire apphost. DO NOT USE FOR: non-Aspire .NET apps (use dotnet CLI), container-only deployments (use docker/podman), Azure deployment after local testing (use azure-deploy skill). INVOKES: Aspire CLI commands (aspire start, aspire describe, aspire otel logs, aspire docs search, aspire add), bash. FOR SINGLE OPERATIONS: Use Aspire CLI commands directly for quick resource status or doc lookups."
---
# Aspire Skill
This repository uses Aspire to orchestrate its distributed application. Resources are defined in the AppHost project (`apphost.cs` or `apphost.ts`).
## CLI command reference
| Task | Command |
|---|---|
| Start the app | `aspire start` |
| Start isolated (worktrees) | `aspire start --isolated` |
| Restart the app | `aspire start` (stops previous automatically) |
| Wait for resource healthy | `aspire wait <resource>` |
| Stop the app | `aspire stop` |
| List resources | `aspire describe` or `aspire resources` |
| Run resource command | `aspire resource <resource> <command>` |
| Start/stop/restart resource | `aspire resource <resource> start|stop|restart` |
| Rebuild a .NET project resource | `aspire resource <resource> rebuild` |
| View console logs | `aspire logs [resource]` |
| View structured logs | `aspire otel logs [resource]` |
| View traces | `aspire otel traces [resource]` |
| Logs for a trace | `aspire otel logs --trace-id <id>` |
| Add an integration | `aspire add` |
| List running AppHosts | `aspire ps` |
| Update AppHost packages | `aspire update` |
| Search docs | `aspire docs search <query>` |
| Get doc page | `aspire docs get <slug>` |
| List doc pages | `aspire docs list` |
| Environment diagnostics | `aspire doctor` |
| List resource MCP tools | `aspire mcp tools` |
| Call resource MCP tool | `aspire mcp call <resource> <tool> --input <json>` |
Most commands support `--format Json` for machine-readable output. Use `--apphost <path>` to target a specific AppHost.
## Key workflows
### Running in agent environments
Use `aspire start` to run the AppHost in the background. When working in a git worktree, use `--isolated` to avoid port conflicts and to prevent sharing user secrets or other local state with other running instances:
```bash
aspire start --isolated
```
Use `aspire wait <resource>` to block until a resource is healthy before interacting with it:
```bash
aspire start --isolated
aspire wait myapi
```
### Applying code changes
Choose the right action based on what changed:
| What changed | Action | Why |
|---|---|---|
| AppHost project (`apphost.cs`/`apphost.ts`) | `aspire start` | Resource graph changed; full restart required |
| Compiled .NET project resource | `aspire resource <name> rebuild` | Rebuilds and restarts only that resource |
| Interpreted resource (JavaScript, Python) | Typically nothing — most run with file watchers | Restart the resource if no watch mode is configured |
**Never restart the entire AppHost just because a single resource changed.** Use `aspire resource <name> rebuild` for .NET project resources — it coordinates stop, build, and restart for just that resource. Use `aspire describe --format Json` to check which commands a resource supports.
### Debugging issues
Before making code changes, inspect the app state:
1. `aspire describe` — check resource status
2. `aspire otel logs <resource>` — view structured logs
3. `aspire logs <resource>` — view console output
4. `aspire otel traces <resource>` — view distributed traces
### Adding integrations
Use `aspire docs search` to find integration documentation, then `aspire docs get` to read the full guide. Use `aspire add` to add the integration package to the AppHost.
After adding an integration, restart the app with `aspire start` for the new resource to take effect.
### Using resource MCP tools
Some resources expose MCP tools (e.g. `WithPostgresMcp()` adds SQL query tools). Discover and call them via CLI:
```bash
aspire mcp tools # list available tools
aspire mcp tools --format Json # includes input schemas
aspire mcp call <resource> <tool> --input '{"key":"value"}' # invoke a tool
```
## Important rules
- **Always start the app first** (`aspire start`) before making changes to verify the starting state.
- **To restart, just run `aspire start` again** — it automatically stops the previous instance. NEVER use `aspire stop` then `aspire run`. NEVER use `aspire run` at all.
- **Only restart the AppHost when AppHost code changes.** For .NET project resources, use `aspire resource <name> rebuild` instead.
- Use `--isolated` when working in a worktree.
- **Avoid persistent containers** early in development to prevent state management issues.
- **Never install the Aspire workload** — it is obsolete.
- **For Aspire API reference and documentation, prefer `aspire docs search <query>` and `aspire docs get <slug>`** over searching NuGet package caches or XML doc files. The CLI provides up-to-date content from aspire.dev.
- Prefer `aspire.dev` and `learn.microsoft.com/microsoft/aspire` for official documentation.
## Playwright CLI
If configured, use Playwright CLI for functional testing of resources. Get endpoints via `aspire describe`. Run `playwright-cli --help` for available commands.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · nikiforovall/keycloak-authorization-services-dotnet | 100 | MIT |
| managedcode/dotnet-skills | 100 | MIT |
| thangchung/agent-engineering-experiment | 100 | MIT |
| codewithmukesh/dotnet-claude-kit | 100 | MIT |
| FritzAndFriends/BlazorWebFormsComponents | 100 | MIT |
| Tyler-R-Kendrick/agent-skills | 100 | MIT |
| Tyler-R-Kendrick/agent-skills | 100 | MIT |
| thangchung/agent-engineering-experiment | 90 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki f4ba6beec97f (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100aspire-monitoring
Obserwuje aplikacje Aspire: logi, ślady, metryki i stan zasobów, także przez CLI, dashboard i zdalne zasoby Azure. - 100aspire-monitoring
Obserwuje aplikacje Aspire: logi, ślady, metryki, stan zasobów, eksport telemetrii i samodzielny dashboard, z przełączaniem między lokalnym CLI, diagnostyką AKS i stanem zasobów Azure. - 100aspire-restart
Uruchamia lub restartuje AppHost .NET Aspire przez CLI deweloperskie, zamiast poleceń run, aspire run czy aspire restart. - 100deployment-e2e-testing
Prowadzi przez pisanie, zmienianie i debugowanie testów end-to-end wdrożeń Aspire na Azure. - 90dotnet-aspire-cloud-native-review
Przegląda AppHost lub service-defaults w .NET Aspire pod kątem gotowości cloud-native: health checks, powiązania usług, polityki odporności, higiena konfiguracji i sekretów, dryf konfiguracji oraz gotowość kontenerów. - 93cli-e2e-testing
Pomaga tworzyć, zmieniać, debugować i recenzować testy end-to-end Aspire CLI oparte na automatyzacji terminala Hex1b w katalogu tests/Aspire.Cli.EndToEnd.Tests.