gatling

Guidance for using the Gatling MCP server's tools (tests, runs, packages, source repositories, locations, teams) to inspect and drive Gatling Enterprise. Use whenever calling those tools, before assuming an ID, role, or format that isn't spelled out in the tool's own description.

Guide for deploying and starting Gatling tests on Gatling Enterprise. Use this skill when the user wants to deploy, push, or start tests on Gatling Enterprise using Gatling build tools (aka plugins) and Configuration as Code.

Guide to generate or update the .gatling/package.conf package descriptor file for Gatling Enterprise deployment. Use this skill when the user wants to configure, set up, or modify their package descriptor file, stop criteria, or load generator settings using Configuration as Code.

Guide for converting Apache JMeter tests to Gatling. Use this skill whenever the user mentions JMeter, .jmx files, JMeter test plans, or asks to convert or migrate a JMeter test to Gatling.

Guide for converting HP/Micro Focus/OpenText LoadRunner scripts to Gatling. Use this skill whenever the user mentions LoadRunner, VuGen, LR scripts, .c action files, vuser_init, web_url, web_submit_data, or any LoadRunner-specific functions. Trigger on phrases like "convert this action", "convert this LoadRunner test to Gatling", "migrate from LoadRunner", or when the user shares .c/.h files that look like LoadRunner scripts.

Bootstrap/set up a Gatling project to get started with Gatling load tests.

Find an existing Gatling project, detect language and build tool used

Scaffolds a new Gatling documentation page with correct Hugo front matter, directory structure, and placeholder sections based on the page type. Use when creating a new guide, reference page, or tutorial from scratch.

Reviews a Gatling documentation page against the team style guide. Use when writing, editing, or reviewing a docs page — checks front matter completeness, verb-led headings, active voice, present tense, code example quality, Hugo shortcode usage, screenshot guidance, markdown tables, and Google Style Guide compliance.

Applies a specific change to an existing Gatling documentation page while enforcing style guide compliance on touched content. Use when making targeted edits — adding a section, updating prerequisites, rewriting for voice and tense, or updating code examples. Does not do a full style audit; use review-doc for that.