agentleFS
Sign inStart free
platformplatformplatformplatform/PlatformPlatform/.claude/skills/aspire-restart/SKILL.md

aspire-restart

Skill439 starsChanged 6 months agoMITView on GitHub

Start or restart the .NET Aspire AppHost via the developer CLI. Always use this, never the developer CLI's `run` command, `aspire run`, or `aspire restart`.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Use developer-cli exactly as written - do not expand to an absolute worktree path.

    line 12
  2. Very specific:

    Always use restart, even when nothing is running yet.

    line 16
  3. Very specific:

    After backend or frontend changes - restart is the safe default.

    line 22
  4. Distinctive:

    When hot reload breaks or stops picking up changes.

    line 24
  5. Distinctive:

    Before running e2e tests on a fresh stack.

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Restart Aspire

dotnet run --project developer-cli -- restart

Use developer-cli exactly as written - do not expand to an absolute worktree path.

Stops any running Aspire AppHost and starts a fresh instance. Detached by default - the CLI returns immediately while Aspire keeps running.

Always use restart, even when nothing is running yet. It is a no-op when Aspire is not up, and the safe default in every other case. Never use the developer CLI's run command, aspire run, or aspire restart.

  • --public-url <url> - set PUBLIC_URL (e.g. an ngrok URL)

When to use

  • After backend or frontend changes - restart is the safe default; it works whether Aspire is up or not.
  • To run database migrations.
  • When hot reload breaks or stops picking up changes.
  • Before running e2e tests on a fresh stack.

Port allocation

Fully automatic. On a fresh checkout the developer CLI bootstraps .workspace/port.txt: the root gets the default base port; worktrees scan a fixed list of candidates and pick the first one whose ports are all free. Once written, the file is the authoritative allocation for the lifetime of the checkout.

Output is fire-and-forget

The CLI prints Aspire is restarting on https://app.dev.localhost:<port> and exits before Aspire is fully ready.

Stopping Aspire

To stop without restarting, run dotnet run --project developer-cli -- stop. Rarely needed - prefer restart for everyday use.

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