GuerthCastro
User.NET coding and testing conventions packaged as Agent Skills: C# style, test patterns, SOLID and Clean Architecture review, and a C# 14 / .NET 10 feature reference. Works with Claude Code, Claude apps, and any tool that reads SKILL.md. MIT.
Categories
Indexed Skills (5)
csharp14-dotnet10-features
Reference for what is new in C# 14 and .NET 10, covering both language features and platform or library changes. Use this skill whenever writing, reviewing, or migrating C# code that targets net10.0, whenever the user asks what is new in C# 14 or .NET 10, and when deciding whether a piece of code can use a C# 14 only construct such as the field keyword, extension blocks, null conditional assignment, or file based apps. This is a feature reference, not a migration runbook.
dotnet10-conventions
Opinionated C# and .NET 10 coding conventions built around Clean Architecture and plain Dapper: one type per file, file-scoped namespaces, primary constructors, camelCase locals and fields with no underscore prefix, POCO entities with hand written SQL, versioned migration scripts, soft deletes, and a single LookUp catalog table. Use this skill whenever writing, reviewing, refactoring, or scaffolding C# code, solution structures, entities, repositories, services, handlers, DTOs, mappers, or validators for a .NET 10 project that follows these conventions. Also use when creating a new project from scratch, migrating an existing one, or adding a new layer to an existing solution. Apply these conventions without exception unless the user explicitly overrides a rule for a specific case.
dotnet10-testing
Opinionated unit testing conventions for .NET 10 solutions built on Clean Architecture and Dapper: xUnit as the runner with `[Theory]` reserved for variants that differ only in input values, Moq for collaborators, Bogus fakers as dedicated builder classes in a shared test library, AwesomeAssertions for assertions, result objects instead of thrown exceptions, and repository tests that run against the real engine in a disposable container rather than a mocked connection. Use this skill whenever writing, reviewing, or restructuring tests for a .NET project: service tests, controller tests, repository tests, test data builders, mocking strategy, test naming, or test project layout. Also use when setting up a test project from scratch or deciding what deserves a test at all.
solid-review
Audit any C#, TypeScript, or Angular code against the five SOLID principles and Clean Architecture layering rules, then produce a severity ranked report with concrete refactorings. Use this skill whenever the user asks to review code for SOLID compliance, identify design violations, refactor toward Clean Architecture, or get a design quality report on a class, service, handler, component, or module. Also use when the user asks "does this follow SOLID?", "is this clean?", "what is wrong with this design?", or pastes code and asks for architectural feedback.
classic-asp-to-aspnet-mvc
Conventions and a working playbook for porting Classic ASP or Web Forms sites to ASP.NET Core MVC on net10.0: Program.cs composition, controllers and routing, view models, Razor layouts, sections and partial views, wwwroot assets, configuration through validated options instead of raw configuration keys, secrets in user secrets locally and Azure Key Vault in production, Dapper repositories behind Abstractions interfaces, and typed HttpClient services that return models rather than transport objects. Use this skill whenever migrating a Classic ASP, ASP, or Web Forms application to ASP.NET Core MVC, reviewing such a migration, scaffolding the MVC layout for a ported site, or deciding where ported inline logic belongs in the new structure.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.