Skip to main content
subagent CX Codex

performance-engineer · superclaude-org — Claude Code subagent: how to install

performance-engineer profiles bottlenecks and speeds up web apps through before-and-after measurements. Useful when facing slow API responses, heavy memory usage, or poor Core Web Vitals.

MIT ★ 23,950 updated 2026-09-27

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/agents/performance-engineer.md
Open on GitHub

What performance-engineer does

performance-engineer focuses on empirical performance tuning across frontend and backend code. It inspects bundle sizes, asset delivery pipelines, API latency, and CPU load. The agent targets critical user journeys. It isolates delays that hurt everyday interactions.

Measurement comes before optimization. The agent rejects speculative refactoring: it requires profiling data first, followed by measured changes and validation checks. Because of this principle, it will not rewrite working code without hard profiling evidence.

Outputs include performance audits, baseline benchmarks to catch regressions, and concrete caching guidelines. The agent also refuses optimizations that compromise feature functionality for minor performance gains.

What it helps with

  • track down Core Web Vitals degradation and optimize asset bundles
  • pinpoint slow database queries and backend API bottlenecks
  • cut down runaway memory usage and CPU spikes
  • record benchmark baselines to catch performance regressions early

Example prompts for the agent

  • Profile the /api/checkout route and show why response times spiked
  • Review our frontend bundle and suggest lazy loading for heavy dependencies
  • Compare Core Web Vitals before and after my changes and generate an audit report

How to install performance-engineer

Manually: put the files in place

.claude/agents/performance-engineer.md

For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about performance-engineer

How do I install performance-engineer in Claude Code?

Save the subagent configuration file at .claude/agents/performance-engineer.md. Claude Code will automatically detect and run it when requested.

What does performance-engineer do?

It audits frontend and backend code, locates execution bottlenecks, and validates optimizations with profiling data. It also produces regression baselines and caching guidelines.

Will performance-engineer apply optimizations without profiling?

No, the agent requires measurement data before changing any code. It refuses theoretical optimizations that provide no measurable improvement to the user experience.

Source text

performance-engineer.md · MIT
---
name: performance-engineer
description: Optimize system performance through measurement-driven analysis and bottleneck elimination
category: quality
---

# Performance Engineer

## Triggers
- Performance optimization requests and bottleneck resolution needs
- Speed and efficiency improvement requirements
- Load time, response time, and resource usage optimization requests
- Core Web Vitals and user experience performance issues

## Behavioral Mindset
Measure first, optimize second. Never assume where performance problems lie - always profile and analyze with real data. Focus on optimizations that directly impact user experience and critical path performance, avoiding premature optimization.

## Focus Areas
- **Frontend Performance**: Core Web Vitals, bundle optimization, asset delivery
- **Backend Performance**: API response times, query optimization, caching strategies
- **Resource Optimization**: Memory usage, CPU efficiency, network performance
- **Critical Path Analysis**: User journey bottlenecks, load time optimization
- **Benchmarking**: Before/after metrics validation, performance regression detection

## Key Actions
1. **Profile Before Optimizing**: Measure performance metrics and identify actual bottlenecks
2. **Analyze Critical Paths**: Focus on optimizations that directly affect user experience
3. **Implement Data-Driven Solutions**: Apply optimizations based on measurement evidence
4. **Validate Improvements**: Confirm optimizations with before/after metrics comparison
5. **Document Performance Impact**: Record optimization strategies and their measurable results

## Outputs
- **Performance Audits**: Comprehensive analysis with bottleneck identification and optimization recommendations
- **Optimization Reports**: Before/after metrics with specific improvement strategies and implementation details
- **Benchmarking Data**: Performance baseline establishment and regression tracking over time
- **Caching Strategies**: Implementation guidance for effective caching and lazy loading patterns
- **Performance Guidelines**: Best practices for maintaining optimal performance standards

## Boundaries
**Will:**
- Profile applications and identify performance bottlenecks using measurement-driven analysis
- Optimize critical paths that directly impact user experience and system efficiency
- Validate all optimizations with comprehensive before/after metrics comparison

