performance-optimization

Profile CPU, memory, and I/O to prioritize and prevent performance regressions.

31|3|Updated Dec 12, 2025
One-click install
npx skills add https://github.com/JeremyDev87/codingbuddy --skill performance-optimization-jeremydev87
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: performance-optimization
Source: https://github.com/JeremyDev87/codingbuddy/tree/main/packages/rules/.ai-rules/skills/performance-optimization
Command: npx skills add https://github.com/JeremyDev87/codingbuddy --skill performance-optimization-jeremydev87

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performance optimization helps teams identify real bottlenecks through profiling before making changes, preventing wasted effort on low-impact fixes.

Core Features & Use Cases

  • Systematic profiling strategy using CPU, memory, I/O, and distributed traces
  • Five-phase workflow: Profile, Benchmark, Prioritize, Optimize, Prevent
  • Real-world use case: slowdown in a REST API or UI lag can be measured, prioritized by ROI, and prevented via CI gates

Quick Start

Run a profiling session on your codebase to begin the five-phase workflow and establish a baseline.

Frequently Asked Questions about performance-optimization

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

FAQPage Schema
What is the best way to profile slow API endpoints before optimizing code?▼

The best way to profile slow API endpoints is using a profiling-first workflow that measures CPU, memory, and I/O bottlenecks to establish a performance baseline before making code changes.

How do I optimize UI lag and memory-heavy processes systematically?▼

You optimize UI lag and memory-heavy processes through a five-phase workflow: Profile, Benchmark, Prioritize by ROI, Optimize, and Prevent, ensuring measured improvements rather than guesswork.

How do I prevent performance regressions in a continuous integration pipeline?▼

You prevent performance regressions by implementing CI gates and regression monitoring after optimization, ensuring code changes are validated against repeatable benchmarks established during prior profiling sessions.

Why should I benchmark code before fixing performance bottlenecks?▼

You should benchmark code before fixing bottlenecks to prioritize changes by ROI, preventing wasted effort on low-impact fixes and ensuring actual performance gains are measurable and repeatable.

Can I use distributed traces for profiling build delays and I/O operations?▼

Yes, you can use distributed traces alongside CPU and memory profiling to identify I/O bottlenecks and build delays, providing comprehensive observability across your application's performance.