What problem does it solve? Valuable lessons from debugging, feature implementation, and design discussions are often lost between sessions, forcing developers and AI agents to rediscover the same contracts, conventions, and pitfalls repeatedly. ## Core Features & Use Cases - Executable Contract Capture: Records concrete signatures, request/response fields, environment keys, and validation/error matrices into .trellis/spec/ documents rather than vague principles. - Spec vs Guide Classification: Distinguishes code-specs (how to implement) from guides (what to think about) so knowledge lands in the correct location. - Structured Update Templates: Provides ready-made templates for design decisions, conventions, patterns, forbidden patterns, common mistakes, and gotchas. - Use Case: After fixing a subtle cross-layer API bug, use this Skill to document the corrected request contract, error matrix, and a wrong-vs-correct example so future sessions never repeat the mistake. ## Quick Start Ask the AI to update the relevant .trellis/spec/ document with the contract and lessons learned from the task you just completed.
