agentleFS
fpindejfpindej/netrock/.claude/skills/add-aspire-dep/SKILL.md

add-aspire-dep

Skill234 starsChanged 3 months agoMITView on GitHub

Add an infrastructure dependency to Aspire AppHost

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    Add hosting package version to src/backend/Directory.Packages.props, matching the version of the existing Aspire.Hosting.* packages in that …

    line 10
  2. Very specific:

    Add package reference to src/backend/MyProject.AppHost/MyProject.AppHost.csproj:

    line 14
  3. Very specific:

    Add resource in src/backend/MyProject.AppHost/Program.cs:

    line 18
  4. Distinctive:

    Add startup dependency if the API needs the resource ready:

    line 29
  5. Very specific:

    Add standalone defaults to appsettings.Development.json so the API can run without Aspire.

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Adds an infrastructure dependency to Aspire AppHost.

Steps

  1. Add hosting package version to src/backend/Directory.Packages.props, matching the version of the existing Aspire.Hosting.* packages in that file:
    <PackageVersion Include="Aspire.Hosting.{Resource}" Version="{same as other Aspire.Hosting.* entries}" />
  2. Add package reference to src/backend/MyProject.AppHost/MyProject.AppHost.csproj:
    <PackageReference Include="Aspire.Hosting.{Resource}" />
  3. Add resource in src/backend/MyProject.AppHost/Program.cs:
    var myResource = builder.AddRabbitMQ("rabbitmq");
  4. Wire to the API project:
    // Native connection string convention:
    .WithReference(myResource)
    // Custom config mapping:
    .WithEnvironment("MySection__ConnectionString", myResource.GetEndpoint("tcp"))
  5. Add startup dependency if the API needs the resource ready:
    .WaitFor(myResource)
  6. Add standalone defaults to appsettings.Development.json so the API can run without Aspire.
  7. Verify: dotnet build src/backend/MyProject.slnx

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.