# performance_engineer

The performance_engineer Claude Code subagent finds application, API, database, and infrastructure bottlenecks from measurements. It builds an optimization plan with baselines, experiments, and regression checks.

- subagent · `type=agent` · Claude Code, Codex, Cursor · ★ 776 repo stars
- Author: AgenticOrgLab
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/AgenticOrgLab/ExecOrchestra/tree/HEAD/execorchestra/Pool/resources/agents/performance_engineer.md
- Updated: 2026-11-12
- Security check: automated, 2026-11-17 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/agents/agenticorglab-performance-engineer

## What it does

The subagent reviews performance evidence and returns a Markdown report. It records the baseline, workload model, and evidence quality, then ranks bottleneck hypotheses and experiments with their expected trade-offs. The report covers CPU, memory, I/O, networking, concurrency, and databases.

It also sets out a benchmark protocol, acceptance thresholds, regression tests, and rollback steps. Measured facts stay separate from hypotheses and recommendations; benchmark results and production traffic are never fabricated. Benchmark output, profiles, traces, resource metrics, and architecture context can be supplied as supporting evidence, but they are optional.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/agents/performance_engineer.md` — For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

### Codex

**Manually: put the files in place**
- File: `.codex/agents/performance_engineer.toml` — Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

### Cursor

**Manually: put the files in place**
- File: `.cursor/agents/performance_engineer.md` — Cursor also reads .claude/agents/

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/AgenticOrgLab/ExecOrchestra/tree/HEAD/execorchestra/Pool/resources/agents/performance_engineer.md

## When to use it
- locate API bottlenecks from measurements
- rank experiments for a latency target
- assess optimization trade-offs across CPU and memory
- define acceptance thresholds and regression checks

## Example prompts
- Analyze these API performance measurements and create an optimization plan with baselines and regression checks.
- Write a database performance report from these profiles and traces.
- Compare the measured workload with the latency budget and rank the next experiments.

## Similar
- [backend-development-performance-engineer](https://affpapa.org/en/nevibecode/agents/backend-development-performance-engineer.md) — subagent · ★ 42780 repo stars
- [performance-engineer](https://affpapa.org/en/nevibecode/agents/performance-engineer.md) — subagent · 671 installs
- [performance-optimizer](https://affpapa.org/en/nevibecode/skills/performance-optimizer.md) — skill · 70 installs
- [performance-budget-setter](https://affpapa.org/en/nevibecode/skills/performance-budget-setter.md) — skill · 228 installs
- [performance-expert](https://affpapa.org/en/nevibecode/skills/performance-expert.md) — skill · 198 installs
- [go-performance-review](https://affpapa.org/en/nevibecode/skills/go-performance-review.md) — skill · ★ 90 repo stars

From the same set: [agenticorglab/execorchestra](https://affpapa.org/en/nevibecode/by/agenticorglab/execorchestra.md) — 24 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
