HeroesOfDomainDrivenDesign.EventSourcing.DCB.Kotlin.Axon5.Spring

Project-specific review checklist for this repository (DDD + Event Sourcing + Axon Framework 5 invariants). Use when: (1) reviewing code changes, a diff, or a pull request in this repository, (2) user says 'review', 'code review', 'check this change', (3) any automated review action runs for this repo.

Subject matter expert on Dynamic Consistency Boundary (DCB) — a technique for enforcing consistency in event-driven systems without rigid transactional boundaries. Use when the user asks about DCB concepts, specification, patterns, examples, or compares DCB with traditional Event Sourcing approaches (aggregates, event streams, sagas). Covers topics including tags, projections, decision models, append conditions, queries, and the DCB-compliant Event Store interface. Implementation-agnostic — explains concepts without adhering to any specific library or language.

Work with proophboard Event Modeling boards via MCP. Read, create, and modify event models — chapters, lanes, slices, and elements (commands, events, information, automations, UI, hotspots). Use when: (1) user asks to read, explore, or understand an event model on proophboard, (2) user asks to create or modify chapters, slices, or elements on the board, (3) user asks to model a feature, flow, or bounded context using Event Modeling, (4) user says 'proophboard', 'event model', 'board', 'add slice to board', 'model this on proophboard', 'update the board', (5) translating between code and event model (syncing implementation status with board slices).

Implement Event Sourcing write slices using Axon Framework 5, Vertical Slice Architecture, and Event Modeling patterns. A write slice is: Command to decide to Events to evolve to State. Use when: (1) implementing a new write slice / command handler in an AF5 project, (2) migrating/porting a write slice from Axon Framework 4 (Java or Kotlin) to AF5, (3) user provides a specification, Event Modeling artifact, existing tests, or natural language description of a command and asks to implement it, (4) user says "implement", "create", "add", "migrate", "port" a write slice, command handler, or aggregate behavior in an Axon Framework 5 / Vertical Slice Architecture project. Understands AF4 aggregate-based input as one possible source format.

Implement automation slices (Event to Command) using Axon Framework 5, Vertical Slice Architecture, and Event Modeling patterns. An automation is: an Event Handler that reacts to an event by dispatching a command via CommandDispatcher. Automations can be stateless (direct event-to-command mapping) or with a private read model (to look up data needed for command construction). Use when: (1) implementing a new automation / event-to-command reactor in an AF5 project, (2) migrating/porting an automation from Axon Framework 4 (Java or Kotlin) to AF5, (3) user provides a specification, Event Modeling artifact, or natural language description of an event-to-command reaction and asks to implement it, (4) user says "implement", "create", "add", "migrate", "port" an automation, event handler, reactor, or event-to-command flow in an Axon Framework 5 / Vertical Slice Architecture project. Understands AF4 @EventHandler/@ProcessingGroup input as one possible source format.

Implement read slices (projections + query handlers + REST API + tests) using Axon Framework 5 AxonTestFixture with Spring Boot integration tests. A read slice is: Events projected into a Read Model, queried via QueryGateway. Use when: (1) implementing a new read slice / projection in an AF5 project, (2) migrating/porting a read slice from Axon Framework 4 (Java or Kotlin) to AF5, (3) user provides a read slice specification or Event Modeling artifact and asks to implement it, (4) user says "implement", "create", "add" a read slice, projection, query handler, or read model in an Axon Framework 5 / Vertical Slice Architecture project.

Implement a single Event Modeling slice from proophboard — discover slices via MCP, let the user choose which one, delegate to the matching implementation skill (write/read/automation), run quality gates, handle git branching, and ask the user how to finalize (merge or PR). Use when: (1) user says "implement slice", "implement next slice", "/em-proophboard-code", (2) user wants to pick and implement a slice from the event model board, (3) user provides a slice ID or name and asks to implement it, (4) user says "what slices are planned" and wants to implement one.

Backup proophboard Event Modeling workspace to local JSON files. Downloads all chapters (with lanes, slices, elements) into .proophboard/chapters/ and records backup metadata. Use when: (1) user says 'backup', 'sync', 'download', 'snapshot' in context of proophboard or event model, (2) user wants to save the current board state to git, (3) user says 'em-proophboard-backup' or '/em-proophboard-backup'.

Show implementation status of Event Modeling slices from proophboard. For each chapter, display a table mapping board slices (write/read/automation) to their codebase implementation and tests. Read-only — no board or code modifications. Use when: (1) user asks about implementation status, progress, or coverage of event model slices, (2) user says 'status', 'overview', 'what is implemented', 'what is missing' in context of proophboard or event model, (3) user wants to see which slices have code and tests, (4) user says 'em-proophboard-status' or '/em-proophboard-status'.

Create git commits following project conventions: Conventional Commits + Gitmoji with Unicode emojis. Use when: (1) user says 'commit', '/commit', 'create a commit', (2) user asks to commit changes, (3) user asks for a commit message, (4) after completing implementation work and user wants to commit.