agentleFS
Sign inStart free
jabrenajabrena/cursor-rules-java/skills/152-java-performance-gatling/SKILL.md

152-java-performance-gatling

Skill452 starsChanged 3 months agoApache-2.0View on GitHub

Use when you need to set up Gatling performance testing for a Java Maven project — including adding Gatling dependencies and the Gatling Maven plugin, creating Java simulations, running gatling:test, configuring a simulation class, and reviewing generated reports. This should trigger for requests such as Add Gatling performance testing; Apply Gatling performance testing; Create a Gatling simulation; Add Gatling support; Review Gatling performance test assertions and feeders. Part of Plinth Toolkit

We split this skill into the rules it gives an agent

19 rules. About 0 are common, 6 are distinctive, and 13 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 13

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Add Gatling dependencies and the gatling-maven-plugin to pom.xml

    line 15
  2. Very specific:

    Run simulations with ./mvnw gatling:test

    line 17
  3. Very specific:

    Use ./mvnw gatling:help -Ddetail=true -Dgoal=test to inspect available plugin options

    line 19
  4. Distinctive:

    Scope: Use Gatling through the Maven plugin for Java simulations.

    line 22
  5. Very specific:

    PREREQUISITE: Verify the project is Maven-based and prefer ./mvnw when the Maven wrapper exists

    line 28
  6. Very specific:

    BUILD CONFIGURATION: Add Gatling dependencies with test scope and configure io.gatling:gatling-maven-plugin in pom.xml

    line 29
  7. Distinctive:

    VERSION SELECTION: Use the project's existing dependency/version-management pattern.

    line 30
  8. Very specific:

    SIMULATION LOCATION: Place Java simulations under src/test/java using an appropriate package name

    line 31
  9. Very specific:

    RESOURCE LOCATION: Place Gatling resources such as gatling.conf, feeders, request-body templates, and Logback test configuration under …

    line 32
  10. Distinctive:

    BEFORE APPLYING: Read the reference for setup, execution, and verification guidance

    line 33
  11. Distinctive:

    EDGE CASE: If the project is not Maven-based, stop and explain that this skill targets Maven projects before suggesting Gradle or sbt …

    line 34
  12. Very specific:

    EDGE CASE: If multiple simulations exist, configure or pass -Dgatling.simulationClass=<FullyQualifiedClassName> for non-interactive …

    line 35
  13. Distinctive:

    Add Gatling performance testing

    line 39
  14. Distinctive:

    Create a Gatling simulation

    line 41
  15. Very specific:

    Check for pom.xml, the Maven wrapper, existing test dependencies, dependency management, plugin management, and any existing Gatling …

    line 49
  16. Very specific:

    Add the Gatling test dependency and io.gatling:gatling-maven-plugin using the project's existing version and plugin configuration style.

    line 53
  17. Very specific:

    Create Java simulation classes under src/test/java or adapt existing simulations, keeping scenario names, base URLs, injection profiles, …

    line 57
  18. Very specific:

    Add optional Gatling resources under src/test/resources, including gatling.conf, feeders, request body templates, and logback-test.xml only …

    line 61
  19. Very specific:

    Use ./mvnw gatling:test to run simulations and -Dgatling.simulationClass=<FullyQualifiedClassName> when a specific simulation must be …

    line 65

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Run performance tests based on Gatling

Provide a complete Gatling performance testing setup for Java Maven projects by adding the required test dependencies and Gatling Maven plugin configuration, creating or guiding Java simulation placement, and explaining how to run simulations and inspect reports.

What is covered in this Skill?

  • Add Gatling dependencies and the gatling-maven-plugin to pom.xml
  • Project structure: src/test/java for Java simulations and src/test/resources for Gatling configuration, feeders, templates, and logging
  • Run simulations with ./mvnw gatling:test
  • Select a simulation with -Dgatling.simulationClass=<FullyQualifiedClassName> when multiple simulations exist
  • Use ./mvnw gatling:help -Ddetail=true -Dgoal=test to inspect available plugin options
  • Review generated Gatling run output and reports under the build output directory

Scope: Use Gatling through the Maven plugin for Java simulations. Prefer project-local Maven wrapper commands when available.

Constraints

Gatling setup must be Maven-based, reproducible, and compatible with Java project conventions. Prefer official Gatling Maven plugin behavior and avoid inventing unsupported command-line options.

  • PREREQUISITE: Verify the project is Maven-based and prefer ./mvnw when the Maven wrapper exists
  • BUILD CONFIGURATION: Add Gatling dependencies with test scope and configure io.gatling:gatling-maven-plugin in pom.xml
  • VERSION SELECTION: Use the project's existing dependency/version-management pattern; if no Gatling versions are present, ask before pinning versions or use placeholders that require replacement
  • SIMULATION LOCATION: Place Java simulations under src/test/java using an appropriate package name
  • RESOURCE LOCATION: Place Gatling resources such as gatling.conf, feeders, request-body templates, and Logback test configuration under src/test/resources
  • BEFORE APPLYING: Read the reference for setup, execution, and verification guidance
  • EDGE CASE: If the project is not Maven-based, stop and explain that this skill targets Maven projects before suggesting Gradle or sbt alternatives
  • EDGE CASE: If multiple simulations exist, configure or pass -Dgatling.simulationClass=<FullyQualifiedClassName> for non-interactive execution

When to use this skill

  • Add Gatling performance testing
  • Apply Gatling performance testing
  • Create a Gatling simulation
  • Add Gatling support
  • Review Gatling performance test assertions and feeders

Workflow

  1. Inspect the Maven project

Check for pom.xml, the Maven wrapper, existing test dependencies, dependency management, plugin management, and any existing Gatling configuration.

  1. Add Gatling build configuration

Add the Gatling test dependency and io.gatling:gatling-maven-plugin using the project's existing version and plugin configuration style.

  1. Create or adapt Java simulations

Create Java simulation classes under src/test/java or adapt existing simulations, keeping scenario names, base URLs, injection profiles, and assertions explicit.

  1. Configure resources

Add optional Gatling resources under src/test/resources, including gatling.conf, feeders, request body templates, and logback-test.xml only when the project needs them.

  1. Run and explain Gatling execution

Use ./mvnw gatling:test to run simulations and -Dgatling.simulationClass=<FullyQualifiedClassName> when a specific simulation must be selected.

  1. Verify reports and next steps

Confirm the Gatling run completed, point to the generated report location from the command output, and summarize any failed assertions or performance findings.

Reference

For detailed guidance, examples, and constraints, see references/152-java-performance-gatling.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free