Compound Docs
Capture solved problems as categorized documentation with YAML frontmatter for fast lookup
Install
npx skills add ratacat/claude-skills --skill compound-docsgit clone --depth 1 https://github.com/ratacat/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/skills/compound-docs ~/.claude/skills/compound-docsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# compound-docs Skill **Purpose:** Automatically document solved problems to build searchable institutional knowledge with category-based organization (enum-validated problem types). ## Overview This skill captures problem solutions immediately after confirmation, creating structured documentation that serves as a searchable knowledge base for future sessions. **Organization:** Single-file architecture - each problem documented as one markdown file in its symptom category directory (e.g., `docs/solutions/performance-issues/n-plus-one-briefs.md`). Files use YAML frontmatter for metadata and searchability. --- <critical_sequence name="documentation-capture" enforce_order="strict"> ## 7-Step Process <step number="1" required="true"> ### Step 1: Detect Confirmation **Auto-invoke after phrases:** - "that worked" - "it's fixed" - "working now" - "problem solved" - "that did it" **OR manual:** `/doc-fix` command **Non-trivial problems only:** - Multiple investigation attempts needed - Tricky debugging that took time - Non-obvious solution - Future sessions would benefit **Skip documentation for:** - Simple typos - Obvious syntax errors - Trivial fixes immediately corrected </step> <step number="2" required="true" depends_on="1"> ### Step 2: Gather Context Extract from conversation history: **Required information:** - **Module name**: Which module or component had the problem - **Symptom**: Observable error/behavior (exact error messages)
Details
- Skill name
compound-docs- Repository
- ratacat/claude-skills
- Path
skills/compound-docs/SKILL.md- Repo updated
- 11 February 2026
FAQ
What does the Compound Docs skill do?
Capture solved problems as categorized documentation with YAML frontmatter for fast lookup
How do I install the Compound Docs skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add ratacat/claude-skills --skill compound-docs. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Compound Docs popular?
It lives in ratacat/claude-skills, which has 59 GitHub stars and 10 forks.
Related skills
Skill Creator
59ratacat/claude-skills
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.
Skill Installer
59ratacat/claude-skills
Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).
Agent Browser
59ratacat/claude-skills
Browser automation using Vercel's agent-browser CLI. Use when you need to interact with web pages, fill forms, take screenshots, or scrape data. Alternative to Playwright MCP - uses Bash commands with ref-based element selection. Triggers on "browse website", "fill form", "click button", "take screenshot", "scrape page", "web automation".
Every Style Editor
59ratacat/claude-skills
This skill should be used when reviewing or editing copy to ensure adherence to Every's style guide. It provides a systematic line-by-line review process for grammar, punctuation, mechanics, and style guide compliance.
Bd to Br Migration
59ratacat/claude-skills
Migrate docs from bd (beads) to br (beads_rust). Use when updating AGENTS.md, converting bd commands, "bd sync" → "br sync --flush-only", or beads migration.
Every Style Editor 2
59ratacat/claude-skills
Use this agent when you need to review and edit text content to conform to Every's specific style guide. This includes reviewing articles, blog posts, newsletters, documentation, or any written content that needs to follow Every's editorial standards. The agent will systematically check for title case in headlines, sentence case elsewhere, company singular/plural usage, overused words, passive voice, number formatting, punctuation rules, and other style guide requirements.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.