Menu
Add or extend MoreSpeakers Domain Result types with explicit factory methods and structured errors.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Apply Result<T>-based feedback patterns in Razor Pages and HTMX flows.
Fix xUnit v3 test projects that compile but show zero discovered tests under dotnet test.
Use reflection-based tests to lock an API contract before the implementation lands.
Expert .NET 10 Full-Stack Developer skill. Use this when implementing new features, vertical slices, or modifying existing logic in the MoreSpeakers application. It covers Domain, Data (EF Core), Managers, and Web (Razor Pages + HTMX).
QA Automation Engineer skill. Use this to write or refactor unit tests. Ensures tests follow the project's xUnit, FluentAssertions, and Moq standards.
Database Architect skill. Use this when you need to modify the database schema, add tables, or seed data. This project uses RAW SQL SCRIPTS orchestrated by .NET Aspire, NOT Entity Framework Migrations.
| name | result-foundation |
| description | Add or extend MoreSpeakers Domain Result types with explicit factory methods and structured errors. |
| domain | error-handling |
| confidence | high |
| source | earned |
Use this skill when implementing or extending the approved Result-based exception handling migration in the Domain layer. It applies when expected failures need to flow through Data, Managers, and Web without losing structured context.
Error, Result, and Result<T> in src\MoreSpeakers.Domain\Models\, but expose them from the root MoreSpeakers.Domain namespace.IdentityResult: factory methods live on non-generic Result instead of exposing public constructors.readonly struct for Result and Result<T> to stay additive and allocation-conscious on the hot path.Error, and failure results throw if callers read Value.src\MoreSpeakers.Domain.Tests\ResultTests.cs, including success, failure, implicit conversion, and equality.Result signatures instead of inheriting generic IDataStore contracts that force sentinel returns.DbUpdateException; return typed Error codes for not-found/no-op outcomes and let unexpected exceptions propagate.Result values unchanged unless adding boundary validation or input normalization that belongs above persistence.var ok = Result.Success();var saved = Result.Success(user);var failed = Result.Failure<User>(new Error("users.save.failed", "Unable to save the user.", ex));Result<Guid> id = Guid.NewGuid();Result or Result<T>.null, false, empty collections) for expected failures once a Result-based path exists.Error can carry the underlying exception reference.