agentleFS
Sign inStart free
EmeaAppGbbEmeaAppGbb/spec2cloud/.github/skills/aspire/SKILL.md

aspire

Skill100 starsChanged 7 months agoMITView on GitHub

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.

We split this skill into the rules it gives an agent

8 rules. 0 are common, 1 is distinctive, and 7 are very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use aspire start to run the AppHost in the background.

    line 42
  2. Very specific:

    Use aspire wait <resource> to block until a resource is healthy before interacting with it:

    line 48
  3. Distinctive:

    Before making code changes, inspect the app state:

    line 59
  4. Very specific:

    Use aspire docs search to find integration documentation, then aspire docs get to read the full guide.

    line 68
  5. Very specific:

    After adding an integration, restart the app with aspire start for the new resource to take effect.

    line 70
  6. Very specific:

    Use --isolated when working in a worktree.

    line 86
  7. Very specific:

    Prefer aspire.dev and learn.microsoft.com/dotnet/aspire for official documentation.

    line 89
  8. Very specific:

    If configured, use Playwright CLI for functional testing of resources.

    line 93

“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

TaskCommand
Start the appaspire start
Start isolated (worktrees)aspire start --isolated
Restart the appaspire start (stops previous automatically)
Wait for resource healthyaspire wait <resource>
Stop the appaspire stop
List resourcesaspire describe or aspire resources
Run resource commandaspire resource <resource> <command>
Start/stop/restart resource`aspire resource <resource> startstoprestart`
View console logsaspire logs [resource]
View structured logsaspire otel logs [resource]
View tracesaspire otel traces [resource]
Logs for a traceaspire otel logs --trace-id <id>
Add an integrationaspire add
List running AppHostsaspire ps
Update AppHost packagesaspire update
Search docsaspire docs search <query>
Get doc pageaspire docs get <slug>
List doc pagesaspire docs list
Environment diagnosticsaspire doctor
List resource MCP toolsaspire mcp tools
Call resource MCP toolaspire 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:

aspire start --isolated

Use aspire wait <resource> to block until a resource is healthy before interacting with it:

aspire start --isolated
aspire wait myapi

Relaunching is safe — aspire start automatically stops any previous instance. Re-run aspire start whenever changes are made to the AppHost project.

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:

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.
  • 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.
  • Prefer aspire.dev and learn.microsoft.com/dotnet/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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free