shipshitdev/performance-expert
bundles/infrastructure/skills/performance-expert/SKILL.md
Backend, database, and infrastructure performance expert covering API response times, query and index optimization, N+1 elimination, caching and background jobs, server profiling, and build/asset delivery. Use when improving API latency, optimizing database queries or indexes, designing a caching layer, moving heavy work to a queue, profiling a server process, shrinking a shipped bundle, or configuring CDN and edge caching. React render and component work belongs to `react-component-performance`.
$ install --global
skillsauthnpx skillsauth add shipshitdev/library performance-expertInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Aug 20, 2026, 3:15 AM24.4s3 files scanned
SKILL.md
- name:
- performance-expert
- description:
- >-
- version:
- 1.1.0
- tags:
- performance, optimization, backend, database, infrastructure
- when_to_use:
- slow API endpoint, high p95 latency, slow database query, missing index, N+1 queries, add caching, Redis cache strategy, move work to a background job, profile the server, connection pooling, bundle size too large, CDN and cache headers, cold starts, load testing
Performance Expert Skill
Backend, database, and infrastructure performance. This skill owns the server-side and delivery-layer of a stack: request latency, data access, caching, background work, and what ships over the wire.
Render-time work inside React components — re-renders, memoization,
virtualized lists, Profiler traces — is a different diagnosis with different
tooling. Route it to react-component-performance instead of duplicating it
here.
Contract
Inputs:
- A performance symptom with a surface: an endpoint, a query, a job, a build output, or a metric that regressed.
Outputs:
- A ranked list of bottlenecks with the measurement that proves each one, plus a targeted fix per bottleneck.
Creates/Modifies:
- None on its own. It diagnoses and prescribes; edits happen in the caller's workflow.
External Side Effects:
- None. Profiling and load-testing commands are prescribed, not executed unattended.
Delegates To:
react-component-performancefor React render hotspots, re-render churn, memoization, and Profiler-driven component work.workspace-performance-auditwhen the target is a whole monorepo rather than one surface.
When to Use
- Improving API response times
- Optimizing database queries, indexes, and aggregation pipelines
- Diagnosing N+1 query patterns
- Implementing caching strategies and invalidation
- Moving heavy work into background jobs or queues
- Profiling a server process or tracing a slow request
- Analyzing shipped bundle size and asset delivery
- Configuring CDN, cache headers, or edge caching
Project Context Discovery
- Check
.agents/memory/for performance architecture context (e.g., any*performance*or*architecture*files) - Identify performance tools (APM, load-testing harness, profiler)
- Review existing optimizations and caching strategies
- Check for
[project]-performance-expertskill
Core Performance Principles
Backend
API Response Times: Target < 200ms (p95), caching, background jobs, connection pooling
Query Optimization: Indexes, projections, pagination, optimized aggregations
Background Processing: Queues for heavy operations, async for non-critical tasks, no blocking work in request handlers
Database
Indexes: On frequently queried fields, compound indexes, monitor usage
Queries: Filter early, project before expensive stages, sort with indexes, avoid full scans
Infrastructure
CDN: Edge caching, correct cache headers, static assets off the origin
Serverless: Cold start optimization, memory allocation, provisioned concurrency
Delivery Layer
Bundles: Code splitting by route, dynamic imports for heavy modules, tree shaking, drop unused dependencies
Assets: WebP images, subset fonts, minify CSS/JS, Gzip/Brotli compression
Server rendering: Static generation for static content, incremental revalidation, framework image and font pipelines
Performance Metrics
Backend
- API p50: < 100ms
- API p95: < 200ms
- DB Query p95: < 50ms
- Error Rate: < 0.1%
Delivery
- LCP: < 2.5s
- TTFB: < 800ms
- Initial bundle: < 200KB
Quick Checklist
Backend
- [ ] Database queries optimized
- [ ] Indexes created and used
- [ ] Caching implemented
- [ ] Background jobs for heavy operations
- [ ] Connection pooling configured
Delivery
- [ ] Bundle size < 200KB initial
- [ ] Code splitting implemented
- [ ] Images optimized and lazy loaded
- [ ] Compression and cache headers configured
For database query optimization code, caching strategy implementation, N+1 query solutions, background-job patterns, infrastructure tuning, performance testing commands, and detailed checklists, see: references/full-guide.md
Related Skills
shipshitdev/weekly-review
development
VerifiedTrustedCommunity
Coordinates a weekly engineering review of board accuracy, recent code changes, operational health, and scoped cleanup. Use for a recurring repository health review or a review of the last several days.
35SKILL.mdUpdated Sep 6, 2026
shipshitdev/project-board
testing
VerifiedTrustedCommunity
Audits project board configuration and prepares explicitly requested setup, copy, or normalization changes while preserving the existing workflow and provider boundaries. Use when inspecting a board's fields, columns, scope, or configuration.
35SKILL.mdUpdated Sep 6, 2026
shipshitdev/board-sync
testing
VerifiedTrustedCommunity
Reconciles a project board with current work and delivery evidence, reports incomplete coverage and metadata gaps, and applies only approved provider-supported field changes. Use when auditing board drift, reviewing blocked work, or assessing upcoming delivery.
35SKILL.mdUpdated Sep 6, 2026
shipshitdev/how
development
VerifiedTrustedCommunity
Walk through how a subsystem works. Use for "how does X work", code walkthroughs before changing something, and placement or ownership questions. Explains architecture, runtime flow, and onboarding mental models. Can critique architecture. Use why for motivation.
35SKILL.mdUpdated Aug 31, 2026