How do I install the 122 Java Type Design skill?

Run npx skillmds@latest add jabrena/122-java-type-design-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is 122 Java Type Design safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with 122 Java Type Design?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is 122 Java Type Design free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published 122 Java Type Design?

jabrena (@jabrena) published this skill. Their other Agent Skills are listed on their SkillMD profile.

122 Java Type Design by jabrena — Agent Skill

Name: 122 Java Type Design
Author: jabrena

122 Java Type Design

Use when you need to review, improve, or refactor Java code for type design quality — including establishing clear type hierarchies, applying consistent naming conventions, eliminating primitive obsession with domain-specific value objects, leveraging generic type parameters, creating type-safe wrappers, designing fluent interfaces, ensuring precision-appropriate numeric types (BigDecimal for financial calculations), and improving type contrast through interfaces and method signature alignment. Part of the skills-for-java project

jabrena Updated Sep 22, 2026

File contents

Type Design Thinking in Java

Review and improve Java code using comprehensive type design principles that apply typography concepts to code structure and organization for maximum clarity and maintainability.

What is covered in this Skill?

Clear type hierarchies: nested static classes, logical structure
Consistent naming conventions: domain-driven patterns, uniform interface/implementation naming
Strategic whitespace for readability
Type-safe wrappers: value objects replacing primitive obsession (EmailAddress, Money)
Generic type parameters: flexible reusable types, bounded parameters
Domain-specific fluent interfaces: builder pattern, method chaining
Type "weights": conceptual importance — core domain vs supporting vs utility
Type contrast through interfaces: contract vs implementation separation
Aligned method signatures: consistent parameter and return types across related classes
Self-documenting code: clear descriptive names
BigDecimal for precision-sensitive calculations (financial/monetary operations)
Strategic type selection: Optional, Set vs List, interfaces over concrete types

Scope: The reference is organized by examples (good/bad code patterns) for each core area. Apply recommendations based on applicable examples.

Constraints

Before applying any type design changes, ensure the project compiles. If compilation fails, stop immediately — do not proceed until resolved. After applying improvements, run full verification.

MANDATORY: Run ./mvnw compile or mvn compile before applying any change
SAFETY: If compilation fails, stop immediately and do not proceed — compilation failure is a blocking condition
VERIFY: Run ./mvnw clean verify or mvn clean verify after applying improvements
BEFORE APPLYING: Read the reference for detailed examples, good/bad patterns, and constraints

When to use this skill

Review Java code for type design
Improve type design in Java code
Fix primitive obsession in Java code
Create value objects in Java code
Create type hierarchies in Java code
Create fluent interfaces in Java code

Reference

For detailed guidance, examples, and constraints, see references/122-java-type-design.md.

---name: "122-java-type-design-2"description: Use when you need to review, improve, or refactor Java code for type design quality — including establishing clear type hierarchies, applying consistent naming conventions, eliminating primitive obsession with domain-specific value objects, leveraging generic type parameters, creating type-safe wrappers, designing fluent interfaces, ensuring precision-appropriate numeric types (BigDecimal for financial calculations), and improving type contrast through interfaces and method signature alignment. Part of the skills-for-java projectlicense: Apache-2.0---# Type Design Thinking in JavaReview and improve Java code using comprehensive type design principles that apply typography concepts to code structure and organization for maximum clarity and maintainability.**What is covered in this Skill?**- Clear type hierarchies: nested static classes, logical structure- Consistent naming conventions: domain-driven patterns, uniform interface/implementation naming- Strategic whitespace for readability- Type-safe wrappers: value objects replacing primitive obsession (EmailAddress, Money)- Generic type parameters: flexible reusable types, bounded parameters- Domain-specific fluent interfaces: builder pattern, method chaining- Type "weights": conceptual importance — core domain vs supporting vs utility- Type contrast through interfaces: contract vs implementation separation- Aligned method signatures: consistent parameter and return types across related classes- Self-documenting code: clear descriptive names- BigDecimal for precision-sensitive calculations (financial/monetary operations)- Strategic type selection: Optional, Set vs List, interfaces over concrete types**Scope:** The reference is organized by examples (good/bad code patterns) for each core area. Apply recommendations based on applicable examples.## ConstraintsBefore applying any type design changes, ensure the project compiles. If compilation fails, stop immediately — do not proceed until resolved. After applying improvements, run full verification.- **MANDATORY**: Run `./mvnw compile` or `mvn compile` before applying any change- **SAFETY**: If compilation fails, stop immediately and do not proceed — compilation failure is a blocking condition- **VERIFY**: Run `./mvnw clean verify` or `mvn clean verify` after applying improvements- **BEFORE APPLYING**: Read the reference for detailed examples, good/bad patterns, and constraints## When to use this skill- Review Java code for type design- Improve type design in Java code- Fix primitive obsession in Java code- Create value objects in Java code- Create type hierarchies in Java code- Create fluent interfaces in Java code## ReferenceFor detailed guidance, examples, and constraints, see [references/122-java-type-design.md](references/122-java-type-design.md).

Frequently asked questions