oliver-kriska/claude-elixir-phoenix / plugins/elixir-phoenix/skills/compound
compound
VerifiedCapture solved problems as searchable solution docs. Use after fixing bugs, when "that worked", or after successful /phx:review or /phx:investigate.
Compound — Capture Solutions as Knowledge
After fixing a problem, capture the solution as searchable institutional documentation.
Usage
/phx:compound Fixed N+1 query in user listing
/phx:compound Resolved LiveView timeout in dashboard
/phx:compound # Auto-detects from recent session context
Philosophy
Each unit of engineering work should make subsequent units easier — not harder.
Workflow
Step 1: Detect Context
- If
$ARGUMENTSprovided, use as description - If no args, check scratchpad DEAD-END/DECISION entries,
git diff,.claude/plans/{slug}/progress.mdfor recent completions - If unclear, ask: "What problem did you just solve?"
Only document non-trivial problems that required investigation.
Step 2: Search Existing Solutions
Create .claude/solutions/ directory if it doesn't exist (run mkdir -p .claude/solutions).
Then search .claude/solutions/ for relevant keywords using Grep.
If found: Create new (different root cause), Update existing (same root cause, new symptom), or Skip.
Step 3: Gather Details and Create Solution
Extract from session context: module, symptoms, investigation steps, root cause, solution code, and prevention advice.
Validate frontmatter against ${CLAUDE_PLUGIN_ROOT}/skills/compound-docs/references/schema.md,
then create file using ${CLAUDE_PLUGIN_ROOT}/skills/compound-docs/references/resolution-template.md.
Write-blocked fallback: if writing to .claude/solutions/ is denied
by permissions, do NOT silently drop the solution. Output the full
solution doc inline (fenced markdown the user can paste), then suggest
/phx:permissions to allow .claude/solutions/ writes for next time.
Step 4: Decision Menu
- Continue (default)
- Promote to Iron Law check — Add to iron-law-judge
- Update skill reference — Add to relevant skill
- Update CLAUDE.md — Add prevention rule
Auto-Trigger Phrases
When user says "that worked", "it's fixed", "problem solved",
"the fix was" — suggest /phx:compound.
Supply-chain finding auto-feed (Phase 3)
When /phx:deps-audit produces a BLOCK-severity finding that the
user investigates and confirms is a real malicious pattern (not a
false positive), suggest:
Caught a high-severity finding in
<pkg>@<version>. Run/phx:compoundto capture this for future audits?
If accepted, the resulting solution doc goes to
.claude/solutions/supply-chain/<pkg>-<cve_or_pattern>.md and
includes the exact rule-id + snippet + diff window that triggered
the finding. This compounds the audit corpus: future runs of
/phx:deps-audit grep solutions/supply-chain/ for snippet
matches and pre-elevate severity on known-bad patterns.
Always prompt; never auto-write. Solution docs are durable and shape future trust calls — the user reviews before committing.
Iron Laws
- YAML frontmatter validates or STOP
- Symptoms must be specific — not "it broke"
- Root cause is WHY, not WHAT
- One problem per file
- NEVER document a fix before verifying it works — run
mix compile && mix testfirst; unverified solutions poison the knowledge base
Integration with Workflow
/phx:review → Complete → /phx:compound ← YOU ARE HERE
│
.claude/solutions/{category}/{fix}.md
│
/phx:investigate and /phx:plan search here
References
${CLAUDE_SKILL_DIR}/references/compound-workflow.md— Detailed step-by-step- See also:
compound-docsskill for schema and templates
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 467k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 196k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |