doc-ptest
Create Performance Test Specifications (PTEST) as Layer 10 subtype artifacts for load, stress, endurance, and spike validation
Find an Agent Skill for your task. Read the guide and copy the install command.
Updated 10-29 00:09
12,875 results
Create Performance Test Specifications (PTEST) as Layer 10 subtype artifacts for load, stress, endurance, and spike validation
Unified SECTEST audit wrapper that runs validator then reviewer and emits combined report for fixer workflows
Apply automated and guided fixes for SECTEST findings from audit/review reports
Validate Security Test Specifications (SECTEST) against Layer 10 SECTEST MVP schema and structure contracts
Create Smoke Test Specifications (STEST) as Layer 10 subtype artifacts for deployment critical-path validation
Automated STEST generation and review orchestration for deployment smoke validation
Automated UTEST generation and review orchestration for component-level unit test workflows
Validate Unit Test Specifications (UTEST) against Layer 10 UTEST MVP schema and structure contracts
Validate UX Specifications (UXSPEC) documents against Layer 9.52 schema standards
Guide the code review and testing phase. Use when evaluating code for testability, designing unit tests, or looking for edge cases — to ensure tests resist…
Tests acceptance criteria and edge cases as an end user in a real browser (Chrome DevTools MCP, Playwright or the browser tool of the environment), then writes…
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding…
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Playwright E2E testing — Page Object Model, configuration, flaky test strategies, and CI/CD integration. Use when writing, debugging, or configuring E2E tests.
Use when the task needs one-shot or reproducible browser automation from the terminal: navigation, form filling, snapshots, screenshots, traces, data…
Use when the task needs a persistent Playwright session for iterative local web or Electron debugging, repeated reloads, and functional plus visual QA through…
Write and review Vitest tests: structure, assertions, fixtures and lifecycle, the mocking surface and its hoisting rules, snapshots, configuration and…
Use if orchestrating multi-agent E2E campaigns with independent evidence review, isolated runtimes, and defect fix/retest loops.
Use if writing, running, or debugging Maestro E2E test flows on iOS Simulators, Android, or Web, including MCP agent automation and CI suites.
Write tests using TDD principles with integration tests as default and minimal mocking. Use when writing code, fixing bugs, or when user mentions tests, TDD,…
Enforces a11y labels, 44pt targets, 200% text, VoiceOver, TalkBack. Use when adding a pressable, swipe or a11y label, text clips when large, contrast fails or…
Gates test-only code behind one literal TEST_ONLY switch: debug menu, debug link, simulated clock and offline. Use when adding a debug screen, a test hook, a…
Runs the end-of-build design review: every screen x theme x direction x text size x device, graded findings, a fix round, a sign-off. Use when a release nears…
Writes and runs Maestro E2E flows on iOS simulators and Android emulators - testID steps, debug-link setup, screenshot baselines. Use when adding a flow or an…