Setup
Prerequisitesβ
- Claude Code
- Node, for skills with scripts
gh, logged in, for/pr
Installβ
Clone the repo next to your project repos, then run setup from inside each project repo you work in:
git clone git@github.com:birdygrey/claude.git
cd hydrogen-storefront
bash ../claude/setup.sh
setup.sh is safe to re-run. It skips anything already linked.
| In the project repo | What setup does |
|---|---|
.claude/skills | Links the whole skills/ folder |
.claude/rules/*.md | Links each shared rule, unless the repo has its own file of that name |
.claude/rules/architecture.md | Creates an empty one if missing. This file belongs to the project repo |
.claude/settings.json | Links the shared permission allowlist, unless the repo has its own |
.mcp.json | Links the Playwright MCP config, unless the repo has its own |
.gitignore | Adds the linked paths |
It also installs Node dependencies for each skill that has them.
Keysβ
Some skills need a .env in their own folder in the claude repo. Copy the .env.example and fill it in. Setup lists the ones still missing.
| Skill | Needs |
|---|---|
ticket, epic | A Linear personal API key |
triage | The Birdy Bot URL and API key |
Updatingβ
cd claude && git pull
Linked repos pick up the change straight away. Re-run setup.sh only when a new skill adds dependencies or a new shared rule is added.