Skip to main content
prompt GP ChatGPT

Load Testing taste — ChatGPT prompt: what it does, how to install

The Load Testing taste prompt for ChatGPT sets performance testing standards and reliability engineering principles. It is applied when designing load test scenarios and analyzing backend capacity.

CC0-1.0 ★ 178,201 updated 2026-10-24

Open on GitHub

What Load Testing taste does

The prompt outlines a structured approach to performance testing focused on explicit latency and throughput goals. It covers writing load tests as code using k6, Gatling, or Locust alongside the service repository, modeling production traffic mixes, and running open workload models for internet-facing systems.

The guidelines detail running distinct test types including smoke, load, stress, spike, and soak tests, as well as reporting latencies through p50, p95, and p99 percentiles. It emphasizes setting pass or fail thresholds directly in test scripts for CI pipelines, isolating rate-limited APIs, and correlating server-side traces with client metrics.

To use the prompt in Claude Code, place the file .claude/commands/prompts.csv.md in the workspace. Effective testing requires a staging environment matching production instance sizes and data cardinality.

What it helps with

  • define performance goals and latency thresholds
  • write load tests as code using k6 or Locust
  • model realistic traffic mixtures from production logs
  • set automated pass or fail thresholds for CI builds
  • analyze latency percentiles including p50, p95 and p99

Example prompts for the agent

  • Apply these load testing taste guidelines to our test suite
  • Help me design a k6 load test script based on these performance standards
  • Review our load testing strategy for production readiness

How to install Load Testing taste

How to use

Paste the text at the start of a chat or into project instructions

Questions about Load Testing taste

How to install Load Testing taste in Claude Code?

To install Load Testing taste, add the file .claude/commands/prompts.csv.md to your project.

What does Load Testing taste do?

It provides engineering standards and rules for load testing, covering percentile reporting, traffic modeling, test environments, and bottleneck analysis.

What is needed to use Load Testing taste?

Executing the testing strategies requires a production-like staging environment and load generation tools such as k6, Gatling, or Locust.

Source text

prompts.csv · CC0-1.0
# Load Testing taste of a performance-minded reliability engineer
- Start every load test from a written goal, such as p95 latency under 300 ms at 500 requests per second, not from a vague "see what breaks". Confidence: 0.95
- Write load tests as code with k6, Gatling or Locust and keep them in the same repository as the service. Confidence: 0.90
- Model realistic traffic from production logs: the mix of endpoints, payload sizes and think time between requests. Confidence: 0.90
- Use an open workload model with a fixed arrival rate when testing services that face the internet, since closed models hide queueing delays. Confidence: 0.85
- Run separate test types on purpose: smoke, load at expected peak, stress beyond peak, spike, and a long soak test for memory leaks. Confidence: 0.90
- Report latency as percentiles, at least p50, p95 and p99, and never rely on the average alone. Confidence: 0.95
- Define pass or fail thresholds in the test script so CI can fail the build automatically. Confidence: 0.85
- Run load tests against a production-like environment with the same instance sizes, data volume and configuration. Confidence: 0.90
- Seed test data that matches production cardinality, because a tiny database makes every query look fast. Confidence: 0.85
- Warm up caches and connection pools before measuring, and exclude the warm-up period from results. Confidence: 0.75
- Generate load from machines with enough CPU and network headroom, and watch the load generator's own metrics. Confidence: 0.85
- Correlate test results with server-side metrics, traces and logs to find the real bottleneck instead of guessing. Confidence: 0.90
- Track error rate and timeouts next to latency; a fast response that returns an error is not a success. Confidence: 0.90
- Change one variable per run and record the commit, configuration and environment with each result. Confidence: 0.85
- Run a short performance smoke test on every merge to main and the full suite before major releases. Confidence: 0.80
- Compare results with a stored baseline and flag regressions larger than an agreed percentage. Confidence: 0.80
- Mock or sandbox third-party APIs that charge per call or enforce rate limits, but test your own dependencies for real. Confidence: 0.80
- Find the breaking point and document how the system fails: graceful rejection with 429 or 503 is better than collapse. Confidence: 0.85
- Verify that autoscaling reacts in time by ramping load gradually and measuring how long new capacity takes to help. Confidence: 0.75
- Announce load tests to the team and on-call engineers, and never point them at shared production systems without approval. Confidence: 0.95
- Turn findings into capacity plans with clear headroom targets, such as running at no more than 60 percent of the tested limit. Confidence: 0.70

© f · CC0-1.0 · f/prompts.chat

Similar prompts

All prompts for Testing and QA →

From the same set218

The whole set →
Cloudflare Worker taste Cloudflare Worker taste — a prompt for ChatGPT and Claude.ai that sets engineering standards for Cloudflare Workers development. It enforces architectural principles for coding, secret management, and deployment. GP ChatGPT ★ 178,201repo stars Playwright E2E taste The Playwright E2E taste prompt for ChatGPT sets conventions for Playwright end-to-end tests. It covers core user journeys and test isolation, from local runs to CI. GP ChatGPT ★ 178,201repo stars Next.js App taste Next.js App taste — a prompt for ChatGPT and Claude.ai that enforces pragmatic Next.js App Router conventions. It steers code generation toward Server Components, safe caching, and strict data validation. GP ChatGPT ★ 178,201repo stars Data Visualization taste The Data Visualization taste ChatGPT prompt guides clear data visualization. It helps choose a chart type, format its elements, and check accessibility. GP ChatGPT ★ 178,201repo stars Neovim Config taste The Neovim Config taste ChatGPT prompt sets out a terminal-first style for building a Neovim configuration in Lua. It covers plugin loading, language tools, formatting, and key bindings. GP ChatGPT ★ 178,201repo stars API Client SDK taste API Client SDK taste — a prompt for ChatGPT that defines developer-experience standards for building API client SDKs. It runs during API architecture design, OpenAPI code generation, and error-handling setup. GP ChatGPT ★ 178,201repo stars dbt Analytics Project taste dbt Analytics Project taste — a prompt for ChatGPT sets conventions for dbt models, tests, documentation, and CI. Use it while shaping an analytics project or revising its model structure. GP ChatGPT ★ 178,201repo stars Design System taste Design System taste — a prompt for ChatGPT that enforces pragmatic design system standards, tokens, accessibility, and component architecture. GP ChatGPT ★ 178,201repo stars

Project sponsors

Companies that keep this analytics open