How do I install the Phxcompound skill?

Run npx skillmds@latest add tomevault-io/phxcompound in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Phxcompound safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Phxcompound?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Phxcompound free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Phxcompound?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Phxcompound by tomevault-io — Agent Skill

Name: Phxcompound
Author: tomevault-io

File contents

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 $ARGUMENTS provided, use as description
If no args, check scratchpad DEAD-END/DECISION entries, git diff, .claude/plans/{slug}/progress.md for 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 compound-docs/references/schema.md, then create file using compound-docs/references/resolution-template.md.

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.

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 test first; 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-docs skill for schema and templates

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: phxcompounddescription: Capture solved problems as searchable solution docs. Use after fixing bugs, when "that worked", or after successful /phx:review or /phx:investigate. Use when this capability is needed.---# Compound — Capture Solutions as KnowledgeAfter fixing a problem, capture the solution as searchableinstitutional 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 Context1. If `$ARGUMENTS` provided, use as description2. If no args, check scratchpad DEAD-END/DECISION entries, `git diff`, `.claude/plans/{slug}/progress.md` for recent completions3. If unclear, ask: "What problem did you just solve?"**Only document non-trivial problems** that required investigation.### Step 2: Search Existing SolutionsCreate `.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), **Updateexisting** (same root cause, new symptom), or **Skip**.### Step 3: Gather Details and Create SolutionExtract from session context: module, symptoms, investigationsteps, root cause, solution code, and prevention advice.Validate frontmatter against `compound-docs/references/schema.md`,then create file using `compound-docs/references/resolution-template.md`.### Step 4: Decision Menu1. **Continue** (default)2. **Promote to Iron Law check** — Add to iron-law-judge3. **Update skill reference** — Add to relevant skill4. **Update CLAUDE.md** — Add prevention rule## Auto-Trigger PhrasesWhen user says "that worked", "it's fixed", "problem solved","the fix was" — suggest `/phx:compound`.## Iron Laws1. **YAML frontmatter validates or STOP**2. **Symptoms must be specific** — not "it broke"3. **Root cause is WHY, not WHAT**4. **One problem per file**5. **NEVER document a fix before verifying it works** — run `mix compile && mix test` first; unverified solutions poison the knowledge base## Integration with Workflow```text/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-docs` skill for schema and templates---> Converted and distributed by [TomeVault](https://tomevault.io/claim/oliver-kriska) — claim your Tome and manage your conversions.

Frequently asked questions

Phxcompound