compound-docs

Generate categorized Markdown files with YAML frontmatter for solved problems.

2|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/CristoVentures/LocalCents --skill compound-docs-cristoventures
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compound-docs
Source: https://github.com/CristoVentures/LocalCents/tree/main/.agent/skills/compound-docs
Command: npx skills add https://github.com/CristoVentures/LocalCents --skill compound-docs-cristoventures

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

After a solution is confirmed, this skill captures it as categorized, YAML-frontmatter documentation to enable fast lookup and cross-reference across projects.

Core Features & Use Cases

  • Automatically generate a structured Markdown file per solved problem, including YAML frontmatter metadata.
  • Organize docs under category directories (docs/solutions/<category>) for easy navigation and discovery.
  • Support cross-referencing and pattern detection to identify recurring solutions across sessions.

Quick Start

Document a solved problem by generating a categorized Markdown file with YAML frontmatter.

Frequently Asked Questions about compound-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document solved problems with YAML frontmatter for fast lookup?

Document solved problems by generating categorized Markdown files with structured YAML frontmatter containing metadata like module, root_cause, and severity, enabling fast lookup across project directories.

What's the best way to organize solution documentation into a searchable knowledge base?

Organize solution documentation into a searchable knowledge base by saving each resolved issue as an individual Markdown file under category directories like docs/solutions/<category> for straightforward navigation and cross-referencing.

Can I detect recurring issues across projects using categorized Markdown documentation?

Yes, you can detect recurring issues across projects because the structured YAML frontmatter and category-based directory organization support cross-referencing and pattern detection across multiple sessions.

When do I need YAML frontmatter in Markdown documentation?

You need YAML frontmatter in Markdown documentation when you want to enforce structured metadata for solved problems, allowing you to quickly filter and cross-reference issues by attributes like component or problem_type.