151-java-performance-jmeter
This Claude Code skill sets up JMeter performance testing for Java projects by creating an executable run-jmeter.sh script from a template, configuring the project structure with load test files, and enabling customizable load parameters through command-line options and environment variables. Use it when adding or improving performance testing capabilities to a Java project, ensuring JMeter is installed first and the script template is copied verbatim without modifications.
git clone --depth 1 https://github.com/jabrena/cursor-rules-java /tmp/151-java-performance-jmeter && cp -r /tmp/151-java-performance-jmeter/skills/151-java-performance-jmeter ~/.claude/skills/151-java-performance-jmeterSKILL.md
# Run performance tests based on JMeter Provide a complete JMeter performance testing solution by creating the run-jmeter.sh script from the exact template, making it executable, and configuring the project structure for load testing. Supports custom loops, threads, ramp-up, and environment variable overrides. **What is covered in this Skill?** - Create run-jmeter.sh in project root from the exact template (no modifications) - Project structure: src/test/resources/jmeter/load-test.jmx, target/ for results - Script options: -l (loops), -t (threads), -r (ramp-up), -g (GUI), -h (help) - Environment variables: JMETER_LOOPS, JMETER_THREADS, JMETER_RAMP_UP - Verify JMeter is installed and available before proceeding **Scope:** Copy the script template verbatim. Do not modify, interpret, or enhance the template content. ## Constraints JMeter must be installed and available in PATH. If not available, show a message and exit. Use only the exact template for the run-jmeter.sh script. - **PREREQUISITE**: Verify JMeter is installed and accessible via `jmeter --version` before creating the script - **CRITICAL**: Copy the run-jmeter.sh template exactly — do not modify, interpret, or enhance - **PERMISSION**: Make the script executable with `chmod +x run-jmeter.sh` - **BEFORE APPLYING**: Read the reference for the exact script template and usage instructions - **EDGE CASE**: If request scope is ambiguous, stop and ask a clarifying question before applying changes - **EDGE CASE**: If required inputs, files, or tooling are missing, report what is missing and ask whether to proceed with setup guidance ## When to use this skill - Improve the code with JMeter performance testing - Apply JMeter performance testing - Refactor the code with JMeter performance testing - Add JMeter support ## Workflow 1. **Verify JMeter prerequisite** Check `jmeter --version` and stop with guidance if JMeter is not installed or not available in PATH. 2. **Read JMeter reference template** Read `references/151-java-performance-jmeter.md` and use the `run-jmeter.sh` template exactly as provided. 3. **Create script and project structure** Create `run-jmeter.sh` in project root, ensure required JMeter directories/files exist, and apply executable permission with `chmod +x`. 4. **Explain usage and environment overrides** Document CLI options (`-l`, `-t`, `-r`, `-g`, `-h`) and environment variable overrides (`JMETER_LOOPS`, `JMETER_THREADS`, `JMETER_RAMP_UP`). ## Reference For detailed guidance, examples, and constraints, see [references/151-java-performance-jmeter.md](references/151-java-performance-jmeter.md).
Use when you need to generate a checklist document with Java system prompts, following the embedded template exactly and producing INVENTORY-SKILLS-JAVA.md in the project root. This should trigger for requests such as Create Java system prompts checklist; Generate INVENTORY-SKILLS-JAVA.md; Use @001-skills-inventory. Part of cursor-rules-java project
Use when you need to generate a checklist document with embedded agents inventory, following the embedded template exactly and producing INVENTORY-AGENTS-JAVA.md in the project root. This should trigger for requests such as Create embedded agents inventory checklist; Generate INVENTORY-AGENTS-JAVA.md; Use @002-agents-inventory. Part of cursor-rules-java project
Use when you need to install the embedded robot agents into either .cursor/agents or .claude/agents, selecting the destination interactively and copying the embedded agent definitions from project assets. This should trigger for requests such as Install embedded agents; Bootstrap .cursor/agents; Bootstrap .claude/agents; Copy robot agents. Part of cursor-rules-java project
Guides the creation of agile epics with comprehensive definition including business value, success criteria, and breakdown into user stories. Use when the user wants to create an agile epic, define large bodies of work, break down features into user stories, or document strategic initiatives. This should trigger for requests such as Create an agile epic; Write an epic; I need to create an epic; Define an epic; Epic definition. Part of cursor-rules-java project
Guides the creation of detailed agile feature documentation from an existing epic. Use when the user wants to split an epic into feature files, derive features with scope and acceptance criteria, or plan feature documentation for stakeholders or engineering. This should trigger for requests such as Create features from an epic; Split epic into features; Feature files from epic; Derive features from epic. Part of cursor-rules-java project
Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story. Part of cursor-rules-java project
Use when you need to generate Architecture Decision Records (ADRs) for a Java project through an interactive, conversational process that systematically gathers context, stakeholders, options, and outcomes to produce well-structured ADR documents. This should trigger for requests such as Generate ADR; Create Architecture Decision Record; Document architecture decision; Architecture Decision Record for Java. Part of cursor-rules-java project
Facilitates conversational discovery to create Architectural Decision Records (ADRs) for functional requirements covering CLI, REST/HTTP APIs, or both. Use when the user wants to document command-line or HTTP service architecture, capture functional requirements, create ADRs for CLI or API projects, or design interfaces with documented decisions. This should trigger for requests such as Create ADR for functional requirements; Document functional requirements; Capture functional requirements; Generate functional requirements in an ADR. Part of cursor-rules-java project