單元測試

Fetch the latest, docs-grounded API details and best practices for a library/framework using Context7 MCP tools `resolve-library-id` and `get-library-docs`. Use when a user asks for “最新用法/最新寫法/最佳實務/latest usage/current best practice/latest API” of a package, or asks how to implement a feature with a library and wants the newest docs-based guidance.

Master of the Watch - Testing commander and quality gate guardian

Follow project-wide development conventions including project structure, documentation standards, version control practices, environment configuration, and dependency management. Use this skill when organizing files and directories, writing README documentation, creating commit messages, managing environment variables, updating dependencies, or establishing code review processes. Apply this skill when ensuring consistent project structure (src/, components/, utils/, tests/), maintaining up-to-date documentation, using clear commit messages and feature branches, properly configuring environment variables without committing secrets, keeping dependencies minimal and documented, and implementing feature flags for incomplete work. This skill ensures the entire team follows predictable patterns for project organization, maintains comprehensive documentation for setup and architecture, practices good version control hygiene, manages configuration securely, and establishes clear workflows for testing and code review.

Unified UI development combining Anthropic's frontend-design plugin (anti-AI-slop aesthetics) with CIPS mobile-responsive-ui (dvh units, touch targets, testing protocol). Produces distinctive, production-grade, responsive interfaces.

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

ALWAYS use this skill when users ask to create, generate, or write UNIT TESTS for BigQuery SQL queries. Invoke proactively whenever the request includes "test" or "tests" with a query/table name. This skill is for unit testing ONLY (not data quality checks - use bigconfig-generator for Bigeye monitoring). Works with bigquery-etl-core skill to understand query patterns.

Use this skill when implementing, modifying, or fixing the admin dashboard (admin-dashboard-v2). Triggers for tasks involving dashboard UI, components, pages, features, hooks, or API integration. Orchestrates a rigorous QA workflow with PM review, use case writing, testing, and bug fixing cycles.

Kotlin/Spring Boot 백엔드 테스트 코드를 생성하는 스킬. 사용자가 "백엔드 테스트 작성해 줘", "서비스 테스트 만들어 줘", "컨트롤러 테스트 생성해 줘" 등의 요청을 할 때 사용합니다. JUnit 5, MockK, Spring Boot Test를 활용한 단위/통합 테스트를 생성합니다.

This skill should be used when developers need to scaffold complete decentralized applications on pod network, including smart contracts, Rust CLI tools, web frontends (React + Vite + viem), and testing infrastructure. Use when starting new DApps, building full-stack applications, or needing end-to-end project setup. Orchestrates pod-templating MCP server, frontend templates, and development tools for comprehensive DApp creation.

This skill enables honest, pressure-tested feedback on ideas, decisions, and proposals. Use this skill when prompted for an opinion on whether something is a good idea, should be done, or what to think about an approach.

Test SNARK submissions with sample data. Use when testing proof submission, validating the API, verifying SNARK operations work correctly, or debugging proof handling.

Guide for creating Claude Code hooks in the liv-conventions plugin. This skill should be used when users want to create a new hook to validate, block, or guide Claude's tool usage (Write, Bash, Edit, etc.). Covers the HookHandler pattern, PreToolUseInput/Response APIs, glob matching, plugin.json configuration, and testing.

GitHub Actions and CI/CD patterns for Databricks, including automated testing, deployment, and quality gates.

Use PROACTIVELY when reviewing CLAUDE.md configurations, onboarding new projects, or before committing memory file changes. Validates against official Anthropic documentation, community best practices, and LLM context optimization research. Detects security violations, anti-patterns, and compliance issues. Not for runtime behavior testing or imported file validation.

Verify test execution by replaying trajectory and checking script coverage.Ensures tests actually happened as recorded and scripts cover all test cases.WHEN TO USE:- After tests claim to pass (verify they actually ran)- Before marking ticket complete (audit trail)- When reviewing someone else's work- User says "validate", "verify tests", "check coverage"- Periodic audit of test integrityCHECKS:1. TRAJECTORY - Steps match recorded actions2. EVIDENCE - Screenshots, logs, outputs exist3. COVERAGE - Scripts test all cases from 3-spec.md4. COMPLETENESS - All required tests have trajectory

Implements new modules, agents, or features using TDD methodology. Used when adding any new functionality to the table2image multi-agent system. Follows six-phase workflow: context loading, test writing, implementation, verification, documentation, and protocol completion.

Track prompt versions, A/B test variants, and measure prompt performance

Expert for building user stories using Test-Driven Development (TDD) with NestJS and @lenne.tech/nest-server. Implements new features by creating story tests first in tests/stories/, then uses generating-nest-servers skill to develop code until all tests pass. Ensures high code quality and security compliance. Use in projects with @lenne.tech/nest-server in package.json dependencies (supports monorepos with projects/*, packages/*, apps/* structure).

Run automated accessibility tests on URLs or HTML content using axe-core engine to WCAG 2.2 AA standards, then format findings as standardized issue reports. Use this skill when users want to test website accessibility, find WCAG violations, audit pages for accessibility issues, check if sites are accessible, analyze HTML for accessibility problems, or create accessibility issue tickets. Triggers on requests like "test accessibility", "check for WCAG violations", "audit this URL", "is this page accessible", "find accessibility issues", or "write accessibility issues".

あらゆる言語/スタックで潜在バグリスクを洗い出し、追加すべきテストケースを提案する。未テストのエッジケース探索や安全性確認、カバレッジ強化のテスト案提示を求められたときに使用する。