What problem does it solve? Hard-won knowledge about a codebase—gotchas, architectural rationale, and effective patterns—often gets lost after a feature ships, forcing future developers to rediscover the same pitfalls. This Skill enforces a disciplined practice of capturing and documenting those learnings alongside strict TDD workflow rules. ## Core Features & Use Cases - Learning Capture Framework: Prompts the question "What do I wish I'd known at the start?" after every significant change, with clear criteria for what deserves documentation. - Structured Documentation Format: Provides a consistent template for recording gotchas, patterns, anti-patterns, decisions, and edge cases with context, issue, and solution sections. - TDD Enforcement: Mandates a failing test before any production code, with refactoring assessment after mutation testing confirms test strength. - Use Case: After debugging a subtle API behavior where an endpoint returns null instead of an empty array, use this Skill to record the gotcha in project docs so the next developer avoids the same trap. ## Quick Start Ask the assistant to document this learning or record this gotcha after finishing a significant code change.
