ai-toolkit-java-design

Plugin ai-toolkit-java-design from marketplace ai-toolkit in oriddd/ai-toolkit. Commands read from the repo's manifest — yesterday.

Skills (13)

• api-design

  Java / Spring Boot REST API design — resources and URLs, HTTP verbs, status codes, versioning, pagination/filtering/sorting, deprecation headers, RFC 9457 errors, OpenAPI-first vs code-first. Use when designing a new endpoint or reviewing an existing API.

• async-api-patterns

  Java / Spring Boot long-running operations — submit-poll-result jobs, webhooks, SSE, job state, cleanup of abandoned jobs, idempotent submits. Use when an endpoint would run longer than ~2 seconds or must return a job handle instead of blocking.

• code-structure

  Java / Spring Boot package hierarchy and layering — controller/operation/service, filter + recorder; every class a small, testable LEGO brick. Runtime-selected behaviour: `strategy-registry-pattern`. Use before creating or editing ANY Java class, package, controller, service or operation.

• domain-modeling

  Java / Spring Boot tactical DDD — bounded context, aggregate root, entity, value object, domain event, domain service, repository, anti-corruption layer, specification. Use during initial design or when adding a new aggregate to a service.

• feature-flags

  Java / Spring Boot feature toggles — local config toggles, remote providers (Unleash, LaunchDarkly), toggle-at-the-edge vs toggle-in-logic, flag lifecycle and cleanup. Use when a change must be toggled at runtime or released dark.

• openapi-first-codegen

  Java / Spring Boot OpenAPI-first — generate controllers and DTOs from api.yaml with openapi-generator-maven-plugin, exclude generated code from coverage and analysis, keep generated DTOs inside the controller. Use when the spec should be the single source of truth.

• pattern-selection

  Java / Spring Boot: choose the smallest pattern that fits the actual scale — decision tables for clients, operations and layers, over-engineering red flags. Use before introducing any new layer, pattern, client package or abstraction.

• pluggable-architecture

  Java / Spring Boot ports and adapters — every external technology (cache, DB, broker, metrics, object store, secrets, identity) behind a port, with adapters chosen by configuration via conditional beans. Use before writing ANY code that talks to an external tool or technology.

• response-layout

  Java / Spring Boot ?layout= parameter (summary/detailed/full) via Strategy + Handler + Registry — one LayoutStrategy per field set. Use when an endpoint must return different field sets on request. For API versions or projections use `response-mapper`.

• response-mapper

  Java / Spring Boot API versioning and response projections via Strategy + Handler + Registry — version resolved from Accept header, URI or query param; one MapperStrategy per version. Use when an API serves several versions or projections. For ?layout= use `response-layout`.

• spring-boot-conventions

  Java / Spring Boot 3 idioms — @ConfigurationProperties over @Value, profiles, conditional beans, @Async with named executors, caching, pagination, idempotency, application events. Use whenever a Spring Boot feature is about to be used.

• strategy-registry-pattern

  Java / Spring Boot Strategy + Registry + Handler for runtime-selected behaviour — add a strategy class, never edit the dispatcher (Open/Closed). Use when several implementations are chosen at runtime by URI, caller, parameter or version. Not for plain validation.

• testable-code-principles

  Java / Spring Boot testability principles — small LEGO-brick classes, names over comments, SOLID mapped to testing, no static methods, global state or hidden side effects. Use before writing a new class or when reviewing code quality. Package layout lives in `code-structure`.

Hooks (1)

• SessionStart

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/detect-and-route.sh"

Similar plugins