AI Agent Hub
Back to skills
💻

C# Development Expert

Development Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Please install @kunlungrowth/kg-csharp-developer according to https://skillhub.cn/install/skillhub.md.

About this skill

What It Solves

This skill is aimed at .NET 8 engineers working on C# backends and Web UIs. It covers Minimal API or Controller interface design, EF Core data-access configuration, Blazor component implementation, and self-checks for async behavior, migrations, and dependency-injection lifetimes. It can also turn natural-language requirements, constraints, and optional code snippets into a reviewable CSharpAppSpec artifact, reducing back-and-forth between APIs, data layers, and UI work. For teams that need to turn verbal requirements into structured design notes for code-reviewer review, it provides a clear input/output boundary.

How It Works

Core capabilities
- Clarify API shape, data layer, and whether to use Blazor
- Separate endpoint, service, and repository boundaries
- Produce Minimal API endpoints, EF Core configuration, and Blazor components
- Emit a {app, framework, endpoints, data, notes} structured artifact

Key steps
1. Confirm requirements for REST shape, data access, and UI goals.
2. Define endpoint/service/repository responsibilities.
3. Implement type-safe application code and configuration.
4. Check async calls, EF migrations, and DI lifetimes.
5. Return CSharpAppSpec plus two or three highest-impact improvement suggestions.

It is useful for diagnosing intermittent .NET API timeouts, synchronous blocking, or EF full-table loads, and can point toward AsNoTracking, indexes, and other checks. It can also take an existing CSharpAppSpec for further refinement, or turn requirements, constraints, and code snippets into a clearer artifact. It does not target non-.NET stacks or legacy .NET Framework projects.

Use Cases

  • Turn a natural-language requirement into a structured Minimal API, EF Core, and Blazor design note.
  • Diagnose intermittent .NET API timeouts by checking synchronous blocking, EF full-table loads, and index or AsNoTracking needs.
  • Separate endpoint, service, and repository boundaries when adding REST APIs, then produce a reviewable CSharpAppSpec.
  • Refine an existing CSharpAppSpec by re-checking async calls, migrations, and dependency-injection lifetimes.

Best For

  • A .NET 8 backend engineer who wants to structure API shape, EF Core configuration, and Blazor components into a clear design.
  • A C# web project maintainer who needs to check async calls, database migrations, and dependency-injection lifetimes.
  • A backend lead who needs to turn verbal requirements into a CSharpAppSpec for code-reviewer review.
  • An engineer building internal systems with Blazor who wants to clarify data-access boundaries when adding UI.