What problem does it solve? Valuable lessons learned during debugging, feature implementation, or design discussions are often lost between sessions, forcing developers and AI agents to rediscover the same patterns and repeat the same mistakes. This Skill turns those learnings into persistent, executable code-spec documents. ## 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 (design decisions, patterns, anti-patterns, gotchas, common mistakes) and routes them to the correct spec file or thinking guide. - Mandatory 7-Section Template: Enforces Scope, Signatures, Contracts, Error Matrix, Good/Base/Bad cases, Tests, and Wrong-vs-Correct examples for infra or cross-layer changes. - Use Case: After fixing a subtle API error-handling bug, invoke this Skill to document the correct contract, the failure mode, and the required tests in the relevant .trellis/spec/ file so future sessions never repeat the mistake. ## Quick Start Ask the agent to update the code-spec with what was just learned from the completed task or bug fix.
