141-java-refactoring-with-modern-features
This skill refactors Java code to leverage modern Java features from Java 8 onwards, including lambda expressions, Stream API, Optional, java.time, collection factories, text blocks, and Java 25 capabilities. Use it when modernizing legacy Java codebases or applying contemporary development best practices to improve readability and maintainability while ensuring compilation and test verification at each step.
git clone --depth 1 https://github.com/jabrena/cursor-rules-java /tmp/141-java-refactoring-with-modern-features && cp -r /tmp/141-java-refactoring-with-modern-features/skills/141-java-refactoring-with-modern-features ~/.claude/skills/141-java-refactoring-with-modern-featuresSKILL.md
# Modern Java Development Guidelines (Java 8+) Identify and apply modern Java (Java 8+) refactoring opportunities to improve readability, maintainability, and performance. **What is covered in this Skill?** - Lambda expressions and method references (over anonymous classes) - Stream API for declarative collection processing - `Optional` for null-safe APIs - `java.time` API (replacing `Date`/`Calendar`) - Default interface methods, `var` type inference - Unmodifiable collection factory methods (`List.of()`, `Set.of()`, `Map.of()`) - Text blocks for multi-line strings - Java 25 Flexible Constructor Bodies (JEP 513) - Java 25 Module Import Declarations (JEP 511) **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 modern Java refactoring, ensure the project compiles. If compilation fails, stop immediately — do not proceed until the project compiles successfully. After applying improvements, run full verification. - **MANDATORY**: Run `./mvnw compile` or `mvn compile` before applying any changes - **SAFETY**: If compilation fails, stop immediately — do not proceed until the project compiles successfully - **VERIFY**: Run `./mvnw clean verify` or `mvn clean verify` after applying improvements - **BEFORE APPLYING**: Read the reference for detailed good/bad examples, constraints, and safeguards for each modern Java feature - **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 - Review Java code for modern Java development - Apply best practices for modern Java development in Java code ## Workflow 1. **Compile project before modernization** Run `./mvnw compile` or `mvn compile` and stop immediately if compilation fails. 2. **Read modern-Java reference and identify candidates** Read `references/141-java-refactoring-with-modern-features.md` and identify high-value opportunities to adopt modern Java features. 3. **Apply modern Java refactorings** Refactor incrementally using appropriate language/library features while preserving behavior and readability. 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/141-java-refactoring-with-modern-features.md](references/141-java-refactoring-with-modern-features.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