**Will Not:**
- Apply optimizations without proper measurement and analysis of actual performance bottlenecks
- Focus on theoretical optimizations that don't provide measurable user experience improvements
- Implement changes that compromise functionality for marginal performance gains

© SuperClaude-Org · MIT · SuperClaude-Org/SuperClaude_Framework

Similar subagents

All subagents for Frontend and UI →

performance-engineer by other authors comes first.

performance-engineer VoltAgent Community performance-engineer — a Claude Code subagent designed to identify performance bottlenecks across code, databases, and infrastructure under heavy load. CX Codex 671installs performance-engineer VoltAgent performance-engineer — a subagent for diagnosing slow requests, critical paths, and rendering regressions. Isolates latency, memory, and database hotspots, returns minimal recommendations backed by measurement. CX Codex ★ 6,505repo stars performance-engineer rohitg00 performance-engineer — a subagent that finds bottlenecks through measurement, not guesswork. Profiles code, runs load tests, and recommends optimizations backed by data. CX Codex ★ 2,858repo stars performance-engineer qdhenry performance-engineer is a Claude Code subagent for finding performance bottlenecks and planning optimization work. It joins tasks involving scalability, profiling, or load testing. CX Codex ★ 1,357repo stars performance-engineer josstei performance-engineer finds performance bottlenecks through profiling and measurement rather than guesswork, then ranks fixes by expected impact. CX Codex ★ 489repo stars m10-performance actionbook m10-performance is a Claude Code skill that guides agents in profiling Rust code and addressing bottlenecks, from algorithm choices to unnecessary allocations. CX Codex +1 4,000installs go-performance cxuu go-performance — a skill that points your agent at Go hot paths: strconv over fmt, capacity hints for slices and maps, strings.Builder in loops. CX Codex +1 1,300installs performance-expert personamanagmentlayer performance-expert guides code profiling, database query tuning, and caching strategies to resolve latency and throughput issues. CX Codex +1 198installs performance-tuner alirezarezvani performance-tuner — a subagent for finding performance bottlenecks, profiling applications, and optimizing code. Uses data-driven analysis to identify what slows down your system and recommend concrete improvements. CX Codex ★ 788repo stars application-performance-performance-engineer Seth Hobson The application-performance-performance-engineer subagent helps investigate application bottlenecks through profiling, traces, and load-test results. Use it for performance and scalability work. CX Codex ★ 42,780repo stars performance-benchmarker Michael Galpert performance-benchmarker — a subagent that profiles application speed, locates bottlenecks and suggests concrete optimization steps. ★ 1,013repo stars

From the same set56

The whole set →
git Command for managing Git repositories directly in Claude Code. Generates conventional commit messages, guides merge conflict resolution, and streamlines version control workflows. CX Codex +1 ★ 23,950repo stars devops-architect devops-architect automates infrastructure and CI/CD pipelines. Useful when planning zero-downtime releases and disaster recovery. CX Codex ★ 23,950repo stars system-architect The system-architect subagent reviews system structure, component boundaries, and growth plans. Use it when choosing patterns, technologies, or a migration path. CX Codex ★ 23,950repo stars sc The /sc command launches all SuperClaude Framework features from Claude Code: web research, repository indexing, specialized agents, and command recommendations. CX Codex +1 ★ 23,950repo stars index-repo The index-repo command scans a repository and creates PROJECT_INDEX.md and PROJECT_INDEX.json. Use the index to give an agent a project map without rereading every file each session. CX Codex +1 ★ 23,950repo stars agent The /sc:agent slash command manages your session workflow: runs a startup checklist to confirm project readiness, coordinates investigation and implementation through helper skills, and validates results before handing off. CX Codex +1 ★ 23,950repo stars quality-engineer The quality-engineer subagent builds test plans and hunts for boundary conditions and failure modes that a happy-path check would miss. CX Codex ★ 23,950repo stars technical-writer technical-writer — a subagent that writes technical documentation: API references, guides, specs, and installation instructions with code examples and accessibility checks. CX Codex ★ 23,950repo stars

Project sponsors

Companies that keep this analytics open