Menu
Use when creating, running, or debugging K6 load tests for frontend flows.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use BEFORE building or changing any UI — components, layout, color, spacing, typography, interaction states, or visual styling — to verify the planned change matches the Figma design via the Figma MCP. Run this gate before writing or editing UI code.
Use when placing features, repositories, hooks, or fixing dependency-cruiser errors.
Use when validating frontend changes before commit, push, or PR.
Use when placing, moving, naming, or splitting frontend files.
Use when retrieving or addressing PR review comments.
Use when frontend files, components, hooks, or helpers exceed complexity gates.
| name | load-testing |
| description | Use when creating, running, or debugging K6 load tests for frontend flows. |
make test-load
make test-load-signup
Both targets start the production service, wait for health, prepare result directories, and run K6 through Docker Compose.
tests/load/results/.Use the existing K6 variables in the Makefile:
K6_TEST_SCRIPTK6_RESULTS_FILEK6_SIGNUP_SCRIPTK6_SIGNUP_RESULTS_FILERun the smallest scenario that exercises the changed flow, then inspect the K6 summary and generated HTML result.
Before applying this skill, confirm the active task against ../AI-AGENT-GUIDE.md and ../SKILL-DECISION-GUIDE.md so every relevant skill is consulted.
Before presenting changes, check changed text files for lines longer than 100 characters.
If any exist, tell the user each path:line and measured character count.
Treat this as disclosure, not failure, unless a project gate fails.