143-java-functional-exception-handling
This Claude Code skill applies functional exception handling best practices to Java codebases by replacing exception-based control flow with monadic types like Optional and VAVR Either, designing error hierarchies using sealed classes and enums, and implementing functional composition patterns for error handling. Use it when refactoring Java code to improve error clarity and maintainability by reducing exception overuse for predictable business failures while reserving exceptions for system-level failures.
git clone --depth 1 https://github.com/jabrena/cursor-rules-java /tmp/143-java-functional-exception-handling && cp -r /tmp/143-java-functional-exception-handling/skills/143-java-functional-exception-handling ~/.claude/skills/143-java-functional-exception-handlingSKILL.md
# Java Functional Exception handling Best Practices Identify and apply functional exception handling best practices in Java to improve error clarity, maintainability, and performance by eliminating exception overuse in favour of monadic error types. **What is covered in this Skill?** - `Optional<T>` for nullable values over throwing `NullPointerException` or `NotFoundException` - VAVR `Either<L,R>` for predictable business-logic failures - `CompletableFuture<T>` for async error handling - Sealed classes and records for rich error type hierarchies with exhaustive pattern matching - Enum-based error types for simple failure cases - Functional composition: `flatMap`/`map`/`peek`/`peekLeft` for chaining operations that can fail - Structured logging: warn/info for business failures, error for system failures - Checked vs unchecked exception discipline - Exception chaining with full causal context when exceptions are unavoidable **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 functional exception handling changes, ensure the project validates. When introducing Either types, confirm the VAVR dependency (io.vavr:vavr) and SLF4J are present. - **MANDATORY**: Run `./mvnw validate` or `mvn validate` before applying any changes - **SAFETY**: If validation fails, stop immediately — do not proceed until the project is in a valid state - **DEPENDENCY**: When introducing `Either` types, confirm VAVR (`io.vavr:vavr`) and SLF4J are present - **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 functional exception handling pattern ## When to use this skill - Improve the code with Functional Exception Handling - Apply Functional Exception Handling - Refactor the code with Functional Exception Handling ## Workflow 1. **Validate project before functional-exception changes** Run `./mvnw validate` or `mvn validate` and stop immediately if validation fails. 2. **Check required dependencies** When introducing `Either`, confirm VAVR (`io.vavr:vavr`) and SLF4J are present before implementation. 3. **Read functional-exception reference and identify targets** Read `references/143-java-functional-exception-handling.md` and identify places to replace exception-heavy control flow with monadic error types. 4. **Apply functional exception-handling refactorings** Implement selected `Optional`/`Either`/async error patterns with structured logging and clear error contracts. 5. **Verify with full build** Run `./mvnw clean verify` or `mvn clean verify` after applying improvements. ## Reference For detailed guidance, examples, and constraints, see [references/143-java-functional-exception-handling.md](references/143-java-functional-exception-handling.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