What problem does it solve? Valuable coding patterns, library usage knowledge, and operational tricks discovered during development are easily forgotten or lost. This Skill captures them as structured, searchable prescriptive documents so the team can reuse proven solutions instead of rediscovering them. ## Core Features & Use Cases - Three Document Types: Classifies each entry as pattern (design/architecture idioms), library (framework API usage and pitfalls), or technique (commands and operational recipes). - Mandatory Code Investigation: Searches the repository for real code examples before drafting, ensuring every trick is grounded in actual project code rather than abstract descriptions. - Overlap Detection and Updates: Checks existing entries before creating new ones, supporting update and supersede workflows with dated frontmatter. - Use Case: After figuring out the correct way to handle Pinia store action errors, ask the assistant to record it; it investigates the codebase, drafts a structured trick document with real code examples, and archives it under codestable/compound/ for future retrieval. ## Quick Start Tell the assistant to record a trick about the library usage or pattern you just validated, and answer its follow-up questions about when it applies and why it works.
