Skip to content
Skillv1.0.0

performance-expert

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 deli

by shipshitdev(0) 0 installs
Free
Sign in to install

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Imported from shipshitdev/skills (skills/performance-expert/SKILL.md). Install upstream with npx skills add shipshitdev/skills --skill performance-expert. Copyright stays with the author.

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-performance for React render hotspots, re-render churn, memoization, and Profiler-driven component work.
  • workspace-performance-audit when 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

  1. Check .agents/memory/ for performance architecture context (e.g., any *performance* or *architecture* files)
  2. Identify performance tools (APM, load-testing harness, profiler)
  3. Review existing optimizations and caching strategies
  4. Check for [project]-performance-expert skill

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

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

yaml
targets:
  - https://api.opensmartroute.ai/api/v1/registry/shipshitdev-skills-performance-expert/manifest   # or paste the manifest below

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

shipshitdev-skills-performance-expert.ocm.jsonjson
{
  "ocm": "1",
  "id": "shipshitdev-skills-performance-expert",
  "kind": "skill",
  "name": "performance-expert",
  "description": "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`.",
  "publisher": "shipshitdev",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "coding",
      "customer_support"
    ],
    "tags": [
      "skill-md",
      "performance",
      "optimization",
      "backend",
      "database",
      "infrastructure",
      "skills-sh"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "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`."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "skills.sh",
      "repository": "https://github.com/shipshitdev/skills",
      "path": "skills/performance-expert/SKILL.md",
      "ref": "HEAD",
      "url": "https://github.com/shipshitdev/skills/blob/HEAD/skills/performance-expert/SKILL.md",
      "key": "shipshitdev/skills/skills/performance-expert/SKILL.md"
    }
  },
  "instructions": "# Performance Expert Skill\n\nBackend, database, and infrastructure performance. This skill owns the\nserver-side and delivery-layer of a stack: request latency, data access,\ncaching, background work, and what ships over the wire.\n\nRender-time work inside React components — re-renders, memoization,\nvirtualized lists, Profiler traces — is a different diagnosis with different\ntooling. Route it to `react-component-performance` instead of duplicating it\nhere.\n\n## Contract\n\nInputs:\n\n- A performance symptom with a surface: an endpoint, a query, a job, a build\n  output, or a metric that regressed.\n\nOutp",
  "cost": {
    "context_tokens": 944
  }
}

Fetch it by URL: GET /api/v1/registry/shipshitdev-skills-performance-expert/manifest?version=1.0.0

Reviews

Star ratings from people who tried it. One review per account; edit yours any time.

No reviews yet. Install it, try it, and be the first to rate it.