單元測試

Configuration validation and testing utilities for OpenRouter API. Use when validating API keys, testing model availability, checking routing configuration, troubleshooting connection issues, analyzing usage costs, or when user mentions OpenRouter validation, config testing, API troubleshooting, model availability, or cost analysis.

Design assessments that work across languages, avoid language-dependent cultural bias, support multilingual learners, and validate assessment equivalence across translations. Use when creating fair assessments for multilingual contexts. Activates on "multilingual assessment", "language-fair testing", or "assessment translation".

Create and maintain AgentV YAML evaluation files for testing AI agent performance. Use this skill when creating new eval files, adding eval cases, or configuring custom evaluators (code validators or LLM judges) for agent testing workflows.

数値の入出力バリデーション方針。関数の引数・戻り値の妥当性チェック規約を定義。test-writer, implement, reviewerの各観点で参照。

Generate and optimize meta titles and descriptions for therapy pages following NextStep's formula (Service + Location | Differentiator | NextStep Therapy). Creates 5 CTR-optimized variations under 60 chars, tests against SERP simulator, scores each for click-through potential. Use when user mentions "meta title", "meta description", "optimize for CTR", "improve SERP appearance", or provides page URL for SEO optimization.

Generate polished walkthrough videos from Playwright test suites. Runs thematically connected tests with video recording, creates title cards, slows footage for readability, and concatenates into a final demo video.

Generates comprehensive tests with balanced quality and speed

Introduce test-driven development to beginners with simple Flask/Sinatra test examples and TDD concepts

Apply testing patterns like AAA (Arrange-Act-Assert), mocking, fixtures, and parameterization for maintainable test suites

Dockerizes backend projects with auto-detection, latest base images via web search, Dockerfile generation, and Makefile with port override support.

Mocks APIs with Mock Service Worker including request handlers, server/browser setup, and testing integration. Use when mocking APIs in tests, developing without backend, or simulating network conditions.

Write failing tests before implementation (RED phase of TDD). Creates test file with test functions that fail because code doesn't exist yet. Use when starting TDD workflow or adding tests for new functionality.

Use when encountering any bug, test failure, or unexpected behavior - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions

Introduces property-based testing with proptest, helping users find edge cases automatically by testing invariants and properties. Activates when users test algorithms or data structures.

Expert guidance on statistical analysis methodologies and Monte Carlo simulation for fantasy football. Use this skill when selecting regression approaches, designing simulations, performing variance analysis, or conducting hypothesis tests. Covers regression types (OLS, Ridge, Lasso, GAMs), Monte Carlo frameworks, regression-to-mean analysis, and statistical best practices for player performance modeling.

Multi-stage deep investigation and reasoning for complex problems using PAL MCP. Use for architecture decisions, complex analysis, performance challenges, or when you need thorough reasoning. Triggers on complex problems requiring deep thought, hypothesis testing, or expert analysis.

Bootstraps complete backend with Apso, including API setup, database configuration, and testing. Triggers when user needs to create backend, setup API, or initialize server.

Reference and maintain the project's technology stack including frameworks, languages, databases, testing tools, and third-party services to ensure consistency across the codebase. Use this skill when making technology decisions, adding new dependencies, choosing appropriate tools or libraries, configuring build systems, setting up testing frameworks, or documenting the tech stack. Apply this skill when selecting which framework, library, or tool to use for a given task, when ensuring code follows the conventions of the chosen stack (React patterns, Python idioms, Rails conventions), when integrating third-party services, or when documenting technology choices in README or architecture documentation. This skill ensures all team members use consistent technologies, new additions align with existing stack decisions, technology choices are documented with rationale, and the project maintains coherent patterns rather than mixing conflicting approaches or frameworks.

Use to avoid critical testing mistakes. Five Iron Laws: Never test mock behavior, Never add test-only methods, Never mock without understanding, Always integration test, Always test error paths.

Official NestJS starter with modular architecture and Jest testing.