Unit Testing

Playwright E2E testing with Page Object pattern, web-first assertions, and proper locators. Triggers on playwright, e2e, page object, getByRole.

Create and manage Azure Test Plans including test cases, suites, and execution. Use when setting up test plans or managing QA processes.

Code-centric Goal-Oriented Action Planning integrated with SPARC methodology. Use for feature implementation planning, performance optimization goals, testing strategy development, or any software development objective requiring systematic breakdown with measurable success criteria.

Implement mobile-first responsive designs with fluid layouts, standard breakpoints, and relative units to ensure optimal viewing experiences across all device sizes from mobile to desktop. Use this skill when creating or modifying UI layouts, implementing media queries, defining responsive breakpoints, or ensuring components adapt properly to different screen sizes. Use this skill when working with component files that render layouts, grids, navigation menus, or any UI elements that need to adjust based on viewport width. Use this skill when testing UI changes across mobile, tablet, and desktop screen sizes, optimizing touch targets for mobile users, or ensuring readable typography across all breakpoints.

Эксперт Android тестирования. Используй для JUnit, Espresso и Android test patterns.

Use when working with .rb files, Ruby gems, or implementing Ruby features. Covers Ruby idioms, naming conventions, enumerable patterns, service objects, error handling, and RSpec testing.

Generate high-level tasks and gated sub-tasks from a PRD, with relevant files and testing guidance.

Эксперт по bug bounty. Используй для поиска уязвимостей, написания отчётов, responsible disclosure и penetration testing.

Docker-based testing with testcontainers. Use when running tests with real databases.

Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.

Vitest configuration template and validation logic for test configuration. Standards differ by package type - use package-type specific configs (react-app, react-library, node-library, node-service, contracts, database, api, integration). Use factory pattern for React packages that need vite.config.ts merging.

Use when writing tests with Swift Testing (@Test,

Validate inputs and preconditions before work begins using symmetric validation across layers, allowlist thinking, and contextual business rules with auditability. Use this skill when writing input validation, form handling, API request validation, or domain logic checks. Applies to all boundary validation requiring structured error responses, edge-case coverage, sanitization, escaping, and contract tests ensuring consistent validation across clients, APIs, background jobs, and CLIs.

Expert knowledge for Testing Layer modeling in Documentation Robotics

React 18+ development patterns including components, hooks, state management, API integration, and accessibility. Use when: (1) building React components, (2) designing user interfaces, (3) implementing state management, (4) writing frontend tests.

Harness CI (Continuous Integration) for container-native builds, test intelligence, caching, parallelization, and build infrastructure management. Activate for build pipelines, CI steps, test automation, artifact publishing, and build optimization.

Containerizes applications with Docker, docker-compose, and Helm charts.Use when creating Dockerfiles, docker-compose configurations, or Helm charts for Kubernetes.Includes Docker Hardened Images (95% fewer CVEs), multi-stage builds, and 15+ battle-tested gotchas.

Analyze llm-compact-logger test output and configure enhancements. Use when user shares debug-compact.json or debug-report.json files.

Unconventional problem-solving with chaotic good energy. Finds creative edge cases, challenges assumptions, explores weird solutions that technically work. Use when you want creative chaos, alternative approaches, or to test if "normal" is actually optimal.

Apply systematic debugging methodology using medical differential diagnosis principles. Trigger when AI modifies working code and anomalies occur, or when users report unexpected test results or execution failures. Use observation without preconception, fact isolation, differential diagnosis lists, deductive exclusion, experimental verification, precise fixes, and prevention mechanisms.