Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Orchestrate test execution — run unit, integration, and E2E tests, collect coverage reports, and analyze failures. Use when running tests, checking coverage, debugging test failures, or validating code changes before merge.
Set up LLM workflow discipline for projects that use AI / LLM calls in production or eval suites. Authors an eval-cost-watcher agent that projects token cost BEFORE regression evals run, plus an AI-workflow-discipline rule covering mock-mode placement, fixture freshness, and multi-stage cost accumulation. Optionally a…
A workflow for comparing two versions of a prompt, skill, or piece of text without revealing which one is the new version. Separate agents create the versions, and a person scores them without seeing their labels.
Honest-completion ruleset for changes that touch tests or the code they cover. Use before deleting, skipping, renaming, or rewriting a test, before weakening an assertion, and before hardcoding or stubbing an implementation to make a test pass. Also covers what to do when a test looks genuinely wrong.
MSW (Mock Service Worker) v2 best practices, patterns, and API guidance for API mocking in JavaScript/TypeScript tests and development. Covers handler design, server setup, response construction, testing patterns, GraphQL, and v1-to-v2 migration. Baseline: msw ^2.15.0. Triggers on: msw imports, http.get, http.post…
Execute an approved plan or specification with targeted implementation, tests, evidence, review, and independent verification. Use for “implement this”, “execute the plan”, “build this feature”, “write the code”, or “refactor without changing behavior”.
Use when doing non-trivial coding with Hermes, OpenClaw, Claude Code, Codex CLI, or similar autonomous coding agents. Orchestrates Karpathy-style minimal-change discipline, grill-plan intake, TDD, systematic debugging, subagent-driven implementation, spikes, and pre-commit review into one end-to-end workflow.
A coding workflow for planning changes, writing tests before or alongside code, and reviewing the result. TDD, or test-driven development, means using tests to guide the implementation.
Verify and debug synthesized audio (Web Audio API) by rendering it offline and measuring the samples, instead of guessing from code or claiming it works untested. Use whenever building, changing, or reviewing UI sound effects, tones, synths, or any AudioContext graph — and especially when sound is reported as…
Use when designing, orchestrating, or executing autonomous multi-agent coding loops with financial budget caps, minimal fixes, and continuous dev-QA gates.
Test web applications in real browsers via Chrome DevTools Protocol including DOM inspection, console analysis, network profiling, performance auditing, Lighthouse CI, and visual regression.
Run APCA Lc text-contrast measurement on a Playwright page in BOTH light and dark color schemes. Returns deterministic apca. findings against rule-map.json. Use during ui-specialist Phase 6 (Accessibility).
Run the HUMHUM quality gates that are actually touched by the current diff — frontend typecheck + vitest, and Rust fmt/clippy/test — mirroring CI. Use before marking work done, opening a PR, or when asked to "verify", "check", or "run the gates".
Scans a target project to extract idiomatic patterns (test framework, code style, architecture, conventions) and generates customized TDD agents that use the project's actual patterns instead of generic pseudocode. Use when the user wants to adapt the TDD agents to a specific codebase.
Run the InvenTree Plugin AI Toolkit devcontainer and execute a plugin's test-all.sh. Covers Docker setup, postCreateCommand, server startup, and the lint/unit/integration/frontend-build/E2E layers.
Use when asked to "run QA", "qa check", "test checklist", or execute QA checklists against a running app via browser automation. Requires the browser-bridge MCP server and Chrome extension.
This skill guides scanning the codebase for memory and performance code smells, debugging performance problems, writing performance/memory tests that follow established project conventions, and updating docs/patterns/ when new categories of issues are discovered and fixed.
A QA workflow for testing software changes and fixing reported bugs through an MCP server. QA means checking that software works as expected before release.
Build, run, record, replay, debug, and maintain deterministic terminal, TUI, PTY cassette, and browser-terminal agent regression tests with ptywright. Use when an agent needs to drive CLI/TUI apps, create ptywright scripts, configure ptywright.config., record or replay PTY output, solidify browser terminal agent flows…
★not rated 1 3mo agoA93 tokens
originalApache-2.0
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: