Test-Driven Development (TDD)
A Skill that enforces Test-Driven Development methodology: write the test first, watch it fail, write minimal code to pass.
Core Principle
If you didn't watch the test fail, you don't know if it tests the right thing.
When to Use
Always:
- New features
- Bug fixes
- Refactoring
- Behavior changes
Exceptions (ask your human partner):
- Throwaway prototypes
- Generated code
- Configuration files
This Skill helps maintain code quality and ensures comprehensive test coverage.
Comments
No comments yet. Be the first to comment!
Related Tools
Subagent-Driven Development Skill
github.com/obra/superpowers
Execute plans by dispatching fresh subagent per task with two-stage review - spec compliance then code quality.
Systematic Debugging Skill
github.com/obra/superpowers
Always find root cause before attempting fixes - systematic approach to debugging any technical issue.
Verification Before Completion Skill
github.com/obra/superpowers
Evidence before claims - always run verification commands and confirm output before making completion claims.
Related Insights
Skills + Hooks + Plugins: How Anthropic Redefined AI Coding Tool Extensibility
An in-depth analysis of Claude Code's trinity architecture of Skills, Hooks, and Plugins. Explore why this design is more advanced than GitHub Copilot and Cursor, and how it redefines AI coding tool extensibility through open standards.
Claude Code's Next Frontier: Not Code, But Your Local Obsidian Knowledge Base
Explore how Obsidian + Claude Code transforms from a knowledge management tool into your private AI assistant. Complete guide including obsidian-skills, Claudian plugin, Claudesidian template, and best practices for achieving both data privacy and AI capabilities.
Anthropic Subagent: The Multi-Agent Architecture Revolution
Deep dive into Anthropic multi-agent architecture design. Learn how Subagents break through context window limitations, achieve 90% performance improvements, and real-world applications in Claude Code.