Compound Documentation
Captures and organizes verified problem solutions into a searchable, categorized knowledge base using structured markdown and YAML frontmatter.
The compound-docs skill streamlines institutional knowledge building by automatically transforming solved technical issues into standardized documentation. Triggered by confirmation phrases or manual commands, it guides Claude through a rigorous 7-step process—from context gathering and YAML validation to cross-referencing existing entries. This ensures that tricky debugging sessions, non-obvious fixes, and root cause analyses are preserved in a consistent format, preventing the repetition of past mistakes and providing a 'Required Reading' layer for future development sessions.
Características Principales
01Cross-referencing and critical pattern detection for recurring issues
02Automated detection of successful fixes to prompt documentation capture
03Post-capture decision menu to promote entries to 'Required Reading' or new skills
04Strict YAML frontmatter validation for consistent metadata and searchability
05Categorized file organization based on enum-validated problem types
0681 GitHub stars
Casos de Uso
01Standardizing how teams document non-obvious solutions and technical debt
02Creating a 'lessons learned' database during major architectural migrations
03Building a searchable repository of complex bug fixes for large codebases