Browse Skills

QA verifies a feature after implementation by tracing the wiring, running the happy path, and trying to break it with edge cases and failure modes. Use it when you need an actionable finding or explicit adversarial validation.

Hands-On Testing performs manual browser-based testing of a web app with playwright-cli. It opens pages, runs interactions, captures screenshots and console output, and writes a structured test report.

Security Review invokes a security expert to assess code changes that affect process spawning, file access, config loading, or environment handling. Use it when reviewing MCP-LSP bridge changes with security-sensitive behavior.

Old Coder turns a change into an approved executable spec, then drives tests, implementation, and a gauntlet of checks to produce evidence before review. Use it for high-assurance changes in tests, types, coverage, mutation, or other high-stakes code.

AI Developer Guide applies decision criteria, anti-pattern detection, debugging, and quality gates for backend or language-agnostic implementation reviews. Use it to assess code smells, failures, completeness, and fallback behavior.

Coding Principles provides language-agnostic guidance for writing maintainable, readable, and well-structured code. Use it when implementing features, refactoring, or reviewing code quality.

Front Review validates React and TypeScript frontend changes against a Design Doc and security requirements. Use it after implementation to review compliance, resolve findings, and apply optional fixes.

Frontend AI Guide applies React and TypeScript review criteria to component, hook, and browser-behavior changes. Use it to check implementation completeness, anti-patterns, and frontend quality gates.

Integration E2E Testing defines principles for designing integration and end-to-end tests, including ROI scoring, budget limits, and review criteria. Use it when selecting test candidates or checking test quality for UI and service flows.

Integration Test Recipes adds integration and end-to-end tests to an existing codebase using design docs and confirmed requirements. Use it when you need test coverage for backend, frontend, or full-stack behavior.

Recipe Diagnose investigates a reported problem, verifies findings, and derives likely fixes. Use it for diagnosis flows that need evidence collection, coverage checks, and solution synthesis.

Recipe Review validates implementation against a design doc and checks for security issues after changes. It is used when post-implementation review needs compliance checks and optional fix routing.