tdd

Universal principles for writing good tests. These apply regardless of framework, language, or repo — discover and follow your repo's specific testing tools, commands, and conventions from its project configuration, contributor guides, existing test files, CI/CD config, and any repo-level AI skills or rules.

Tests verify behavior through public interfaces, not implementation details. Code can change entirely; tests shouldn't break unless behavior changed.

Good tests exercise real code paths through public APIs. They describe what the system does, not how. A good test reads like a specification — "user can checkout with valid cart" tells you exactly what capability exists. These tests survive refactors because they don't care about internal structure.

通用的測試驅動開發方法和測試設計流程。 撰寫以行為為中心的測驗、模擬策略的背景知識， 垂直切片和曳光彈執行。編寫測試時自動加載 在實施、審查回饋或獨立測試創作期間。 觸發因素：編寫測試、測試設計、模擬策略、測試品質、 行為測試、整合測試、測試優先、紅綠重構。 來源：inkeep/team-skills。