Optimizes agent context setup for .NET/C# projects. Use when starting a new session, when agent output quality degrades (wrong patterns, hallucinated APIs, unaware of .NET conventions), when switching between Avalonia/Blazor/ASP.NET Core codebases, or when you need to configure CLAUDE.md, .editorconfig, and analyzer…
Guides systematic root-cause debugging for .NET/C# code. Use when dotnet test fails, dotnet build breaks, behavior doesn't match expectations, or you encounter any unexpected error (NullReferenceException, TaskCanceledException, missing DI registration, EF Core migration conflict). Use when you need a systematic…
Manages deprecation and migration for .NET/C# systems — removing NuGet packages, retiring controllers/endpoints, sunsetting features, migrating EF Core schemas. Use when removing old code, migrating users from one implementation to another, or deciding whether to maintain or sunset existing code.
Records architectural decisions and writes durable documentation for .NET/C# projects — ADRs, XML doc comments, OpenAPI/Swagger, README with dotnet CLI commands, CLAUDE.md pointers. Use when making architectural decisions, changing public APIs, shipping features, or recording context that future engineers and agents…
Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when correctness matters more than speed, when working in unfamiliar code, when stakes are high (production, security-sensitive logic, irreversible operations like EF Core migrations or deploys), or any time a confident…
Structures git workflow practices for .NET/C# projects — atomic commits, trunk-based branches, pre-commit hygiene with dotnet test + dotnet format, worktrees for parallel agent work. Use when making any code change to a .NET solution, when committing, branching, resolving conflicts, or organizing work across multiple…
Refines raw ideas into sharp, actionable .NET/C# concepts through structured divergent and convergent thinking. Use "idea-refine" or "ideate" to trigger when deciding what to build next in a .NET solution — new Avalonia app, ASP.NET Core API, EF Core data model, NuGet library, or process improvement.
Delivers .NET/C# changes incrementally — thin vertical slices with dotnet build + dotnet test verification between each. Use when implementing any feature that touches more than one project or assembly. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step.
Tests .NET/C# systems at their integration boundaries — HTTP APIs with WebApplicationFactory , EF Core against real databases via Testcontainers (PostgreSQL, SQL Server, Redis), Blazor/Razor Pages in real browsers via Microsoft.Playwright, Avalonia UI via Avalonia.Headless.XUnit. Works with xUnit v2/v3 on VSTest or…
Extracts what the user actually wants instead of what they think they should want. Achieves this through one-question-at-a-time interview until 95% confidence about the underlying intent. Use when an ask is underspecified ("build me X" without "for whom" or "why now"), when the user explicitly invokes ("interview me"…
Instruments .NET/C# code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting to an ASP.NET Core / Blazor / worker / desktop app. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you…
Breaks .NET/C# work into ordered, verifiable tasks. Use when you have a spec or clear requirements and need to decompose work into implementable units with dotnet CLI verification steps. Use when a task feels too large to start, when you need to estimate scope across a multi-project solution, or when parallel work is…
Hardens .NET/C# code against vulnerabilities — input validation (FluentValidation), EF Core parameterization, ASP.NET Core Identity / JWT bearer / policy-based authz, Data Protection, antiforgery, user-secrets + Key Vault, dotnet list package --vulnerable. Use when handling user input, authentication, data storage, or…
Prepares production launches for .NET/C# systems — pre-launch checklist with dotnet test + dotnet list package --vulnerable, feature flags via IOptions , staged rollout with Application Insights / OpenTelemetry monitoring, EF Core migration rollback, dotnet ef database update to previous migration. Use when deploying…
Grounds every .NET/C# implementation decision in official documentation (Microsoft Learn, EF Core docs, ASP.NET Core docs, Avalonia docs, NuGet README). Use when you want authoritative, source-cited code free from outdated patterns. Use when building with any .NET framework or library where correctness depends on…
Creates specs before coding a .NET/C# project. Use when starting a new .NET 8+ solution, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea. Frames examples for Avalonia, ASP.NET Core, Blazor, .NET MAUI, EF Core, xUnit, and MSTest.
Drives .NET/C# development with tests — RED/GREEN/REFACTOR with xUnit (v2 or v3) or MSTest, the Prove-It Pattern for bug fixes, the test pyramid with WebApplicationFactory for integration and Playwright/Avalonia.Headless for E2E. Supports both VSTest and Microsoft.Testing.Platform (MTP) runners. Use when implementing…
Meta-skill — discovers and invokes the right .NET/C# agent skill from this marketplace for the task at hand. Use when starting a session, when a task doesn't obviously map to a single skill, or when you need a phase-by-phase map of what's available across Define / Plan / Build / Verify / Review / Ship. Governs how…