k6-best-practices
k6 Scenario Builder
Enforces a consistent, production-ready pattern for k6 load test scripts using JavaScript or TypeScript, covering HTTP/REST, WebSocket, and gRPC protocols.
Output Format
When producing or fixing a script, always deliver three things:
- A complete, runnable script file — never a partial snippet.
- The exact run command with the environment variables needed.
- A one-line explanation of the executor chosen and why it fits the load goal.
When fixing any OOM error or open() misuse, cover both failure modes — even if the user only mentioned one:
- Plain variable at init context → OOM (data copied per VU). Fix:
SharedArray. open()insidedefault()→ immediate runtime error (can't call open() in the VU context). Fix: move to init context.
More from rcampos09/performance-testing-skills
gatling-best-practices
Guides developers and testers in writing, fixing, and structuring Gatling load test scenarios. Use this skill whenever the user mentions load testing, performance testing, stress testing, Gatling, virtual users, VUs, ramp-up, injection profiles, simulations, JMeter migration, k6 migration, throughput, response time SLAs, or wants to benchmark an API or service — even if they don't explicitly say 'Gatling' or 'performance test'.
25performance-testing-strategy
>
19performance-report-analysis
>
13locust-best-practices
>
5