Does it document every minor fix?

No, the skill is designed to skip trivial issues like typos and simple syntax errors, focusing on non-obvious solutions that provide future value.

How does Compound Docs trigger?

It automatically detects confirmation phrases like 'that worked' or 'it's fixed,' and can also be manually invoked using the /doc-fix or /compound commands.

Where is the documentation stored?

Solutions are saved as Markdown files within a structured 'docs/solutions/' directory, organized automatically by problem category.

Can I customize the problem categories?

Yes, categories are managed via a schema.yaml file using enums to ensure all documentation remains consistent and searchable.

What is the Required Reading feature?

It allows users to promote critical patterns to a central 'Required Reading' file that Claude reviews before generating code, ensuring foundational rules are followed.

Compound Docs

Name: Compound Docs
Author: Folly-Partners

byFolly-Partners

학습 및 문서화

Captures and organizes verified problem solutions into a searchable institutional knowledge base with structured YAML metadata.

소개

Compound Docs is a specialized documentation skill for Claude Code that automates the creation of 'resolution briefs' once a problem is solved. It extracts critical technical context—including symptoms, root causes, and verified fixes—and stores them in a categorized directory structure with strict YAML frontmatter validation. By transforming ephemeral troubleshooting sessions into durable, searchable documentation, this skill helps development teams build a robust institutional memory that prevents the recurrence of similar bugs and streamlines future AI-assisted coding sessions.

주요 기능

Strict YAML schema validation ensuring consistent metadata and categorization
Built-in cross-referencing and pattern detection for recurring technical issues
Automated directory management and file naming based on problem context
0 GitHub stars
Interactive decision menu to promote critical solutions to 'Required Reading'
Automatic invocation via confirmation phrases like 'problem solved' or 'it's fixed'

사용 사례

Building a searchable technical wiki of 'lessons learned' during complex debugging
Creating foundational 'Required Reading' patterns to guide AI code generation
Standardizing documentation for bug resolutions and technical debt across a team

소개

주요 기능

Strict YAML schema validation ensuring consistent metadata and categorization
Built-in cross-referencing and pattern detection for recurring technical issues
Automated directory management and file naming based on problem context
0 GitHub stars
Interactive decision menu to promote critical solutions to 'Required Reading'
Automatic invocation via confirmation phrases like 'problem solved' or 'it's fixed'

사용 사례

Building a searchable technical wiki of 'lessons learned' during complex debugging
Creating foundational 'Required Reading' patterns to guide AI code generation
Standardizing documentation for bug resolutions and technical debt across a team