Loading...
Loading...
Found 107 Skills
テスト駆動開発（TDD）ワークフローを実行するスキル。 使用タイミング: (1) 新機能の実装開始時 (2) バグ修正時 (3) リファクタリング前 (4) 「テストから書いて」と言われた時 (5) 品質重視の実装が必要な時。 トリガー例: 「TDDで実装して」「テスト駆動で」「テストから書いて」 「RED-GREEN-REFACTORで」「UserServiceのテストを書いて」
Android Test-Driven Development standards. Enforces Red-Green-Refactor cycle, test pyramid (70/20/10), layer-specific testing strategies, and CI integration. Use when building or reviewing Android apps with TDD methodology.
Guiding principles for writing clear, concise, human readable and maintainable Python code.
Test-Driven Development methodology enforcing RED-GREEN-REFACTOR cycle. Use for writing tests first, preventing regression, and ensuring code correctness. Based on obra/superpowers.
Test-driven development workflow — write failing tests first, implement minimum code, run full suite, commit. Use when implementing features, fixing bugs, or adding test coverage. Includes mock bootstrap phase for projects with mockReset:true.
Agent testing methodology - run agents with test inputs, observe outputs, iterate until outputs are accurate and well-structured.
Applies TDD workflow to development. Use when writing tests before code, implementing features test-first, fixing bugs via failing test, or refactoring with test coverage. Detects AI anti-patterns.
Create Test Specifications (TSPEC) - Layer 10 artifact for unit, integration, smoke, and functional test cases
Test-driven development workflow with philosophy guide - plan → write tests → implement → validate
Use when implementing any code in RLM Phase 3. Enforces strict RED-GREEN-REFACTOR discipline with The Iron Law - no production code without a failing test first.
TDD Skill for Team Workflows (Phase 3). Before writing any implementation code, you must first write a failing test and verify the failure, then write the minimal implementation until it passes, and finally refactor and re-test.
Use this when encountering any errors, test failures, or unexpected behavior before proposing a fix