Unit Testing

Godot 测试与调试工作流专家，支持自然语言描述自动完成单元测试、集成测试、错误诊断、性能调试等测试工作

Expert testing and quality engineer for Vitest (running on Bun). Use when user needs test creation, test strategy, code quality setup, E2E testing, or debugging test failures. Examples - "write tests for this function", "create E2E tests with Playwright", "help me test this API route", "setup testing infrastructure", "why is this test failing?", "improve code quality with Biome".

Define MVP scope, success metrics, and explicit out-of-scope items to focus on the smallest testable product. Use when user asks to define MVP, scope MVP, or start Stage 3 after personas.

Build responsive layouts that work seamlessly across mobile, tablet, and desktop screen sizes using mobile-first development, fluid layouts, and relative units. Use this skill when implementing layouts or UI components that need to adapt to different screen sizes. When setting up breakpoints, media queries, or responsive utilities. When using relative units (rem, em, %) instead of fixed pixels. When ensuring touch-friendly tap targets and optimizing for mobile performance. When testing UI changes across multiple device sizes. When implementing responsive typography, images, or navigation patterns.

Research and document write/create APIs of a source system to enable write-back testing functionality.

Generate project-specific skills and commands from PRDs for Blueprint Development methodology. Use when generating skills for architecture patterns, testing strategies, implementation guides, or quality standards from requirements documents.

Assist contributors working on the functype library codebase. Use this skill when creating new data structures, implementing functional interfaces (Functor, Monad, Foldable), adding tests, debugging library internals, or understanding functype's Scala-inspired architecture patterns including the Base pattern, HKT system, and Companion utilities.

Creates Karibu unit tests for Vaadin views.

Complete browser automation with Playwright. **ALWAYS use when user needs browser testing, E2E testing, screenshots, form testing, or responsive design validation.** Auto-detects dev servers, saves test scripts to working directory. Examples - "test this page", "take screenshots of responsive design", "test login flow", "check for broken links", "validate form submission".

Automate browser actions using Puppeteer with a simple DSL for web testing and automation

Systematic project orientation for unfamiliar codebases. Automatically activates when Claude detects uncertainty about project state, structure, or tooling. Analyzes git state (branch, changes, commits), project type (language, framework, structure), and development tooling (build, test, lint, CI/CD). Provides structured summary with risk flags and recommendations. Use when entering new projects or when working on shaky assumptions.

Reference and maintain knowledge of the project's technical stack including frameworks, languages, databases, testing tools, and third-party services. Use this skill when making architectural decisions about which technologies to use. When adding new dependencies or integrating third-party services. When setting up development environments or deployment infrastructure. When choosing between different libraries or frameworks for a feature. When documenting the technology choices made in the project. When onboarding new team members to understand the tech stack. This skill helps ensure technology choices align with the established stack and provides a reference for all technical decisions.

Build accessible user interfaces with semantic HTML, proper ARIA attributes, keyboard navigation, and screen reader compatibility. Use this skill when creating or modifying HTML markup, UI components, forms, or interactive elements. When implementing keyboard navigation, focus management, or tab order. When adding alternative text for images or labels for form inputs. When ensuring sufficient color contrast ratios. When working with navigation menus, modals, buttons, or dynamic content. When structuring pages with proper heading hierarchy (h1-h6). When testing UI changes for screen reader compatibility.

Property-based testing with Hypothesis for discovering edge cases and validating invariants.Use when implementing comprehensive test coverage, testing complex logic with many inputs,or validating mathematical properties and invariants across input domains.Triggered by: hypothesis, property-based testing, @given, strategies, generative testing.

OpenShift platform and Kubernetes expert with deep knowledge of cluster architecture, operators, networking, storage, troubleshooting, and CI/CD pipelines. Use for analyzing test failures, debugging cluster issues, understanding operator behavior, investigating build problems, or any OpenShift/Kubernetes-related questions.

Classify a change set as behavior vs structure, then recommend the correct PR label (change:behavior or change:structure) and the appropriate local/CI checks. Use when the user asks whether a change is a behavior change or a structure change, what label to apply, or how CI/testing should differ based on change type.

Create Buck2 tests with local resources (processes, services, databases) using LocalResourceInfo and ExternalRunnerTestInfo. Use when tests need external dependencies like databases, HTTP servers, message queues, or Unix sockets that Buck2 should manage automatically. (project)

Comprehensive testing workflow that should be used proactively after ANY code changes. Covers immediate testing, recursive package validation with `...`, target determination for affected packages, and reverse dependency testing. Use this skill after modifying BUILD files, changing code, fixing tests, or before committing to ensure nothing breaks downstream. (project)

Develop, test, and document the PikaCSS monorepo (core engine, unplugin adapters, Vite/Nuxt plugins, docs site) using pnpm-based workflows.

To resize the browser window, change viewport size to test responsive layouts.