ddd4j-web
Installation
SKILL.md
ddd4j Web
Overview
ddd4j-web-core defines the cross-runtime behavior. Each adapter implements the same HTTP contract. Framework APIs may differ, but response, context, and security behavior must remain consistent.
When to Use
- Implementing or porting the ddd4j HTTP contract across the adapters:
webmvc,webflux,javalin,quarkus,micronaut,vertx,helidon,dropwizard. - Binding Request/Trace/Tenant/Subject context at the entry point and cleaning up on success, exception, and async completion.
- Mapping failures to the stable error contract (400, 401, 403, 404, 409, 415, 422, 429, 500) without leaking internal stack traces.
- Using the validation constraints —
AllowableValues(allows, nullable),PhoneNumber(lang),NumberValue(regex),StringDateValue(pattern)— and wiring the Jakarta/Javax validation dependency per line. - Configuring production controls: idempotency scope, CORS allowlist, request-size/timeout/rate limits.
- Separating liveness from readiness, with readiness aggregating real dependencies (DB, MQ, Auth, Outbox).
- Aligning runtimes with
web-testkitendpoints and assertions.
When NOT to Use
Do not use this skill when: