Claude Skills

My personal Claude Code skills — drop-in prompts and playbooks for things I do often (React, Inertia, Laravel, …).

Install

./install.sh

On first run it scans ~/.claude/skills/ and offers to import any existing skills back into the repo. Then it symlinks everything in here into ~/.claude/skills/. Idempotent — re-run anytime; stale links and orphaned folders get cleaned up.

Layout

Two ways to add a skill:

A bare .md file — for simple, one-file skills. Group related ones in a folder.

inertia.md                -> ~/.claude/skills/inertia/SKILL.md
react/
├── hooks.md              -> ~/.claude/skills/react-hooks/SKILL.md
└── server-components.md  -> ~/.claude/skills/react-server-components/SKILL.md
laravel/
└── eloquent.md           -> ~/.claude/skills/laravel-eloquent/SKILL.md

A folder containing SKILL.md — for skills that ship extra files (scripts, references, assets). The whole folder gets symlinked.

today-recap/
├── SKILL.md              -> ~/.claude/skills/today-recap/  (whole folder linked)
└── reference.md

Rule: a folder with SKILL.md directly inside is a skill. A folder without is just for grouping.

Each file needs the standard skill frontmatter so Claude can discover it:

---
name: react-hooks
description: When to reach for which React hook, with examples. Use when writing or reviewing React components.
---

# React Hooks
…

The name should match the generated folder (<subfolder>-<filename> or just <filename> at the root).

Why?

Backup, version history, and an excuse to keep my prompts tidy.