performance-load-testing
Performance Load Testing
Overview
Use this skill to validate performance under realistic and stress conditions before production risk increases.
Scope Boundaries
- Use this skill when the task matches the trigger condition described in
description. - Do not use this skill when the primary task falls outside this skill's domain.
Shared References
- Workload realism rules:
references/workload-realism-rules.md
Templates And Assets
- Load profile template:
assets/load-profile-template.md
- Load test report template:
assets/load-test-report-template.md
Inputs To Gather
- Critical user flows and traffic distribution.
- Target latency/throughput/error thresholds.
- Environment and dependency readiness.
- Saturation and recovery expectations.
Deliverables
- Load profile and execution plan.
- Bottleneck evidence and saturation points.
- Release readiness recommendation and fixes.
Workflow
- Define workload in
assets/load-profile-template.md. - Validate realism using
references/workload-realism-rules.md. - Execute baseline/peak/stress phases.
- Document outcomes in
assets/load-test-report-template.md. - Publish remediation and retest plan.
Quality Standard
- Load profiles represent production-critical behavior.
- Bottlenecks are evidenced and prioritized.
- Saturation behavior and failure modes are understood.
Failure Conditions
- Stop when test profile misses critical production traffic patterns.
- Stop when results cannot be reproduced or interpreted confidently.
- Escalate when unresolved bottlenecks threaten SLOs.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9