agentleFS
Sign inStart free
jabrenajabrena/cursor-rules-java/skills/142-java-functional-programming/SKILL.md

142-java-functional-programming

Skill452 starsChanged 3 months agoApache-2.0View on GitHub

Use when you need to apply functional programming principles in Java — including writing immutable objects and Records, pure functions, functional interfaces, lambda expressions, Stream API pipelines, Optional for null safety, function composition, higher-order functions, pattern matching for instanceof and switch, sealed classes/interfaces for controlled hierarchies, Stream Gatherers for custom operations, currying/partial application, effect boundary separation, and concurrent-safe functional patterns. This should trigger for requests such as Improve the code with Functional Programming; Apply Functional Programming; Refactor the code with Functional Programming; Refactor Java code to use streams or Optionals safely; Improve immutability and pure functions in Java. Part of Plinth Toolkit

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 7 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before applying any functional programming changes, ensure the project compiles.

    line 33
  2. Very specific:

    MANDATORY: Run ./mvnw compile or mvn compile before applying any changes

    line 35
  3. Distinctive:

    SAFETY: If compilation fails, stop immediately — do not proceed until the project compiles successfully

    line 36
  4. Distinctive:

    VERIFY: Verify maven-compiler-plugin source/target supports the Java features being used

    line 37
  5. Very specific:

    VERIFY: Run ./mvnw clean verify or mvn clean verify after applying improvements

    line 38
  6. Distinctive:

    BEFORE APPLYING: Read the reference for detailed good/bad examples, constraints, and safeguards for each functional programming pattern

    line 39
  7. Distinctive:

    EDGE CASE: If request scope is ambiguous, stop and ask a clarifying question before applying changes

    line 40
  8. Distinctive:

    EDGE CASE: If required inputs, files, or tooling are missing, report what is missing and ask whether to proceed with setup guidance

    line 41
  9. Very specific:

    Run ./mvnw compile or mvn compile and stop immediately if compilation fails.

    line 55
  10. Distinctive:

    Verify maven-compiler-plugin source/target supports the functional features planned for adoption.

    line 59
  11. Very specific:

    Read references/142-java-functional-programming.md and identify opportunities for immutability, pure functions, and functional composition.

    line 63
  12. Very specific:

    Run ./mvnw clean verify or mvn clean verify after applying improvements.

    line 71

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Java Functional Programming rules

Identify and apply functional programming principles in Java to improve immutability, expressiveness, and maintainability.

What is covered in this Skill?

  • Immutable objects and Records (JEP 395)
  • Pure functions free of side effects
  • Functional interfaces: Function, Predicate, Consumer, Supplier, custom @FunctionalInterface
  • Lambda expressions and method references
  • Stream API: filter/map/reduce pipelines, parallel streams, toUnmodifiable* collectors
  • Optional idiomatic usage: map/flatMap/filter/orElse* over isPresent()+get()
  • Function composition: andThen/compose
  • Higher-order functions: memoization, currying, partial application
  • Pattern Matching for instanceof and switch (Java 21)
  • Sealed classes and interfaces (Java 17) for exhaustive domain hierarchies
  • Switch Expressions (Java 14), Stream Gatherers (JEP 461)
  • Effect-boundary separation: side effects at edges, pure core logic
  • Immutable collections: List.of(), Collectors.toUnmodifiableList()

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 programming changes, ensure the project compiles. If compilation fails, stop immediately — do not proceed until the project compiles successfully. Verify that maven-compiler-plugin source/target supports the Java features being used.

  • 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: Verify maven-compiler-plugin source/target supports the Java features being used
  • 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 programming pattern
  • 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 Functional Programming
  • Apply Functional Programming
  • Refactor the code with Functional Programming
  • Refactor Java code to use streams or Optionals safely
  • Improve immutability and pure functions in Java

Workflow

  1. Compile project before functional refactoring

Run ./mvnw compile or mvn compile and stop immediately if compilation fails.

  1. Confirm Java feature compatibility

Verify maven-compiler-plugin source/target supports the functional features planned for adoption.

  1. Read functional-programming reference and assess code

Read references/142-java-functional-programming.md and identify opportunities for immutability, pure functions, and functional composition.

  1. Apply functional programming improvements

Implement selected functional refactorings while keeping side effects at boundaries.

  1. Verify with full build

Run ./mvnw clean verify or mvn clean verify after applying improvements.

Reference

For detailed guidance, examples, and constraints, see references/142-java-functional-programming.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free