Skip to main content

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 repoWhat setup does
.claude/skillsLinks the whole skills/ folder
.claude/rules/*.mdLinks each shared rule, unless the repo has its own file of that name
.claude/rules/architecture.mdCreates an empty one if missing. This file belongs to the project repo
.claude/settings.jsonLinks the shared permission allowlist, unless the repo has its own
.mcp.jsonLinks the Playwright MCP config, unless the repo has its own
.gitignoreAdds 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.

SkillNeeds
ticket, epicA Linear personal API key
triageThe 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.