1.5천건 · 관련도순
Use when implementing features or fixing bugs with strict Test-Driven Development (TDD). Activate for coding tasks that require new functionality, refactoring, or comprehensive test coverage, especially when the user mentions TDD or Test Driven Development.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when adding or repairing Spark regression tests for asynchronous ownership, cancellation, persistence, restart recovery, or cross-surface projections. Not a coverage campaign, performance benchmark, source-text policy check, or full delivery review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Proves a Godot 4.x build is actually green and holds its project conventions. Trigger when a GUT or GDScript result needs believing (a suite green while a script failed to parse, a one-file run that ran the whole suite, drifted CI guard counts, a coverage claim, a gate figure, a failing check someone wants softened); to review scenes, signals, awaits, threads, determinism, saves, imports or .uid files, or the upgrade rule (not the migration); to prove a simulation or balance rule; for import settings and the pixel-art render precondition; or say godotsmith (check, guard, gate, review, intake). API reference is the Godot docs'; art reads pixelsmith's; audio direction soundsmith's.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when adding or repairing Spark regression tests for asynchronous ownership, cancellation, persistence, restart recovery, or cross-surface projections. Not a coverage campaign, performance benchmark, source-text policy check, or full delivery review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[60] VALIDATE. Ensure new (staged and unstaged) changes are covered by tests at >70% and the full test suite is green. Use when asked to validate coverage for recent changes, add tests for modified code, or verify nothing else broke.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[51] EXECUTE. Commitment to maximum quality work with 150% coverage. Use when you need the highest quality output for critical tasks, complex problems, important decisions, or when standard work isn't enough. Triggers on "maximum quality", "150% mode", "full quality", "critical task", or when you explicitly want AI to work at its best.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Python testing strategies using pytest, TDD methodology, fixtures, mocking, parametrization, and coverage requirements.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Kotlin testing patterns with Kotest, MockK, coroutine testing, property-based testing, and Kover coverage. Follows TDD methodology with idiomatic Kotlin practices.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Perl testing patterns using Test2::V0, Test::More, prove runner, mocking, coverage with Devel::Cover, and TDD methodology.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Verification loop for Spring Boot projects: build, static analysis, tests with coverage, security scans, and diff review before release or PR.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Django testing strategies with pytest-django, TDD methodology, factory_boy, mocking, coverage, and testing Django REST Framework APIs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use only when writing/updating/fixing C++ tests, configuring GoogleTest/CTest, diagnosing failing or flaky tests, or adding coverage/sanitizers.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Verification loop for Django projects: migrations, linting, tests with coverage, security scans, and deployment readiness checks before release or PR.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Local-first insurance record organizer for tracking policies, renewals, claims logs, and related insurance records. Use when the user wants to store policy details, list recorded policies, track renewal dates, log claim events, or summarize insurance records. NEVER provides insurance advice, recommends coverage amounts, or facilitates policy purchases.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Test and assure quality — test plan, QA, coverage, unit test, integration test, end-to-end, performance, benchmark, regression. Applies TDD and FIRST principles for the CTO office's tester.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run a bounded, governed iteration — "loop", "iterate until", "keep going until", "sweep", "ratchet", "until it passes", "coverage to 100". Turns an open-ended autonomous run into a finite loop with checkpoints and explicit stopping conditions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Creates an integration testing plan for .NET data access artifacts during Oracle-to-PostgreSQL database migrations. Analyzes a single project to identify repositories, DAOs, and service layers that interact with the database, then produces a structured testing plan. Use when planning integration test coverage for a migrated project, identifying which data access methods need tests, or preparing for Oracle-to-PostgreSQL migration validation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Launch new products from idea to first customers. Use when launching products, finding early adopters, building launch week playbooks, diagnosing why adoption stalls, or learning that press coverage does not equal growth. Includes the three-layer diagnosis, the 2-week experiment cycle, and the launch that got 50K impressions and 12 signups.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Creates integration test cases for .NET data access artifacts during Oracle-to-PostgreSQL database migrations. Generates DB-agnostic xUnit tests with deterministic seed data that validate behavior consistency across both database systems. Use when creating integration tests for a migrated project, generating test coverage for data access layers, or writing Oracle-to-PostgreSQL migration validation tests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze a failing test or design the right test coverage for a change
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Add focused Bun unit tests for mission-critical behavior and edge cases — not blanket coverage.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
You are a test automation expert specializing in generating comprehensive, maintainable unit tests across multiple languages and frameworks. Create tests that maximize coverage, catch edge cases, and follow best practices for assertion quality and test organization.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.