agentleFS
LeanMeanCleanAppsLeanMeanCleanApps/CleanWebApi/.agents/skills/openapi-and-scalar/SKILL.md

openapi-and-scalar

Skill4 starsChanged 10 days agoMITView on GitHub

How this Web API builds its OpenAPI document and serves the Scalar API reference - AddOpenApi, the document and operation transformers, the bearer scheme when authentication is on, the Scalar options, and the tests that read the generated document. Use when changing the API description, tags, security scheme, Scalar settings, or when the API reference looks wrong.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    When you add an action, update the operation count in GetOpenApiDocument_ShouldDescribe_EveryOperation.

    line 28
  2. Distinctive:

    Run the app and read the result at <http://localhost:7340/scalar>.

    line 29
  3. Distinctive:

    Add Swashbuckle or NSwag. The built-in generator and Scalar replace them.

    line 62
  4. Distinctive:

    Add the security scheme when authentication is off.

    line 66

≈ “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

OpenAPI and Scalar (Web API)

The rule

The OpenAPI document is generated at runtime by Microsoft.AspNetCore.OpenApi and served at /openapi/v1.json. Scalar (Scalar.AspNetCore) renders it at /scalar. Operation and schema text comes from XML comments on the actions and request classes (xml-docs-and-openapi), and each operation's tag comes from its controller name. Everything else is set by transformers in src/Presentation/OpenApi/.

TransformerAdds
DocumentInfoTransformerTitle (with the environment name), description, contact, licence, external docs and the tag descriptions
BearerSecurityTransformerOnly in a solution with authentication, and only when Authentication:Authority is set: the Bearer security scheme, a security requirement and a 401 response on every operation that needs a token

Scalar is set up in ProgramExtensions.ConfigureApplication with the title, C# HttpClient as the default code sample, and its developer tools, agent, MCP and telemetry features turned off.

tests/Presentation.Tests.Integration/OpenApi/OpenApiDocumentTests.cs reads the generated document and fails if an operation has no summary, description, sample request or parameter descriptions, or a schema property has no description.

Steps

  1. A new controller needs a CreateTag(...) line in DocumentInfoTransformer, named like the controller without Controller, with a one-sentence description.
  2. Something every operation needs goes in an operation transformer; something about the whole API goes in a document transformer. Register it in AddOpenApi in ProgramExtensions.ConfigureBuilder.
  3. Transformers are classes implementing IOpenApiDocumentTransformer or IOpenApiOperationTransformer, sealed, with XML docs. Unit test them in tests/Presentation.Tests.Unit/OpenApi/.
  4. When you add an action, update the operation count in GetOpenApiDocument_ShouldDescribe_EveryOperation.
  5. Run the app and read the result at http://localhost:7340/scalar.

Example

// src/Presentation/Extensions/ProgramExtensions.cs
_ = builder.Services.AddOpenApi(options =>
{
    _ = options.AddDocumentTransformer<DocumentInfoTransformer>();

    // Only with --include-auth.
    if (authentication.Enabled)
    {
        _ = options.AddDocumentTransformer<BearerSecurityTransformer>();
        _ = options.AddOperationTransformer<BearerSecurityTransformer>();
    }
});
// src/Presentation/Extensions/ProgramExtensions.cs
_ = app.MapOpenApi();
_ = app.MapScalarApiReference(options => options
    .WithTitle("CleanWebApi API")
    .WithDefaultHttpClient(ScalarTarget.CSharp, ScalarClient.HttpClient)
    .HideDeveloperTools()
    .DisableAgent()
    .DisableMcp()
    .DisableTelemetry());

Don't

  • Add Swashbuckle or NSwag. The built-in generator and Scalar replace them.
  • Describe operations with [EndpointSummary] or [EndpointDescription]. The XML comments are the one source.
  • Set [Tags] on an action. The controller name is the tag.
  • Turn Scalar telemetry back on.
  • Add the security scheme when authentication is off. The reference would ask for a token nobody needs.

Check

dotnet test --filter "FullyQualifiedName~OpenApi"
dotnet run --project ./src/Presentation   # then open http://localhost:7340/scalar

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.