128-java-generics
This skill reviews and improves Java code for generics quality, addressing raw types, type safety, PECS wildcard principles, bounded type parameters, generic methods, the diamond operator, type erasure, generic inheritance, heap pollution prevention with @SafeVarargs, and integration with modern Java features like Records and sealed types. Use it when refactoring Java code to apply generics improvements, enhance type safety, or eliminate unsafe casts and raw types.
git clone --depth 1 https://github.com/jabrena/cursor-rules-java /tmp/128-java-generics && cp -r /tmp/128-java-generics/skills/128-java-generics ~/.claude/skills/128-java-genericsSKILL.md
# Java Generics Best Practices Review and improve Java code using comprehensive generics best practices that enforce compile-time type safety and enable flexible, reusable APIs. **What is covered in this Skill?** - Type safety: avoiding raw types, eliminating unsafe casts - Code reusability: generic methods and types for multiple type contexts - PECS wildcards: `? extends` for producers, `? super` for consumers - Diamond operator for type inference - Type erasure awareness: type tokens, factory patterns, array creation - Generic inheritance and variance: invariance, covariance, contravariance - `@SafeVarargs` for heap pollution prevention - Wildcard capture helpers, self-bounded generics (CRTP) for fluent builders - Proper wildcard API design: `Comparator<? super T>`, `Function<? super T, ? extends R>` - Arrays-vs-generics covariance pitfalls, serialization with `TypeReference`/`TypeToken` - Generic naming conventions (`T`, `E`, `K/V`, `?`), typesafe heterogeneous containers - Integration with Records, sealed types, and pattern matching **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 generics 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 - **EDGE CASE**: If request scope is ambiguous, stop and ask a clarifying question before applying changes - **EDGE CASE**: If required inputs, files, or tooling are missing, report what is missing and ask whether to proceed with setup guidance ## When to use this skill - Improve the code with Generics - Apply Generics - Refactor the code with Generics ## Workflow 1. **Compile project before generics changes** Run `./mvnw compile` or `mvn compile` and stop immediately if compilation fails. 2. **Read generics reference and assess type safety** Read `references/128-java-generics.md` and identify raw types, unsafe casts, wildcard misuse, and API variance opportunities. 3. **Apply generics refactorings** Implement selected generic type and API improvements while preserving behavior. 4. **Verify with full build** Run `./mvnw clean verify` or `mvn clean verify` after applying improvements. ## Reference For detailed guidance, examples, and constraints, see [references/128-java-generics.md](references/128-java-generics.md).
Use when you need to generate a checklist document with Java system prompts, following the embedded template exactly and producing INVENTORY-SKILLS-JAVA.md in the project root. This should trigger for requests such as Create Java system prompts checklist; Generate INVENTORY-SKILLS-JAVA.md; Use @001-skills-inventory. Part of cursor-rules-java project
Use when you need to generate a checklist document with embedded agents inventory, following the embedded template exactly and producing INVENTORY-AGENTS-JAVA.md in the project root. This should trigger for requests such as Create embedded agents inventory checklist; Generate INVENTORY-AGENTS-JAVA.md; Use @002-agents-inventory. Part of cursor-rules-java project
Use when you need to install the embedded robot agents into either .cursor/agents or .claude/agents, selecting the destination interactively and copying the embedded agent definitions from project assets. This should trigger for requests such as Install embedded agents; Bootstrap .cursor/agents; Bootstrap .claude/agents; Copy robot agents. Part of cursor-rules-java project
Guides the creation of agile epics with comprehensive definition including business value, success criteria, and breakdown into user stories. Use when the user wants to create an agile epic, define large bodies of work, break down features into user stories, or document strategic initiatives. This should trigger for requests such as Create an agile epic; Write an epic; I need to create an epic; Define an epic; Epic definition. Part of cursor-rules-java project
Guides the creation of detailed agile feature documentation from an existing epic. Use when the user wants to split an epic into feature files, derive features with scope and acceptance criteria, or plan feature documentation for stakeholders or engineering. This should trigger for requests such as Create features from an epic; Split epic into features; Feature files from epic; Derive features from epic. Part of cursor-rules-java project
Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story. Part of cursor-rules-java project
Use when you need to generate Architecture Decision Records (ADRs) for a Java project through an interactive, conversational process that systematically gathers context, stakeholders, options, and outcomes to produce well-structured ADR documents. This should trigger for requests such as Generate ADR; Create Architecture Decision Record; Document architecture decision; Architecture Decision Record for Java. Part of cursor-rules-java project
Facilitates conversational discovery to create Architectural Decision Records (ADRs) for functional requirements covering CLI, REST/HTTP APIs, or both. Use when the user wants to document command-line or HTTP service architecture, capture functional requirements, create ADRs for CLI or API projects, or design interfaces with documented decisions. This should trigger for requests such as Create ADR for functional requirements; Document functional requirements; Capture functional requirements; Generate functional requirements in an ADR. Part of cursor-rules-java project