單元測試

Test Nuxt 3 / Nitro API handlers with real PostgreSQL, transaction rollback isolation, and typed factories. No mocks, real SQL.

Automatically troubleshoot unexpected results OR command/script errors without user request. Triggers when: (1) unexpected behavior - command succeeded but expected effect didn't happen, missing expected errors, wrong output, silent failures; (2) explicit failures - stderr, exceptions, non-zero exit, SDK/API errors. Applies systematic diagnosis using error templates, hypothesis testing, and web research for any Stack Overflow-worthy issue.

Guides test creation for Polibase following strict testing standards. Activates when writing tests or creating test files. Enforces external service mocking (no real API calls), async/await patterns, test independence, and proper use of pytest-asyncio to prevent CI failures and API costs.

Guides on analyzing and improving test coverage for Python (pytest-cov) and JavaScript (c8) projects. Use when a user asks to set up test coverage, generate coverage reports, understand why coverage is low, or improve their test coverage.

Test n8n nodes using Jest, nock for HTTP mocking, and local testing workflows with npm link. Use this skill when writing test files in __tests__ folders, mocking HTTP requests with nock, creating mock IExecuteFunctions contexts, testing helper functions, setting up golden file tests, running the linter before publishing, or locally testing nodes in the n8n UI. Apply when organizing test files, mocking external APIs, validating node execution output, or following the pre-publish checklist.

Run ruff + pytest and fix issues minimally.

Best practices for writing Python tests - use when creating or improving test coverage

Vitest setup and best practices. Use when configuring Vitest for TypeScript projects.

Review Prisma code for common violations, security issues, and performance anti-patterns found in AI coding agent stress testing. Use when reviewing Prisma Client usage, database operations, or performing code reviews on projects using Prisma ORM.

Automates visual regression testing for Storybook components using cloud-based snapshot comparison. Use when setting up visual testing, catching UI regressions, or reviewing component changes.

🔄 PHP-QA-CI TOOL ORCHESTRATOR - Automatic run→fix→run cycling for php-qa-ci tools.**ONLY for php-qa-ci pipeline tools** (./bin/qa -t toolname)NOT for ad-hoc tool execution outside php-qa-ci.Use when user requests QA tools via php-qa-ci:- "run phpstan", "use stan skills"- "run tests", "run phpunit"- "run rector", "run cs fixer"- "run allStatic", "run allCS"**CRITICAL**: MUST cycle automatically until tool reports clean OR escalation needed.DO NOT stop after one fix to ask "what next?" - KEEP CYCLING.Supports all php-qa-ci tools via ./bin/qa -t {toolname}:- phpstan (static analysis) - has fixer agent- phpunit (tests) - has fixer agent- rector (refactoring) - self-fixing, re-run until clean- fixer (code style) - self-fixing, re-run until clean- infection (mutation testing) - no auto-fix- allStatic/allCs/allTests - meta groupsAutomatically detects which tools have fixers and invokes them.**PERFORMS PREFLIGHT CHECK**: Invokes docs-conflict-checker agent to ensureproject documentation doesn

Patterns for creating components that return VirtualNode data structures. Covers component structure, Props types, HTML wrappers vs custom components, CSS organization, and testing. Use when creating UI components. Includes script for generating component scaffold.

Creates risk-based test plans and strategies. Use when planning testing, defining test scope, or documenting QA approach.

Skill de teste para verificar o funcionamento do sistema

Balance escape room difficulty, timing, and hint systems to achieve 60-70% completion rate. Designs progressive difficulty curves, three-tier hint systems, stuck-point analysis, and playtest metrics. Use when balancing game difficulty, designing hint systems, analyzing playtest data, or optimizing escape room completion rates.

Design mobile-first responsive layouts using fluid containers, relative units, standard breakpoints, and touch-friendly interfaces that adapt seamlessly across devices from mobile to desktop. Use this skill when implementing responsive designs, media queries, viewport configurations, or testing across screen sizes. Applies to any frontend layout work requiring optimization for mobile phones, tablets, and desktop displays with readable typography and appropriate content prioritization.

Use when working with .cs files, .NET projects, implementing C# features, advising on C#/.NET architecture and patterns, or answering questions about C#/.NET development. Covers async patterns, dependency injection, LINQ, and testing conventions.

Creates and tests Pangea Ruby function resources with synthesis testing. Use when creating new resources, writing synthesis tests, generating test coverage for Terraform DSL resources, or filling test gaps for AWS/Cloudflare/Hetzner resources.

REST Controller 전문가. Thin Controller 패턴, CQRS Command/Query Controller 분리,ResponseEntity<ApiResponse<T>> 래핑, @Valid 검증 필수. DELETE 금지(PATCH 사용).TestRestTemplate 필수 (MockMvc 금지). UseCase 의존. Mapper DI.

フロントエンド（TypeScript/Svelte 5/Vitest）のテスト実装とデバッグを行います。テストの作成、テストの実行、テストエラーの修正、Svelte 5 コンポーネントのテスト、国際化対応のモックなどのテスト関連タスクに使用します。