單元測試

Expert guidance for writing professional Python code following industry best practicesincluding PEP 8 compliance, testing, type hints, error handling, and modern tooling.Use this skill when writing new Python code, refactoring existing code, setting upPython projects, implementing tests, or ensuring code quality and maintainability.Emphasizes: PEP 8, modularity, DRY principle, TDD, virtual environments (uv),and modern tooling (Ruff, Black, Mypy).

Use when writing tests, validating features, or tempted to use mocks - enforces scenario-driven end-to-end testing with real dependencies; mocks are lies that hide bugs; scenarios with real data are the only source of truth

Browser automation skill for Lovable deployments. Activates when:- yolo_mode: on in CLAUDE.md- Running /deploy-edge or /apply-migration commands- After git push when auto_deploy: on (automatic detection)- Any mention of "yolo mode", "automate Lovable", "browser automation"Automatically navigates to Lovable.dev and submits deployment prompts.Runs verification tests based on configuration.Auto-deploys after git push when enabled.

Code review checklist for SwiftUI and Swift PRs. Use when reviewing pull requests, checking code quality, verifying Swift/SwiftUI implementations, or conducting PR reviews. Provides prioritized checklist covering state management, performance, component design, data flow, async handling, UI/UX, accessibility, security, and testing.

Reduce regressions by discovering tests, running them, then editing code

A skill with nested file structure for testing

Fetch raw ADF JSON data from a Confluence page URL. Use this skill when you need to see real-world ADF examples, understand how Confluence represents specific elements, debug ADF parsing, or create test samples.

Analyze OSS-Fuzz incremental build and JVM RTS (Regression Test Selection) test logs. Use when user mentions RTS logs, test failures, build failures, log analysis, or when working with *.log files from JVM RTS tests. Extracts errors, failed test classes, and categorizes issues.

Performs critical code reviews with a skeptical mindset, assuming the author cannot be fully trusted. Evaluates code quality, architecture, testing, requirements, and production readiness. Use after completing significant code changes or before merging.

Apply Lean Startup methodology for validated learning. Guides Build-Measure-Learn cycles, MVP definition, hypothesis testing, and pivot/persevere decisions.

RSpec testing patterns for Ruby and Rails. Use when writing tests, reviewing test code, or discussing testing strategy. Covers structure, naming, matchers, and external service stubbing.

This skill should be used when performing any coding task including implementing features, fixing bugs, refactoring code, or making any modifications to source code. Provides best practices, security considerations, testing guidelines, and a structured workflow for development tasks.

Identify and flag unnecessary test artifacts and temporary files in pull requests. Use when reviewing pull requests to ensure only production-relevant files are committed.

Ensures code quality through comprehensive checks including TDD practices, lint/test/build validation, and prevention of common mistakes. Use after completing implementations, fixing bugs, refactoring, or before committing code.

Execute and manage Rust tests including unit tests, integration tests, and doc tests. Use when running tests to ensure code quality and correctness.

Property-based testing for functor laws, monad laws, and naturality conditions using fp-ts and fast-check. Use when validating categorical implementations in TypeScript, testing algebraic laws in functional code, verifying functor/monad/applicative instances, or building test suites for categorical abstractions.

Systematic approach to implementing new features in the Rust memory system following project conventions. Use when adding new functionality with proper testing and documentation.

Core documentation generation patterns and framework for Treasure Data pipeline layers. Provides shared templates, quality validation, testing framework, and Confluence integration used by all layer-specific documentation skills.

Create a test plan mapping EARS requirements and Critical Constraints to specific tests

Comprehensive Rust backend development guide for Tauri applications. Use when creating Tauri commands, database operations, error handling, state management, or async patterns. Covers layered architecture (commands → services → operations → database), Result-based error handling, SeaORM patterns, tokio async/await, testing with cargo test, and type-driven design principles.