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。