Skip to content
cccskills
FreePublished on GitHub

145-java-refactoring-high-performance

Use when you need to refactor Java code for high performance — including memory/allocation reduction, CPU hot-path optimization, and syntax/API/control-flow improvements. This should trigger for requests such as Review Java code for high performance; Optimize Java hot path; Reduce Java allocations; Improve Java latency/throughput. Part of Plinth Toolkit

The English summary is being prepared. Showing the original description.

See how to install

Files included (4)

  • SKILL.md3.7 KB
  • references/145-refactoring-high-performance-java-code-syntax.md20.1 KB
  • references/145-refactoring-high-performance-java-cpu.md10.1 KB
  • references/145-refactoring-high-performance-java-memory-allocation.md32.6 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Java rules for High Performance

Identify and apply practical Java high-performance techniques using a measure-first approach, with emphasis on allocation reduction, data layout, concurrency discipline, and evidence-based validation.

What is covered in this Skill?

  • Measure-first workflow for Java code optimization
  • JVM/runtime-aware coding guidance
  • Allocation reduction techniques with bad/good patterns
  • CPU hot-path simplification and loop-level efficiency patterns
  • Concurrency/backpressure and timeout/cancellation discipline
  • I/O, parsing, and serialization efficiency patterns
  • Persistence/query and caching strategy guidance
  • Java-centric decision workflow: keep/revert based on measured impact

Scope: Practical optimization in application code and APIs. Apply only where profiling indicates real bottlenecks.

Constraints

Performance optimization must be evidence-driven and safe, focused on Java code changes that preserve correctness and maintainability.

  • MEASURE-FIRST: Establish baseline behavior and identify Java code hot paths before optimization
  • NO PREMATURE OPTIMIZATION: Only optimize code paths identified by profiling evidence
  • BEFORE APPLYING: Read the relevant reference(s) for bad/good examples and measurement workflow
  • EDGE CASE: If hotspot evidence is unclear, ask clarifying questions before changing code

When to use this skill

  • Review Java code for high performance
  • Optimize Java hot path
  • Reduce Java allocations
  • Improve Java latency
  • Improve Java throughput

Workflow

  1. Identify Java hotspot and baseline behavior

Confirm the performance-sensitive Java path and baseline behavior before changing code.

  1. Select the relevant reference(s) by bottleneck

Pick and read only the reference(s) matching the observed hotspot: references/145-refactoring-high-performance-java-memory-allocation.md for allocation pressure, primitives vs. wrappers, escape analysis, collection sizing, data layout, and deduplication; references/145-refactoring-high-performance-java-cpu.md for CPU-bound hot paths, bit-level parsing, branchless arithmetic, loop unrolling, Unsafe caution, and SIMD/vectorization; references/145-refactoring-high-performance-java-code-syntax.md for code shape, lambdas, API return conventions, parsing syntax, I/O strategy, concurrency, and control-flow improvements.

  1. Apply targeted optimizations

Implement minimal, evidence-backed changes scoped to the chosen domain(s): memory/allocation, CPU/low-level, or code shape/control flow (and adjacent concurrency, I/O, and persistence/caching in Java code).

  1. Validate and compare code-level outcomes

Compare before/after behavior and keep only Java code changes with meaningful, verified gains.

Reference

For detailed guidance, examples, and constraints, see:

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Use when you need to generate a checklist document with embedded commands inventory, following the embedded template exactly and producing INVENTORY-COMMANDS-JAVA.md in the project root. This should trigger for requests such as Create embedded commands inventory checklist; Generate INVENTORY-COMMANDS-JAVA.md; Use @001-commands-inventory; Inventory embedded Java project commands; List command files bundled for Java agents. Part of Plinth Toolkit

The English summary is being prepared. Showing the original description.

jabrena/plinth453Updated Oct 15, 2026

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; Inventory embedded Java agent definitions; List generated agent roles for Java development. Part of Plinth Toolkit

The English summary is being prepared. Showing the original description.

jabrena/plinth453Updated Oct 15, 2026

Use when you need to generate a checklist document with Java system prompts from skills.xml, following the embedded section template and producing INVENTORY-SKILLS-JAVA.md. This should trigger for requests such as Create Java system prompts checklist; Generate INVENTORY-SKILLS-JAVA.md; Use @003-skills-inventory; Inventory Java cursor rule skills; List available Java system prompt skills. Part of Plinth Toolkit

The English summary is being prepared. Showing the original description.

jabrena/plinth453Updated Oct 15, 2026

Use when you need to install the embedded project commands into command directories (.github/commands, .claude/commands, .cursor/command, .codex/commands), selecting the destination interactively and copying the embedded command definitions from project assets. This should trigger for requests such as Install embedded commands; Bootstrap .cursor/command; Bootstrap .claude/commands; Copy project commands; Install project command suite. Part of Plinth Toolkit

The English summary is being prepared. Showing the original description.

jabrena/plinth453Updated Oct 15, 2026

Use when you need to install the embedded robot agents into .github/agents, .claude/agents, .cursor/agents, or .codex/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 .github/agents; Bootstrap .cursor/agents; Bootstrap .claude/agents; Bootstrap .codex/agents; Copy robot agents. Part of Plinth Toolkit

The English summary is being prepared. Showing the original description.

jabrena/plinth453Updated Oct 15, 2026

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 Plinth Toolkit

The English summary is being prepared. Showing the original description.

jabrena/plinth453Updated Oct 15, 2026

See all skills by jabrena

Report a problem with this skill