본문으로 건너뛰기
cccskills
무료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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jabrena/plinth
설치 방법 보기

포함된 파일(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(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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:

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

001-commands-inventory

무료

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jabrena/plinth4532026년 10월 15일 업데이트

002-agents-inventory

무료

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jabrena/plinth4532026년 10월 15일 업데이트

003-skills-inventory

무료

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jabrena/plinth4532026년 10월 15일 업데이트

004-commands-installation

무료

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jabrena/plinth4532026년 10월 15일 업데이트

005-agents-installation

무료

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jabrena/plinth4532026년 10월 15일 업데이트

012-agile-epic

무료

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jabrena/plinth4532026년 10월 15일 업데이트

jabrena의 스킬 모두 보기

이 스킬의 문제 신고