What problem does it solve? Turning an event-modeling board's state-change slice into working .NET code involves many conventions (handler naming, validation placement, storage strategy, test layering) that are easy to get wrong. This Skill codifies those conventions so a Wolverine.Http + Marten command slice is implemented correctly and consistently from its slice.json definition. ## Core Features & Use Cases - Slice-driven codegen: Reads slice.json (commands, events, specifications, comments) as the single source of truth and generates request/response records, a handler, and tests without inventing fields. - Dual storage strategies: Chooses between Marten document-store (IDocumentSession.Store/LoadAsync) and event-sourced (session.Events.Append with live-computed state) patterns per module, following ADR-019. - Test-first layering: Produces Layer 1 domain tests, Layer 2 mocked handler tests (xUnit, FluentAssertions, NSubstitute), and Layer 3 Testcontainers integration tests when session.Query<T>() is used. - Use Case: Given a new "EditApplicationDetails" slice on the eventmodelers.ai board, run this Skill to generate the request record with DataAnnotations validation, the <SliceName>Handler with authorization and ownership checks, Marten schema registration, and the matching test suite. ## Quick Start Ask the AI to build the state-change slice for a given slice name, after running the load-slice skill so its slice.json is fresh.