What problem does it solve? Valuable lessons from debugging sessions, feature implementations, and design discussions are often lost between sessions, forcing developers and AI assistants to rediscover the same patterns and mistakes. This Skill turns those learnings into persistent, executable code-spec documents. ## Core Features & Use Cases - Structured Spec Updates: Classifies learnings into design decisions, conventions, patterns, anti-patterns, common mistakes, and gotchas, each with a dedicated Markdown template. - Mandatory 7-Section Contract Format: Enforces signatures, request/response contracts, validation and error matrices, Good/Base/Bad cases, and required tests for infra or cross-layer changes. - Code-Spec vs Guide Separation: Directs concrete implementation rules into layer-specific spec files and thinking checklists into guides/ to keep documentation organized. - Use Case: After fixing a subtle bug in an API error-handling flow, use this Skill to document the root cause, the correct contract, and a Wrong vs Correct example in the relevant backend spec so future sessions avoid the same mistake. ## Quick Start Ask the assistant to update the relevant .trellis/spec document with what was just learned from the completed task or bug fix.
