Learn to implement minimal code that makes failing tests pass during TDD green phase. Avoid over-engineering and keep implementations simple.
スキルZIPをダウンロード
Claudeでアップロード
設定 → 機能 → スキル → スキルをアップロードへ移動
オンにして利用開始
テストする
「tdd-workflows-tdd-green」を使用しています。 I have a failing test for user creation. Help me implement minimal code.
期待される結果:
- Here's the minimal implementation using Fake It pattern:
- class UserService {
- create(data) {
- return { id: '123', ...data };
- }
- }
- This passes the test with a hard-coded ID. You can evolve to real ID generation when more tests require it.
「tdd-workflows-tdd-green」を使用しています。 Should I add error handling to this green phase implementation?
期待される結果:
- No - in green phase, only add what tests require. If tests don't check error scenarios, skip error handling for now.
- Add it during refactor phase when you have tests that validate error paths.
セキュリティ監査
安全All 105 detected patterns are false positives from code examples in educational documentation. The skill contains only instructional markdown content with code samples demonstrating TDD patterns. No executable code, scripts, or runtime behavior exists. The 'MD5', 'SHA1', 'SQLite', 'backticks', and 'fetch' patterns appear strictly within code blocks as teaching examples for proper TDD implementation across multiple programming languages.
品質スコア
作れるもの
Learning TDD Fundamentals
New developers learning test-driven development can use this skill to understand the green phase methodology and avoid common mistakes like over-engineering
Speeding Up Feature Implementation
Experienced developers can quickly implement minimal passing tests without getting bogged down in premature optimization during initial development
Team TDD Training
Development teams adopting TDD can use the structured patterns and examples to establish consistent green phase practices across the organization
これらのプロンプトを試す
Help me implement the minimal code needed to make these failing tests pass. Focus on simplicity and avoid over-engineering.
Show me how to implement minimal code for these tests using [JavaScript/Python/Java/C#/Go/Ruby]. Follow TDD green phase best practices.
Should I use a fake implementation or real implementation for these tests? Explain the trade-offs and recommend the best approach.
Review my implementation and tell me if it's truly minimal for the green phase or if I'm over-engineering. Suggest simplifications if needed.
ベストプラクティス
- Implement the absolute minimum code that makes tests pass - avoid adding features or optimizations not required by tests
- Run tests after each small change to verify progress and catch issues early
- Document technical debt and shortcuts taken during green phase for later refactoring
回避
- Gold plating - adding unrequested features or enhancements during green phase
- Premature refactoring - changing code structure while tests are still failing
- Implementing design patterns or architectural decisions before tests require them
よくある質問
What is the TDD green phase?
Should I fake it or implement real code?
Can I refactor during the green phase?
What if my implementation feels too simple?
Do I need to add error handling in green phase?
How do I know when green phase is complete?
開発者の詳細
作成者
sickn33ライセンス
MIT
リポジトリ
https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/tdd-workflows-tdd-green参照
main
ファイル構成