Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →davekilleen/compound-docs
Capture solved problems as categorized documentation with YAML frontmatter for fast lookup
Passed 15 of 19 test cases with the skill, and 8 of 19 without it.
and 5 more in the full report
8 fixed9 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
We documented a fix for Hotwire Native Tailwind variant styling in docs/solutions/ui/tail-var.md. What option from our post-documentation choices allows us to link this documentation directly into the resources reference file of an existing learning skill?
| Checked | Without skill | With skill |
|---|---|---|
| Selects Option 4 as Add to existing skill. | Missed | Passed |
The instructions your model reads when the skill loads.
Purpose: Automatically document solved problems to build searchable institutional knowledge with category-based organization (enum-validated problem types).
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">
Auto-invoke after phrases:
OR manual: /doc-fix command
Non-trivial problems only:
Skip documentation for:
test cases passed, vs 8 / 19 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.