123-java-design-patterns — Claude Code skill: setup
The 123-java-design-patterns skill helps choose, review, and apply Java patterns for APIs, Kafka, persistence, and integrations.
Apache-2.0 267 installs ★ 465 updated 2026-10-21
npx skills add jabrena/plinth --skill 123-java-design-patterns -a claude-codeWhat 123-java-design-patterns does
The skill starts with the design pressure instead of a pattern name, then selects the smallest useful solution. It covers classic Java patterns, REST resource and contract design, Kafka and event-driven systems, persistence, transactions, locking, migrations, outbox, sagas, and integration boundaries.
Its workflow points to one of five references: references/123-java-design-patterns.md, references/123-rest-api-patterns.md, references/123-kafka-event-driven-patterns.md, references/123-database-persistence-patterns.md, or references/123-cross-cutting-integration-patterns.md. Recommendations must explain the benefit, cost, and cases where the pattern should be avoided.
Before refactoring, the skill requires ./mvnw compile or mvn compile; after code changes it requires ./mvnw clean verify or mvn clean verify. That build check is part of its operating rules.
What it helps with
- choose a pattern for changing object behavior
- shape a REST contract with idempotency and versioning
- design Kafka delivery with retries and an outbox
- align transactions, aggregates, and read models
- harden integration boundaries and error handling
Example prompts for the agent
- Choose a suitable pattern for this Java code where behavior varies, and explain the trade-offs.
- Review this REST API for idempotency, versioning, and error-handling issues.
- Design the Kafka events for this flow and show where retries, an outbox, or a saga belongs.
How to install 123-java-design-patterns
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 123-java-design-patterns -a claude-code2Manually: put the files in place
~/.claude/skills/123-java-design-patterns/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/123-java-design-patterns/
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 123-java-design-patterns -a codex2Manually: put the files in place
.agents/skills/123-java-design-patterns/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 123-java-design-patterns -a cursor2Manually: put the files in place
.cursor/skills/123-java-design-patterns/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install jabrena/plinth skills/123-java-design-patterns2Manually: put the files in place
.github/skills/123-java-design-patterns/SKILL.md1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 123-java-design-patterns -a gemini-cli2Platform CLI
gemini skills install https://github.com/jabrena/plinth --path skills/123-java-design-patternsManually: put the files in place
.devin/skills/123-java-design-patterns/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 123-java-design-patterns -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about 123-java-design-patterns
How do I install 123-java-design-patterns in Claude Code?
Run npx skills add jabrena/plinth --skill 123-java-design-patterns -a claude-code. The installed skill will be available at ~/.claude/skills/123-java-design-patterns/SKILL.md.
What does 123-java-design-patterns do?
It helps select, review, and implement Java patterns from a concrete design problem. Its coverage includes REST APIs, Kafka, persistence, and integration work, with trade-offs for each recommendation.
Which references does the skill use?
It selects the relevant file from five references covering Java patterns, REST APIs, Kafka and event-driven design, persistence, and cross-cutting integration patterns.
Source text
SKILL.md · Apache-2.0
--- name: 123-java-design-patterns description: Use when you need to select, review, or implement Java design and integration patterns — including classic Java design patterns, REST API patterns, Kafka and event-driven patterns, database and persistence patterns, and cross-cutting integration patterns. This should trigger for requests such as Apply Java design patterns; Review REST API patterns; Design Kafka event-driven patterns; Improve database persistence patterns; Add resilient integration patterns. Part of Plinth Toolkit license: Apache-2.0 metadata: author: Juan Antonio Breña Moral version: 0.19.0 --- # Java Design and Integration Patterns Guide Java developers in selecting patterns by problem signal, implementation context, and trade-off rather than by pattern name alone. **What is covered in this Skill?** - Classic Java design patterns for application code: creational, structural, and behavioral patterns - REST API patterns for resource design, contracts, idempotency, versioning, and error handling - Kafka and event-driven patterns for event schemas, partitioning, idempotency, retries, outbox, and sagas - Database and persistence patterns for repositories, transactions, aggregates, locking, migrations, and read models - Cross-cutting integration patterns for anti-corruption layers, resilience, observability, and reliable message boundaries **Scope:** Use this skill to explain, review, and implement practical patterns in Java systems. Prefer simple code first; introduce a pattern only when it reduces real complexity, protects a boundary, improves testability, or makes change safer. ## Constraints Pattern guidance must be problem-led, concrete, and safe to apply in Java projects. - **PROBLEM FIRST**: Identify the design pressure before naming or applying a pattern - **NO PATTERN SHOPPING**: Do not add abstractions only because a pattern exists; prefer simple code when variation is not present - **BUILD SAFETY**: For code changes, run `./mvnw compile` or `mvn compile` before refactoring and `./mvnw clean verify` or `mvn clean verify` after changes - **REFERENCE SELECTION**: Read the relevant reference before acting: Java code patterns, REST API patterns, Kafka/event-driven patterns, database/persistence patterns, or cross-cutting integration patterns - **TRADE-OFFS REQUIRED**: Explain the benefit, cost, and when-not-to-use guidance for any recommended pattern ## When to use this skill - Apply Java design patterns - Review Java code for design patterns - Choose REST API patterns - Design Kafka event-driven patterns - Improve database persistence patterns - Add resilient integration patterns ## Workflow 1. **Identify the design pressure** Clarify the concrete problem: object creation, behavior variation, API contract evolution, event delivery, persistence consistency, integration reliability, or another recurring design force. 2. **Select the relevant reference** Read only the matching reference(s): `references/123-java-design-patterns.md`, `references/123-rest-api-patterns.md`, `references/123-kafka-event-driven-patterns.md`, `references/123-database-persistence-patterns.md`, or `references/123-cross-cutting-integration-patterns.md`. 3. **Recommend the smallest useful pattern** Choose the simplest pattern that addresses the design pressure. Show how it changes responsibilities, boundaries, tests, operations, or evolution safety. 4. **Implement or document the pattern** When code changes are requested, make focused Java or configuration changes following the project conventions. When design advice is requested, provide diagrams, examples, request/response shapes, event shapes, or transaction flows as appropriate. 5. **Validate the outcome** Verify that the resulting design remains understandable, testable, and operationally safe. Run the project build for code changes and name any remaining trade-offs. ## Reference For detailed guidance, examples, and constraints, see: - [references/123-java-design-patterns.md](references/123-java-design-patterns.md) - [references/123-rest-api-patterns.md](references/123-rest-api-patterns.md) - [references/123-kafka-event-driven-patterns.md](references/123-kafka-event-driven-patterns.md) - [references/123-database-persistence-patterns.md](references/123-database-persistence-patterns.md) - [references/123-cross-cutting-integration-patterns.md](references/123-cross-cutting-integration-patterns.md)
© Juan Antonio Breña Moral · Apache-2.0 · jabrena/plinth