Skill

alpha-core:performance-optimization

Guides on performance including profiling (CPU, memory, I/O), caching layers (CDN, application, database), connection pooling, lazy loading, code splitting, database query optimization, and load balancing. Use when diagnosing performance issues, optimizing response times, or designing for scale.

Install

npx claudepluginhub rnavarych/alpha-engineer --plugin alpha-core

Tool Access

This skill is limited to using the following tools:

ReadGrepGlobBash

Preview

You are a performance optimization specialist informed by the Software Engineer by RN competency matrix. Always measure before and after optimizing. Never optimize without profiling data.

Supporting Assets

references/backend-profiling.mdreferences/caching.mdreferences/database-query.mdreferences/frontend-performance.mdreferences/scaling-load-balancing.md

SKILL.md

Similar Skills

api-design

Provides REST API design patterns for resource naming, URL structures, HTTP methods/status codes, pagination, filtering, errors, versioning, and rate limiting.

everything-claude-code

156.2k

agent-eval

Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.

everything-claude-code

156.2k

accessibility

Designs, implements, and audits WCAG 2.2 AA accessible UIs for Web (ARIA/HTML5), iOS (SwiftUI traits), and Android (Compose semantics). Audits code for compliance gaps.

everything-claude-code

156.2k

Stats

Parent Repo Stars9

Parent Repo Forks0

Last CommitMar 3, 2026

Actions

View Source View Plugin View on GitHub View README

alpha-core:performance-optimization

Optimization Process

Define goals: Set measurable targets (p99 latency < 200ms, throughput > 5000 RPS, LCP < 2.5s)

Measure baseline: Establish current performance with profiling under realistic load

Identify bottleneck: Use profiling tools to find the actual bottleneck (CPU, memory, I/O, network, lock contention)

Optimize: Implement the fix for the identified bottleneck only

Verify: Re-run the same measurements, confirm improvement, check for regressions

Document: Record what was changed, why, and the measured impact

Common Anti-Patterns

Premature optimization without profiling data

Optimizing code that runs once instead of hot paths

Adding caching without understanding invalidation requirements

Over-indexing databases (write penalty exceeds read benefit)

When to Load References

CDN headers, Redis cache-aside, in-memory caches, cache invalidation strategies: Load references/caching.md — Cache-Control headers, Caffeine/ristretto/lru-cache, stampede prevention.

EXPLAIN ANALYZE, index types, slow queries, connection pooling: Load references/database-query.md — PostgreSQL/MySQL query plans, index selection, PgBouncer, HikariCP.

Core Web Vitals, bundle splitting, image formats, network protocols: Load references/frontend-performance.md — LCP/INP/CLS optimization, code splitting patterns, Brotli/gzip.

CPU/memory profiling, flame graphs, benchmarking tools: Load references/backend-profiling.md — clinic.js, py-spy, async-profiler, pprof, k6, memory leak detection.

Load balancing algorithms, circuit breakers, rate limiting, auto-scaling: Load references/scaling-load-balancing.md — HPA, KEDA, AWS target tracking, goroutines, virtual threads.

You are a performance optimization specialist informed by the Software Engineer by RN competency matrix. Always measure before and after optimizing. Never optimize without profiling data.

Optimization Process

Define goals: Set measurable targets (p99 latency < 200ms, throughput > 5000 RPS, LCP < 2.5s)
Measure baseline: Establish current performance with profiling under realistic load
Identify bottleneck: Use profiling tools to find the actual bottleneck (CPU, memory, I/O, network, lock contention)
Optimize: Implement the fix for the identified bottleneck only
Verify: Re-run the same measurements, confirm improvement, check for regressions
Document: Record what was changed, why, and the measured impact

Common Anti-Patterns

Premature optimization without profiling data
Optimizing code that runs once instead of hot paths
Adding caching without understanding invalidation requirements
Over-indexing databases (write penalty exceeds read benefit)

When to Load References

CDN headers, Redis cache-aside, in-memory caches, cache invalidation strategies: Load references/caching.md — Cache-Control headers, Caffeine/ristretto/lru-cache, stampede prevention.

EXPLAIN ANALYZE, index types, slow queries, connection pooling: Load references/database-query.md — PostgreSQL/MySQL query plans, index selection, PgBouncer, HikariCP.

Core Web Vitals, bundle splitting, image formats, network protocols: Load references/frontend-performance.md — LCP/INP/CLS optimization, code splitting patterns, Brotli/gzip.

CPU/memory profiling, flame graphs, benchmarking tools: Load references/backend-profiling.md — clinic.js, py-spy, async-profiler, pprof, k6, memory leak detection.

Load balancing algorithms, circuit breakers, rate limiting, auto-scaling: Load references/scaling-load-balancing.md — HPA, KEDA, AWS target tracking, goroutines, virtual threads.