Claude Code skills

Skills are reusable prompt workflows stored as Markdown files in ~/.claude/skills/. Invoke any skill with /skill-name in a Claude Code session.

Installation

Copy a skill file to your global skills directory:

cp skills/brain-review/SKILL.md ~/.claude/skills/brain-review.md
cp skills/brainstorm/SKILL.md ~/.claude/skills/brainstorm.md
cp skills/bug-report/SKILL.md ~/.claude/skills/bug-report.md
cp skills/feature-change/SKILL.md ~/.claude/skills/feature-change.md
cp skills/frontend-skill/SKILL.md ~/.claude/skills/frontend-skill.md

Or install all at once:

for d in skills/*/; do
  name=$(basename "$d")
  cp "$d/SKILL.md" ~/.claude/skills/"$name".md
done

Note: qmd is not a skill — it’s a rule you add to CLAUDE.md and AGENTS.md so agents use it automatically. See qmd.

---

Available skills

brain-review

Keeps brain/ documentation aligned with the actual code after changes are implemented. Diffs the codebase against brain files and updates only the impacted sections.

Invoke: /brain-review
Use when: after implementing a feature or fix and wanting docs to stay current.

---

feature-change

Implements a requested app change end-to-end, validates it, then automatically calls brain-review with a focused change packet so documentation stays in sync.

Invoke: /feature-change
Use when: building a new feature or making a code change and wanting brain docs updated automatically.

---

brainstorm

Facilitates structured ideation: frames the goal, presents 2–4 options with tradeoffs, converges on a plan with your input, then hands off to feature-change for implementation.

Invoke: /brainstorm
Use when: you want to compare approaches before writing any code.

Flow: brainstorm → feature-change → brain-review

---

bug-report

Triages a bug report into a concrete fix plan: captures observed vs expected behavior, identifies reproduction steps, traces the code path, proposes fix options, and builds a handoff packet for feature-change.

Invoke: /bug-report
Use when: a user reports a crash, regression, or unexpected behavior and you want a structured root-cause before coding.

---

frontend-skill

Generates production-grade frontend interfaces with strong art direction: full-bleed heroes, restrained composition, deliberate motion, and utility copy for app surfaces.

Invoke: /frontend-skill
Use when: building a landing page, app UI, prototype, or any visually led interface.

---

Skill chaining

Skills can call each other. The typical chain for a feature with doc sync:

/brainstorm   →   /feature-change   →   /brain-review

For a bug with doc sync:

/bug-report   →   /feature-change   →   /brain-review

When qmd is configured via CLAUDE.md/AGENTS.md, all skills benefit from it automatically — Claude will use qmd for any context retrieval before reasoning or editing.