compound

Captures solved problems as searchable markdown assets with YAML frontmatter in docs/solutions.

1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/psw7205/skills --skill compound-psw7205
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: compound
Source: https://github.com/psw7205/skills/tree/main/skills/compound
Command: npx skills add https://github.com/psw7205/skills --skill compound-psw7205

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Hard-won debugging insights disappear when a session ends, forcing you to re-solve the same problem later. This Skill compresses a just-solved problem into a searchable knowledge asset so the next occurrence is resolved with a single grep. ## Core Features & Use Cases - Four-axis extraction: Distills a session into problem, root cause, fix, and applies-to fields, prioritizing the root cause that diffs alone cannot reveal. - Searchable frontmatter schema: Writes YAML frontmatter with tags, applies-to, and related fields so files are discoverable via grep/rg by symptom keywords and stack identifiers. - Trigger and quality gates: Filters out trivial five-minute fixes, confirms slug and tags with the user before saving, and enforces a Patterns to Reuse section. - Use Case: After spending an hour diagnosing why React Native Metro logs went missing, save the root cause and fix to docs/solutions/2026-05-22-rn-metro-log-missing.md so the next session finds it instantly. ## Quick Start Save the problem we just solved as a reusable solution asset in docs/solutions with searchable tags.

Frequently Asked Questions about compound

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

FAQPage Schema
How do I save a debugging solution for future reuse?▼

Trigger the skill after solving a non-trivial problem and it extracts the problem, root cause, fix, and applicable stack into a markdown file under docs/solutions with YAML frontmatter. The file is searchable later with grep or ripgrep by tags and symptom keywords.

What is the difference between compound and session-history?▼

Compound captures one problem's solution pattern across four axes (problem, root cause, fix, applies-to) for grep-based reuse. Session-history records an entire session's decision narrative chronologically for handoff. Use compound for recurring problem patterns and session-history for full session context.

When should a problem not be saved as a solution asset?▼

Skip problems solved in under five minutes, self-explanatory fixes obvious from the diff, and issues with low recurrence probability. The skill's trigger step filters these out because storing trivial fixes creates noise rather than searchable assets.

How do I search saved solutions in docs/solutions?▼

Run rg -l 'tag-or-keyword' docs/solutions/ to find files by tag, or rg -n 'applies-to:' docs/solutions/ filtered by your stack. Slugs combine domain and symptom keywords so filenames themselves are searchable.

Why is root cause emphasized over the fix in solution files?▼

The fix is always visible in the git diff, but the root cause evaporates when the session ends. The asset's long-term value comes from the root cause and the Patterns to Reuse section, which tell future you where to look first when the symptom recurs.