wow

name: wow description: | Wow framework assistant for building reactive DDD + Event Sourcing + CQRS microservices in Kotlin/Java on JVM 17+ with Spring Boot.

Use this skill when a task involves Wow framework semantics:

• DDD aggregates, command/event/state modeling, bounded contexts, tenant/owner routing
• CQRS, Event Sourcing, event stores, snapshots, projections, read models
• Saga orchestration, event processors, retry policy, PrepareKey
• Command gateway, wait plans, command bus, WebFlux command endpoints
• Wow tests: AggregateSpec, SagaSpec, AggregateVerifier, SagaVerifier
• Wow annotations such as @AggregateRoot, @OnCommand, @OnSourcing, @OnEvent, @StatelessSaga, @ProjectionProcessor, @EventProcessor, @AfterCommand, @OnError, @Retry, @BoundedContext, @CreateAggregate, @CommandRoute

Do not trigger for unrelated Kotlin, Gradle, frontend, or documentation tasks unless Wow framework behavior or APIs are directly relevant. compatibility: Kotlin 2.3, JVM 17+, Spring Boot 4.x, Gradle, MongoDB, Kafka, Reactor

Wow Framework Skill

Use this as the router for Wow framework work. For end-to-end aggregate or saga development, route to ../wow-development-workflow/SKILL.md. For focused lookup, load the smallest reference file that matches the task, then verify exact APIs in the current checkout before editing code.

Source-First Rule

Before writing or changing Wow code, verify the current implementation with rg, rg --files, and nearby source files. Examples in this skill and its references are navigation aids, not a substitute for the target repository's APIs.

Useful first searches:

rg -n "@AggregateRoot|@OnCommand|@OnSourcing|@StatelessSaga|@ProjectionProcessor" . -g "*.kt"
rg -n "AggregateSpec<|SagaSpec<|aggregateVerifier|sagaVerifier" . -g "*.kt"
rg -n "@ConfigurationProperties|class .*Properties" wow-spring-boot-starter -g "*.kt"

Task Routing

Core Model

Wow applications normally separate command handling from state mutation:

Command -> Command Aggregate -> Event -> EventStore -> EventBus
                                      -> State Aggregate sourcing
                                      -> Projection / Saga / EventProcessor

Prefer the Aggregate Pattern: command aggregate handles commands and returns events; state aggregate mutates only through sourcing handlers. Avoid direct state mutation in command handlers.

Quality Gates

Before finishing Wow code changes, check:

• Command handlers return domain events and do not mutate state directly.
• Commands and domain events include @Summary and @Description metadata when they are part of the API/domain contract.
• Important repeated domain fields are modeled with <FieldName>Capable interfaces where reuse improves clarity.
• State changes happen through deterministic sourcing handlers.
• Handlers returning polymorphic Any or multiple event types declare explicit return metadata when the current API requires it.
• Saga logic has both trigger and no-command tests when conditions branch.
• Aggregate behavior is tested with AggregateSpec; saga orchestration is tested with SagaSpec.
• Projection and event processor side effects are outside aggregates.
• Tests use me.ahoo.test.asserts.assert / .assert().
• Gradle commands use resolved module names from settings.gradle.kts, not hard-coded api or domain placeholders.
• Verification commands are reported exactly.

References

Skill Maintenance

Run the skill lint before finishing changes to this skill set:

python3 scripts/skill_lint.py