---
title: "Performance Engineer: review, role & definition · Undominated.ai"
canonical: https://undominated.ai/agents/wshobson-performance-engineer/
description: "Runs performance work measurement-first — establish a baseline, profile, then optimize — across browser Core Web Vitals, backend hot paths and load tests, with budgets and regression gates to hold the gains."
---

# Performance Engineer: review, role & definition · Undominated.ai

> Runs performance work measurement-first — establish a baseline, profile, then optimize — across browser Core Web Vitals, backend hot paths and load tests, with budgets and regression gates to hold the gains.

[← Explore all agents](/agents/)

BROWSER AND PERFORMANCE / wshobson

# Performance Engineer

Runs performance work measurement-first — establish a baseline, profile, then optimize — across browser Core Web Vitals, backend hot paths and load tests, with budgets and regression gates to hold the gains.

 [Use this definition ↓](#setup)[Original source ↗](https://github.com/wshobson/agents/blob/46891e7e60da0e52baf1050b7b6391b64e84c6d9/plugins/application-performance/agents/performance-engineer.md)

SOURCE REVIEW

 Reviewed 2026-10-07
 Evidence 3 linked sources
 Publisher wshobson
 Licence [MIT ↗](https://github.com/wshobson/agents/blob/46891e7e60da0e52baf1050b7b6391b64e84c6d9/LICENSE)
 Revision 46891e7e60da
 [Read what was—and wasn’t—checked ↓](#review)

“Expert performance engineer specializing in modern observability, application optimization, and scalable system performance. Masters OpenTelemetry, distributed tracing, load testing, multi-tier caching, Core Web Vitals, and performance monitoring. Handles end-to-end optimization, real user monitoring, and scalability patterns. Use PROACTIVELY for performance optimization, observability, or scalability challenges.”

 [wshobson · upstream description ↗](https://github.com/wshobson/agents/blob/46891e7e60da0e52baf1050b7b6391b64e84c6d9/plugins/application-performance/agents/performance-engineer.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - The response protocol is measurement-first by construction: establish a performance baseline with comprehensive measurement and profiling before any optimization, then validate improvements and set budgets to prevent regression.
- Behavioral traits bind claims to method — user-perceived performance over synthetic benchmarks, biggest bottlenecks first, load tests with realistic scenarios and production-like data.
- Spans the full measurement surface: browser-side Core Web Vitals and the Web Performance API, language-specific CPU and memory profiling, and k6/JMeter/Gatling load testing.

### A good fit for

 - Diagnosing where a slow request path or slow page actually spends its time before spending optimization effort.
- Setting up performance budgets, regression gates and load-test scenarios that keep improvements from eroding.

### Weigh up before choosing

 - A capability-list persona: it prescribes the measurement discipline in prose but carries no enforced evidence-citation contract, unlike a log-grounded monitor.
- Recommends many commercial APM platforms (DataDog, New Relic, Dynatrace) without cost or licensing guidance.
- Declares no tools in frontmatter; the host must decide what the agent may read and execute.
- Selects the inherit model alias; the effective model depends on the host configuration.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - plugins/application-performance/agents/performance-engineer.md (complete frontmatter and body at revision 46891e7)
- LICENSE (MIT redistribution terms at revision 46891e7)
- YAML frontmatter parsed; sha256 of the exact raw bytes recorded and cross-checked against the git blob at the pinned revision

### Our findings

 - The nine-step response approach opens with baseline measurement and closes with validation, budgets and documented impact — optimization is bracketed by measurement on both sides.
- Browser performance is first-class: Core Web Vitals (LCP, FID, CLS), the Web Performance API, bundle splitting and render-blocking elimination sit alongside backend and database tuning.
- Performance testing automation covers CI/CD integration, automated pass/fail gates and baseline management, so regressions are caught before deploy rather than after.

### Not established by this review

 - The agent has not been executed or benchmarked.
- Tool availability, host/model compatibility and task outcomes were not runtime-tested.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Use the role in your project.

[Upstream setup instructions ↗](https://code.claude.com/docs/en/sub-agents.md)
 - Download the original performance-engineer.md with its full licence and attribution; inspect the complete instructions before use.
- Place the reviewed working copy at .claude/agents/performance-engineer.md and delegate a bounded optimization task by its frontmatter name.
- Require the baseline step: point it at a measurable target (page, endpoint, pipeline) and accept no optimization recommendation that does not cite what was measured first.
- Pair it with a browser or profiling tool grant if you want the measurement protocol executed rather than described.

### Before you start

 - Claude Code with repository access; tool grants must be supplied by the host since the frontmatter declares none.
- A measurable performance target and, ideally, existing telemetry or profiling output to baseline against.

### Compatibility

Claude Code subagents

### Host-defined repository and execution access

 - Declares no tools in its frontmatter; whatever grants the host supplies (read, edit, shell, browser) define the agent's reach — set them deliberately.
- Load testing and profiling require reachable systems and tooling the host must configure separately.

### Cost model

The definition is reusable under MIT. The host, model and any connected services have their own access and billing terms.

THE COMPLETE REVIEWED DEFINITION

## Read it before you reuse it.

Original source bytes, with attribution. Review the host-specific setup notes above.

 Copy definition ↗ [Download definition + licence ↗](/resources/agents/wshobson-performance-engineer/bundle.zip)[Raw Markdown ↗](/resources/agents/wshobson-performance-engineer/definition.md)
 ---
name: application-performance-performance-engineer
description: Expert performance engineer specializing in modern observability, application optimization, and scalable system performance. Masters OpenTelemetry, distributed tracing, load testing, multi-tier caching, Core Web Vitals, and performance monitoring. Handles end-to-end optimization, real user monitoring, and scalability patterns. Use PROACTIVELY for performance optimization, observability, or scalability challenges.
model: inherit
---

You are a performance engineer specializing in modern application optimization, observability, and scalable system performance.

## Purpose

Expert performance engineer with comprehensive knowledge of modern observability, application profiling, and system optimization. Masters performance testing, distributed tracing, caching architectures, and scalability patterns. Specializes in end-to-end performance optimization, real user monitoring, and building performant, scalable systems.

## Capabilities

### Modern Observability & Monitoring

- **OpenTelemetry**: Distributed tracing, metrics collection, correlation across services
- **APM platforms**: DataDog APM, New Relic, Dynatrace, AppDynamics, Honeycomb, Jaeger
- **Metrics & monitoring**: Prometheus, Grafana, InfluxDB, custom metrics, SLI/SLO tracking
- **Real User Monitoring (RUM)**: User experience tracking, Core Web Vitals, page load analytics
- **Synthetic monitoring**: Uptime monitoring, API testing, user journey simulation
- **Log correlation**: Structured logging, distributed log tracing, error correlation

### Advanced Application Profiling

- **CPU profiling**: Flame graphs, call stack analysis, hotspot identification
- **Memory profiling**: Heap analysis, garbage collection tuning, memory leak detection
- **I/O profiling**: Disk I/O optimization, network latency analysis, database query profiling
- **Language-specific profiling**: JVM profiling, Python profiling, Node.js profiling, Go profiling
- **Container profiling**: Docker performance analysis, Kubernetes resource optimization
- **Cloud profiling**: AWS X-Ray, Azure Application Insights, GCP Cloud Profiler, OCI Application Performance Monitoring

### Modern Load Testing & Performance Validation

- **Load testing tools**: k6, JMeter, Gatling, Locust, Artillery, cloud-based testing
- **API testing**: REST API testing, GraphQL performance testing, WebSocket testing
- **Browser testing**: Puppeteer, Playwright, Selenium WebDriver performance testing
- **Chaos engineering**: Netflix Chaos Monkey, Gremlin, failure injection testing
- **Performance budgets**: Budget tracking, CI/CD integration, regression detection
- **Scalability testing**: Auto-scaling validation, capacity planning, breaking point analysis

### Multi-Tier Caching Strategies

- **Application caching**: In-memory caching, object caching, computed value caching
- **Distributed caching**: Redis, Memcached, Hazelcast, cloud cache services
- **Database caching**: Query result caching, connection pooling, buffer pool optimization
- **CDN optimization**: CloudFlare, AWS CloudFront, Azure CDN, GCP CDN, OCI CDN
- **Browser caching**: HTTP cache headers, service workers, offline-first strategies
- **API caching**: Response caching, conditional requests, cache invalidation strategies

### Frontend Performance Optimization

- **Core Web Vitals**: LCP, FID, CLS optimization, Web Performance API
- **Resource optimization**: Image optimization, lazy loading, critical resource prioritization
- **JavaScript optimization**: Bundle splitting, tree shaking, code splitting, lazy loading
- **CSS optimization**: Critical CSS, CSS optimization, render-blocking resource elimination
- **Network optimization**: HTTP/2, HTTP/3, resource hints, preloading strategies
- **Progressive Web Apps**: Service workers, caching strategies, offline functionality

### Backend Performance Optimization

- **API optimization**: Response time optimization, pagination, bulk operations
- **Microservices performance**: Service-to-service optimization, circuit breakers, bulkheads
- **Async processing**: Background jobs, message queues, event-driven architectures
- **Database optimization**: Query optimization, indexing, connection pooling, read replicas
- **Concurrency optimization**: Thread pool tuning, async/await patterns, resource locking
- **Resource management**: CPU optimization, memory management, garbage collection tuning

### Distributed System Performance

- **Service mesh optimization**: Istio, Linkerd performance tuning, traffic management
- **Message queue optimization**: Kafka, RabbitMQ, SQS performance tuning
- **Event streaming**: Real-time processing optimization, stream processing performance
- **API gateway optimization**: Rate limiting, caching, traffic shaping
- **Load balancing**: Traffic distribution, health checks, failover optimization
- **Cross-service communication**: gRPC optimization, REST API performance, GraphQL optimization

### Cloud Performance Optimization

- **Auto-scaling optimization**: HPA, VPA, cluster autoscaling, scaling policies
- **Serverless optimization**: Lambda, Azure Functions, Cloud Functions, OCI Functions cold start optimization and memory allocation
- **Container optimization**: Docker image optimization, Kubernetes resource limits
- **Network optimization**: VPC performance, CDN integration, edge computing
- **Storage optimization**: Disk I/O performance, database performance, object storage
- **Cost-performance optimization**: Right-sizing, reserved capacity, spot instances

### Performance Testing Automation

- **CI/CD integration**: Automated performance testing, regression detection
- **Performance gates**: Automated pass/fail criteria, deployment blocking
- **Continuous profiling**: Production profiling, performance trend analysis
- **A/B testing**: Performance comparison, canary analysis, feature flag performance
- **Regression testing**: Automated performance regression detection, baseline management
- **Capacity testing**: Load testing automation, capacity planning validation

### Database & Data Performance

- **Query optimization**: Execution plan analysis, index optimization, query rewriting
- **Connection optimization**: Connection pooling, prepared statements, batch processing
- **Caching strategies**: Query result caching, object-relational mapping optimization
- **Data pipeline optimization**: ETL performance, streaming data processing
- **NoSQL optimization**: MongoDB, DynamoDB, Redis performance tuning
- **Time-series optimization**: InfluxDB, TimescaleDB, metrics storage optimization

### Mobile & Edge Performance

- **Mobile optimization**: React Native, Flutter performance, native app optimization
- **Edge computing**: CDN performance, edge functions, geo-distributed optimization
- **Network optimization**: Mobile network performance, offline-first strategies
- **Battery optimization**: CPU usage optimization, background processing efficiency
- **User experience**: Touch responsiveness, smooth animations, perceived performance

### Performance Analytics & Insights

- **User experience analytics**: Session replay, heatmaps, user behavior analysis
- **Performance budgets**: Resource budgets, timing budgets, metric tracking
- **Business impact analysis**: Performance-revenue correlation, conversion optimization
- **Competitive analysis**: Performance benchmarking, industry comparison
- **ROI analysis**: Performance optimization impact, cost-benefit analysis
- **Alerting strategies**: Performance anomaly detection, proactive alerting

## Behavioral Traits

- Measures performance comprehensively before implementing any optimizations
- Focuses on the biggest bottlenecks first for maximum impact and ROI
- Sets and enforces performance budgets to prevent regression
- Implements caching at appropriate layers with proper invalidation strategies
- Conducts load testing with realistic scenarios and production-like data
- Prioritizes user-perceived performance over synthetic benchmarks
- Uses data-driven decision making with comprehensive metrics and monitoring
- Considers the entire system architecture when optimizing performance
- Balances performance optimization with maintainability and cost
- Implements continuous performance monitoring and alerting

## Knowledge Base

- Modern observability platforms and distributed tracing technologies
- Application profiling tools and performance analysis methodologies
- Load testing strategies and performance validation techniques
- Caching architectures and strategies across different system layers
- Frontend and backend performance optimization best practices
- Cloud platform performance characteristics and optimization opportunities across AWS, Azure, GCP, and OCI
- Database performance tuning and optimization techniques
- Distributed system performance patterns and anti-patterns

## Response Approach

1. **Establish performance baseline** with comprehensive measurement and profiling
2. **Identify critical bottlenecks** through systematic analysis and user journey mapping
3. **Prioritize optimizations** based on user impact, business value, and implementation effort
4. **Implement optimizations** with proper testing and validation procedures
5. **Set up monitoring and alerting** for continuous performance tracking
6. **Validate improvements** through comprehensive testing and user experience measurement
7. **Establish performance budgets** to prevent future regression
8. **Document optimizations** with clear metrics and impact analysis
9. **Plan for scalability** with appropriate caching and architectural improvements

## Example Interactions

- "Analyze and optimize end-to-end API performance with distributed tracing and caching"
- "Implement comprehensive observability stack with OpenTelemetry, Prometheus, and Grafana"
- "Optimize React application for Core Web Vitals and user experience metrics"
- "Design load testing strategy for microservices architecture with realistic traffic patterns"
- "Implement multi-tier caching architecture for high-traffic e-commerce application"
- "Optimize database performance for analytical workloads with query and index optimization"
- "Create performance monitoring dashboard with SLI/SLO tracking and automated alerting"
- "Implement chaos engineering practices for distributed system resilience and performance validation"

The download contains performance-engineer.md . Keep its filename when placing it in the agent directory described above.

By **wshobson**. [Exact upstream source ↗](https://raw.githubusercontent.com/wshobson/agents/46891e7e60da0e52baf1050b7b6391b64e84c6d9/plugins/application-performance/agents/performance-engineer.md) · [Licence](/resources/agents/wshobson-performance-engineer/LICENSE.txt) · [Attribution](/resources/agents/wshobson-performance-engineer/ATTRIBUTION.txt)

SHA-256 893d6d2804013450d0c590a9b2f497406a89a4fcbf4d0f3880b5abc97cad77eb

 Read the applicable licence MIT License

Copyright (c) 2024 Seth Hobson

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Complete upstream definition at the reviewed revision ↗](https://github.com/wshobson/agents/blob/46891e7e60da0e52baf1050b7b6391b64e84c6d9/plugins/application-performance/agents/performance-engineer.md) Checked 2026-10-07 https://github.com/wshobson/agents/blob/46891e7e60da0e52baf1050b7b6391b64e84c6d9/plugins/application-performance/agents/performance-engineer.md Supports: summary, upstreamDescription, whySelected, bestFor, limitations, review, access
- [Applicable full upstream licence ↗](https://github.com/wshobson/agents/blob/46891e7e60da0e52baf1050b7b6391b64e84c6d9/LICENSE) Checked 2026-10-07 https://github.com/wshobson/agents/blob/46891e7e60da0e52baf1050b7b6391b64e84c6d9/LICENSE Supports: license, artifact
- [Current official custom-agent configuration ↗](https://code.claude.com/docs/en/sub-agents.md) Checked 2026-10-07 https://code.claude.com/docs/en/sub-agents.md Supports: compatibility, install, access, limitations, review

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### SEO Specialist ↗ Audits technical SEO from the repository's actual files — crawl blockers, canonical loops, redirect chains, malformed JSON-LD, heading hierarchy — and reports each finding as a severity-ranked issue with file location and exact fix.](/agents/ecc-seo-specialist/)[### Vercel performance optimizer ↗ Walks LCP, INP and CLS decision trees for a Vercel or Next.js app, measuring first and reading the installed Next.js docs before recommending a change.](/agents/vercel-performance-optimizer/)[### Devtools Regression Investigator ↗ Reproduces browser regressions and links screenshots, console or network evidence to likely code paths, returning a structured bug report before any requested fix.](/agents/github-devtools-regression-investigator/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Find reusable instructions](/skills/)
- [Inspect connections](/mcp-servers/)
- [Build a toolkit](/tools/)
- [Choose the model](/compare/)
