optimization

Identify and fix performance bottlenecks through measurement-driven optimization.

1|1|Updated May 7, 2026
One-click install
npx skills add https://github.com/chapzin/jcode-harness --skill optimization-chapzin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: optimization
Source: https://github.com/chapzin/jcode-harness/tree/main/.jcode/skills/optimization
Command: npx skills add https://github.com/chapzin/jcode-harness --skill optimization-chapzin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performance engineering helps teams improve system speed, efficiency, and resource usage by defining metrics, measuring thoroughly, attributing bottlenecks, and prioritizing macro-optimizations before micro-optimizations.

Core Features & Use Cases

  • Define target metrics and baselines for latency, throughput, memory, and CPU.
  • Attribute bottlenecks across code, services, and pipelines, then apply macro- and micro-optimizations.
  • Use static analysis to validate improvements and guard against regressions.

Quick Start

Provide a simple directive to start optimizing.

Frequently Asked Questions about optimization

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify performance bottlenecks in my software system?

Performance bottlenecks are identified through measurement-driven profiling that collects data on latency, throughput, memory, and CPU to attribute costs across code, services, and build pipelines.

What is the best way to prioritize macro-optimizations over micro-optimizations?

Prioritize macro-optimizations by establishing target metrics and baselines first, then applying measurement-driven profiling to attribute major bottlenecks across modules before attempting micro-level code improvements.

How do I set target metrics and baselines for system profiling?

System profiling baselines are set by defining target metrics for latency, throughput, memory, and CPU usage, which provides the measurement foundation needed to evaluate optimization progress and guard against regressions.

Can I use static analysis to validate performance improvements and prevent regressions?

Static analysis is used to validate performance improvements by checking optimized code against established metrics, ensuring macro- and micro-optimizations hold and guarding against future performance regressions.

Does measurement-driven optimization work for codebases and systems at any scale?

Measurement-driven optimization applies to codebases and systems at any scale, guiding teams from initial profiling through macro-optimizations across modules, services, and build pipelines regardless of system size.

When should I start profiling to fix latency and throughput issues?

Profiling should start immediately after defining target metrics and baselines for latency and throughput, enabling you to collect data, attribute costs, and apply optimizations in a prioritized, measurement-driven manner.