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 preserves that knowledge as executable code-specs with concrete signatures, contracts, and test requirements. ## Core Features & Use Cases - Executable Contract Capture: Records command/API signatures, request/response fields, environment keys, and validation error matrices rather than abstract principles. - Spec vs Guide Classification: Routes content to layer-specific spec files for implementation rules or guides/ checklists for thinking prompts. - Structured Update Templates: Provides ready-made templates for design decisions, conventions, patterns, anti-patterns, common mistakes, and gotchas. - Use Case: After fixing a subtle cross-layer API bug, use this Skill to document the correct request contract, error matrix, and a wrong-vs-correct example in the relevant .trellis/spec/ file so future sessions avoid the same mistake. ## Quick Start Update the relevant code-spec in .trellis/spec/ with the validation rules and error handling pattern we just discovered while fixing the API bug.
