What problem does it solve? Valuable lessons learned during debugging, feature implementation, and design discussions are often lost between sessions, forcing developers and AI assistants to rediscover the same patterns and repeat the same mistakes. This Skill preserves that knowledge as executable code-specs in the .trellis/spec/ directory. ## Core Features & Use Cases - Executable Contract Capture: Records concrete signatures, request/response fields, environment keys, and validation/error matrices rather than vague principles. - Structured Update Workflow: Guides classification of learnings into design decisions, conventions, patterns, anti-patterns, common mistakes, and gotchas with ready-to-use Markdown templates. - Code-Spec vs Guide Distinction: Enforces correct placement of content between layer-specific spec files and thinking-checklist guides. - Use Case: After fixing a subtle cross-layer API bug, run this Skill to document the contract, error matrix, and a wrong-vs-correct example so future sessions implement it safely. ## Quick Start Update the code-spec to capture the validation contract and error handling pattern we just implemented for the backend API.
