perf

⚡ Performance Testing Skills (perf-skills)

Turn your AI assistant into a senior performance engineer. An opinionated, token-optimized knowledge base for planning, scripting, executing, and analyzing load tests across any major tool.

"The more you sweat in training, the less you bleed in battle." - Richard Marcinko
"The more relevant skills your AI loads during development, the fewer fires you fight in production."

---

📖 Table of Contents

• 🔍 What is perf-skills?
• 📦 Supported Tools & Protocols
• ⛓️ Dynamic Value Correlation
• 🛠️ Compatible AI Assistants
• 🚀 Installation & Setup
• 📂 File Structure & Routing
• 💡 How the Skill Works
• 🤝 Contributing & License

---

🔍 What is perf-skills?

perf-skills is a highly structured knowledge base designed specifically for AI coding assistants (like Claude, Cursor, Windsurf, etc.). It injects deep, expert-level performance testing context on-demand, allowing your AI to generate correct scripts, follow best practices, and debug bottlenecks without bloating its context window.

---

📦 Supported Tools & Protocols

Category	Supported Technologies
Open Source	Apache JMeter, k6 (Grafana Labs), Gatling, Locust
Commercial/SaaS	NeoLoad (Tricentis), LoadRunner (OpenText), OctoPerf
Protocols	HTTP/REST, gRPC, GraphQL, WebSocket, SSE, JDBC, SOAP, Kafka/MQ, Citrix, SAP

---

⛓️ Dynamic Value Correlation

A major highlight of this library is the Dynamic Value Correlation engine (correlation.md). Correlation is often the most fragile part of performance scripting; perf-skills equips your AI with robust strategies to handle it flawlessly:

• The Correlation Workflow: Standardizes identifying, extracting, injecting, and verifying dynamic tokens.
• Advanced Scanning: Strategies for Next.js/React SSR hydration payloads (__NEXT_DATA__), SPA client-side token retrieval, runtime hooking, and Swagger contract mapping.
• Robust vs. Brittle Regex: Guides your AI to write expressions that don't break on minor HTML structure modifications.
• Tech Stack Rules: Pre-defined extraction rules for enterprise environments:
  • ASP.NET: ViewState, RequestVerificationToken, EventValidation.
  • Java: JSF ViewState, Spring Security _csrf, JSESSIONID.
  • SAP & Oracle: NetWeaver sap-contextid, ADF _afrLoop.
  • OAuth 2.0 / SAML: SAMLResponse, code, state tokens.
  • Modern SSR/SPA: Hydration states, Laravel _token, Django csrfmiddlewaretoken, Rails authenticity_token.
• Diagnostic Playbook: Step-by-step troubleshooting for URL-encoding, base64 url-safe transforms, JSON-escaping, and thread safety.

---

🛠️ Compatible AI Assistants

perf-skills works seamlessly with any modern AI development tool:

AI Assistant	Integration Method
Claude Code	Native Plugin or CLAUDE.md context referencing
Windsurf (Cascade)	Local Skill configuration
Cursor	Custom rules .cursor/rules/ or index via @Docs
Cline / Roo Code	Workspace instructions / custom rules
Aider	Conventions file or /read context loading
GitHub Copilot	Repository-level custom instructions
Antigravity / Pochi	Context files / instruction references

---

🚀 Installation & Setup

Claude Code Plugin (Recommended)

To install as a Claude Code plugin, run:

/plugin marketplace add QAInsights/perf-skills
/plugin install perf@qainsights
/reload-plugins

Once installed, the /perf skill will be available and automatically load when you ask performance-related questions.

To update to the latest version:

/plugin marketplace update
/plugin uninstall perf
/plugin install perf@qainsights
/reload-plugins

---

Install as local Skills (npx)

If you are using a tool that supports npx skills, add it directly:

npx skills add QAInsights/perf-skills

---

Setup for Other Editors

🌊 Windsurf (Cascade)

1. Clone this repository:

   git clone https://github.com/QAInsights/perf-skills.git
   

2. Copy the skill directory:

   cp -r perf-skills/skills/perf ~/.windsurf/skills/
   

The skill will auto-trigger when you ask about performance testing, load testing, or any supported tool.

🎯 Cursor

Option A (Project Rules):

1. Copy SKILL.md content into a rule file: .cursor/rules/perf.mdc.
2. Configure rules to trigger on file paths matching performance scripts or performance-related prompts.