Name: csharp-api-design
Author: yappologistic

Imported from yappologistic/CSharp-Tutor (csharp-api-design/SKILL.md). Install upstream with npx skills add yappologistic/CSharp-Tutor --skill csharp-api-design. Copyright stays with the author.

C# API Design

Use $csharp-tutor mode=api-design.

Treat all user text after $csharp-api-design as a C# API design, public surface, library design, DTO contract, compatibility, or package design question. Use the main csharp-tutor skill as the source of truth.

Load these csharp-tutor references when useful:

references/api-design-guidance.md
references/nuget-guidance.md
references/versioning-guidance.md
references/docs-grounding.md
references/testing-guidance.md
references/architecture-guidance.md
references/source-citation-rules.md

Standalone Guidance

Core rule: Keep the answer centered on the concrete api-design decision, failure mode, or contract.
Avoid: Giving generic C# advice without tying it to the api-design concern.
Minimal example: Task<Order?> GetOrderAsync(int id, CancellationToken cancellationToken);

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Install csharp-api-design and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "yappologistic-csharp-tutor-csharp-api-design", "kind": "skill", "name": "csharp-api-design", "description": "Teach and review C# public API design. Use for method signatures, naming, nullability, exceptions, result types, cancellation, async APIs, records, DTOs, versioning, binary compatibility, XML docs, NuGet packaging, library boundaries, and maintainable API surfaces.", "publisher": "yappologistic", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Teach and review C# public API design. Use for method signatures, naming, nullability, exceptions, result types, cancellation, async APIs, records, DTOs, versioning, binary compatibility, XML docs, NuGet packaging, library boundaries, and maintainable API surfaces." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/yappologistic/CSharp-Tutor", "path": "csharp-api-design/SKILL.md", "ref": "b0e6d5c7e4c690ce376c99ed782027008adf40bd", "url": "https://github.com/yappologistic/CSharp-Tutor/blob/b0e6d5c7e4c690ce376c99ed782027008adf40bd/csharp-api-design/SKILL.md", "key": "yappologistic/CSharp-Tutor/csharp-api-design/SKILL.md" } }, "instructions": "# C# API Design\n\nUse `$csharp-tutor mode=api-design`.\n\nTreat all user text after `$csharp-api-design` as a C# API design, public surface, library design, DTO contract, compatibility, or package design question. Use the main [csharp-tutor](../csharp-tutor/SKILL.md) skill as the source of truth.\n\nLoad these csharp-tutor references when useful:\n\n- `references/api-design-guidance.md`\n- `references/nuget-guidance.md`\n- `references/versioning-guidance.md`\n- `references/docs-grounding.md`\n- `references/testing-guidance.md`\n- `references/architecture-guidance.md`\n- `references/source-citation-rules.md", "cost": { "context_tokens": 283 } }

csharp-api-design

About

C# API Design

Standalone Guidance

Use it

Install csharp-api-design and it becomes one more candidate the router can pick - when it fits.

Manifest

Reviews