setup

Your task

Install claudefiles by reading the manifest and deploying everything to the target directory.

Step 1: Read the manifest

Read claudefiles.yaml in this repo root. It declares what gets installed and how.

Step 2: Ask install target

Ask the user:

• Global (recommended): Install to ~/.claude/ — available in all Claude Code sessions
• Local: Install to ./.claude/ in the current project only

Step 3: Detect platform

Determine if running on macOS or Linux to resolve the {{sound_player}} template variable:

• macOS → afplay
• Linux → aplay

uname -s

Step 4: Create target directories

mkdir -p <target>/skills
mkdir -p <target>/commands
mkdir -p <target>/sounds
mkdir -p <target>/hooks

Step 5: Copy files

Copy the contents declared in install.targets.

Skills come with one exception: any skill directory named in an experimental feature's skills: list (e.g. tower) is opt-in and is copied in Step 8.5 only if the user enables that feature. Collect those names from the manifest first, then copy everything else:

# Skills — copy each skill directory, skipping opt-in skills declared under
# experimental.features[].skills (space-separated; taken from the manifest)
OPT_IN_SKILLS="<experimental.features[].skills, space-separated>"
for src in skills/*/; do
  name=$(basename "$src")
  case " $OPT_IN_SKILLS " in *" $name "*) continue ;; esac
  case "$name" in prune_*) continue ;; esac   # marked for deletion, never installed
  cp -R "$src" <target>/skills/
done

# Commands — copy all .md files
cp commands/*.md <target>/commands/

# Sounds — copy all files
cp sounds/* <target>/sounds/

# Hooks — copy all hook scripts and make executable
cp hooks/* <target>/hooks/
chmod +x <target>/hooks/*

Step 6: Deploy nvim plugin overlays (skip per-file if exists)

Overlay dotfiles/nvim/lua/plugins/ onto ~/.config/nvim/lua/plugins/. The nvim_plugins target in the manifest has skip_if_exists: true at the file level — never overwrite an existing plugin file the user already customized.