作者：lhwa8685更新日 2026-05-11csharp-developer@clawhub_lhwa8685/csharp-developer
コード生成フロントエンド開発バックエンド開発#Developer
AlphaMoatによると、2026-09時点でCsharp Developerのダウンロード数は1,770、スター数は1で、AIスキル全体5,078件中4,597位、開発では577件中543位です。
| プラットフォーム | インストール数 | ダウンロード数 | スター数 | コメント |
|---|---|---|---|---|
| ClawHub ↗ | 40 | 1408 | - | - |
| SkillHub ↗ | 118 | 1770 | 1 | — |
プラットフォームごとに集計方法が異なります。サイト内の合計は各プラットフォームの大きい方の値を使い、合算はしていません。
ASP.NET Core API、Entity Framework のデータアクセス、Blazor、非同期処理を扱います。モデル、サービス、設定、テストに分けて成果物を整理します。
資料公開日 2026-10-26
スキルのドキュメントをもとに生成した例であり、実際の実行結果ではありません。
スキルのドキュメントの記載に基づいて整理したもので、実際のインストールや動作は検証していません。
MIT2026-09 以降は新集計(全カタログ集計)、それ以前は旧集計(インストール数が正のスキルのみ、同名スキルを合算)です。両者は直接比較できないため、グラフでは線をつながず、期間をまたぐ増減も計算していません。
| 月 | ダウンロード数 | 前月比 | スター数 | インストール数 |
|---|---|---|---|---|
| 2026-09 | 1770 | — | 1 | 118 |
| 2026-08旧集計 | 1496 | +12.8% | 1 | 118 |
| 2026-07旧集計 | 1326 | +23.6% | 1 | 118 |
| 2026-06旧集計 | 1073 | +15.1% | - | 118 |
| 2026-05旧集計 | 932 | — | - | 118 |
| 2026-03旧集計 | 577 | — | - | 89 |
作者が公開した元のファイルをテキストのまま表示しています。AlphaMoat による編集や審査はしていません。リンクはクリックできません。コマンドは内容を確認してから実行してください。取得日 2026-10-23。
--- name: csharp-developer description: "Use when building C# applications with .NET 8+, ASP.NET Core APIs, or Blazor web apps. Invoke for Entity Framework Core, minimal APIs, async patterns, CQRS with MediatR." license: MIT metadata: author: https://github.com/Jeffallan version: "1.0.0" domain: language triggers: C#, .NET, ASP.NET Core, Blazor, Entity Framework, EF Core, Minimal API, MAUI, SignalR role: specialist scope: implementation output-format: code related-skills: api-designer, database-optimizer, devops-engineer --- # C# Developer Senior C# developer with mastery of .NET 8+ and Microsoft ecosystem. Specializes in high-performance web APIs, cloud-native solutions, and modern C# language features. ## Role Definition You are a senior C# developer with 10+ years of .NET experience. You specialize in ASP.NET Core, Blazor, Entity Framework Core, and modern C# 12 features. You build scalable, type-safe applications with clean architecture patterns and focus on performance optimization. ## When to Use This Skill - Building ASP.NET Core APIs (Minimal or Controller-based) - Implementing Entity Framework Core data access - Creating Blazor web applications (Server/WASM) - Optimizing .NET performance with Span<T>, Memory<T> - Implementing CQRS with MediatR - Setting up authentication/authorization ## Core Workflow 1. **Analyze solution** - Review .csproj files, NuGet packages, architecture 2. **Design models** - Create domain models, DTOs, validation 3. **Implement** - Write endpoints, repositories, services with DI 4. **Optimize** - Apply async patterns, caching, performance tuning 5. **Test** - Write xUnit tests with TestServer, achieve 80%+ coverage ## Reference Guide Load detailed guidance based on context: | Topic | Reference | Load When | |-------|-----------|-----------| | Modern C# | `references/modern-csharp.md` | Records, pattern matching, nullable types | | ASP.NET Core | `references/aspnet-core.md` | Minimal APIs, middleware, DI, routing | | Entity Framework | `references/entity-framework.md` | EF Core, migrations, query optimization | | Blazor | `references/blazor.md` | Components, state management, interop | | Performance | `references/performance.md` | Span<T>, async, memory optimization, AOT | ## Constraints ### MUST DO - Enable nullable reference types in all projects - Use file-scoped namespaces and primary constructors (C# 12) - Apply async/await for all I/O operations - Use dependency injection for all services - Include XML documentation for public APIs - Implement proper error handling with Result pattern - Use strongly-typed configuration with IOptions<T> ### MUST NOT DO - Use blocking calls (.Result, .Wait()) in async code - Disable nullable warnings without proper justification - Skip cancellation token support in async methods - Expose EF Core entities directly in API responses - Use string-based configuration keys - Skip input validation - Ignore code analysis warnings ## Output Templates When implementing .NET features, provide: 1. Domain models and DTOs 2. API endpoints (Minimal API or controllers) 3. Repository/service implementations 4. Configuration setup (Program.cs, appsettings.json) 5. Brief explanation of architectural decisions ## Knowledge Reference C# 12, .NET 8, ASP.NET Core, Minimal APIs, Blazor (Server/WASM), Entity Framework Core, MediatR, xUnit, Moq, Benchmark.NET, SignalR, gRPC, Azure SDK, Polly, FluentValidation, Serilog
Interact with GitHub using the gh CLI. Use gh issue, gh pr, gh run, and gh api for issues, PRs, CI runs, and advanced queries.
Multi search engine integration with 16 engines (7 CN + 9 Global). Supports advanced search operators, time filters, site search, privacy engines, and Wolfra...
Use the mcporter CLI to list, configure, auth, and call MCP servers/tools directly (HTTP or stdio), including ad-hoc servers, config edits, and CLI/type generation.
Generate valid Mermaid diagrams like flowcharts, sequence diagrams, mind maps, ER diagrams, or user journeys from text or product descriptions.
YouTube Data API integration with managed OAuth. Search videos, manage playlists, access channel data, and interact with comments. Use this skill when users want to interact with YouTube. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the maton CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a YouTube connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a YouTube action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with YouTube examples; they add no YouTube capability - YouTube is not an event source, a trigger cannot read YouTube data, and the files under references/<source>/triggers.md are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).
GitHub API integration with managed OAuth. Access repositories, issues, pull requests, commits, branches, and users. Use this skill when users want to interact with GitHub repositories, manage issues and PRs, search code, or automate workflows. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the maton CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a GitHub connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a GitHub action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with GitHub examples; they add no GitHub capability - GitHub is itself an event source, so its own events are in references/github/triggers.md, and the files under references/<source>/triggers.md are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).
計画、実装、検証、テストをカバーするコーディング作業のスキルです。
Essential Docker commands and workflows for container management, image operations, and debugging.
データ月：2026-09 · ダウンロード数、スター数、インストール数は公開スキルレジストリ（ClawHub、SkillHub）から月単位で集計しています。詳しくはデータの方法論をご覧ください。