單元測試

Property-based testing with clojure.test.check. Use when writing generative tests, creating custom generators, or debugging shrinking behavior. Triggers on test.check imports, prop/for-all, gen/* usage, or questions about property-based testing in Clojure.

Teaches testing custom hooks in React 19 using renderHook from React Testing Library. Use when testing custom hooks or hook behavior.

Pattern for testing your own code during implementation. Ensures quality before declaring complete.

Run WaveCap-SDR test harness with automated parameter sweeps and validation. Use when regression testing, validating audio quality across configurations, testing SDR hardware, or benchmarking demodulation performance.

Generate unit tests, integration tests, and test fixtures for code. Supports Jest, Mocha, pytest. Use when writing tests or improving test coverage.This skill provides automated test generation:- Unit tests with AAA pattern (Arrange, Act, Assert)- Integration tests for APIs and databases- Test fixtures and mocks- Edge case identification- Test coverage recommendationsTriggers: "generate tests", "create unit test", "add test coverage", "write tests", "テスト生成", "テストコード作成", "カバレッジ向上"

Validates that code actually works through sandbox testing, execution verification, and systematic debugging. Use this skill after code generation or modification to ensure functionality is genuine rather than assumed. The skill creates isolated test environments, executes code with realistic inputs, identifies bugs through systematic analysis, and applies best practices to fix issues without breaking existing functionality. This ensures code delivers its intended behavior reliably.

Standards for maintaining high code quality including comments, test coverage, and documentation practices

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

Python coding standards, best practices, type hints, and testing patterns with uv for package management. Use when writing or reviewing Python code, implementing tests, setting up Python projects, managing dependencies with uv, working with virtual environments, adding type hints, writing pytest tests, or discussing Python language features and best practices.

Guides developer verification before handoff. Use when completing implementation, preparing for acceptance testing, or self-reviewing work before commit or PR.

Expert coding agent for this codebase. Learns from every session to improvecode quality, catch edge cases, and apply proven patterns. Use for ANY codingtask: writing, debugging, refactoring, testing. Accumulates project knowledge.

Extract text, fill forms, merge PDFs. Use when working with PDF files, forms, or document extraction. Requires pypdf and pdfplumber packages.

This skill should be used when the user asks to "create lwc component", "lightning web component", "component architecture", "lwc state management", "lwc testing", "jest test", or mentions container/presentational patterns, pub-sub, or LWC best practices.

Research-driven design methodology producing unique, context-appropriate frontends. Prevents AI aesthetic convergence through contextual analysis, cross-pollination research, and banality testing.

Activate when users ask about Claude Code installation, slash commands (/cook, /plan, /fix, /test, /docs, /design, /git), creating/managing Agent Skills, configuring MCP servers, setting up hooks/plugins, IDE integration (VS Code, JetBrains), CI/CD workflows, enterprise deployment (SSO, RBAC, sandboxing), troubleshooting authentication/performance issues, or advanced features (extended thinking, caching, checkpointing).

Beads (bd) issue workflow and repo operations for markdowntown. Use when creating bd tasks, updating status, adding dependencies, running required tests, committing, and pushing to main.

Async testing patterns with pytest-asyncio. Use when writing tests, mocking async code, testing database operations, or debugging test failures.

Right-side-of-V verification/validation orchestration for a change or PR.Produces a single Quality Gate Report with evidence covering: code review,security audit, performance regression risk, requirements traceability,acceptance/UAT scenarios, and (when UI changes) visual regression testing.Use when preparing a PR for merge/release, doing a “ready?” check, orenforcing an engineering quality gate.

Parses legacy requirement documents and generates a traceability matrix linking requirements to tasks, code, and tests. Enforces end-to-end traceability for the migration ensuring every work item maps back to formal documented requirements.

HTML documentation test