Personal configuration for Claude Code: agent guidelines, slash commands, subagents, language-specific skills, plugins, a Zig statusline, and a settings baseline. Designed to be usable as a standalone repo or as a submodule of a larger dotfiles tree.

Clone the repo anywhere, then run the installer to symlink runtime assets into ~/.claude/:

git clone https://github.com/alleneubank/claude-code.git ~/code/claude-code
cd ~/code/claude-code
./install.sh             # apply symlinks
./install.sh --check     # report drift without changing anything

The installer is idempotent. It links:

• CLAUDE.md → ~/.claude/CLAUDE.md (agent guidelines)
• commands/ → ~/.claude/commands/ (slash commands)
• agents/ → ~/.claude/agents/ (subagents)
• .claude/skills/ → ~/.claude/skills/ (best-practices skills)
• codex.json → ~/.claude/codex.json (Codex CLI config for the codex-reviewer plugin)

Settings, statusline binary, and plugins are opt-in — see the sections below.

claude-code/
├── CLAUDE.md                    # Agent guidelines (linked into ~/.claude/CLAUDE.md)
├── codex.json                   # Codex CLI defaults (linked into ~/.claude/codex.json)
├── install.sh                   # Idempotent symlink installer
├── commands/                    # Slash commands
├── agents/                      # Subagents
├── .claude/skills/              # Best-practices skills (auto-load by file context)
├── .claude-plugin/              # Marketplace manifest for the bundled plugins
├── plugins/                     # Source for plugins published via marketplace.json
│   ├── codex-reviewer/          # Codex CLI review gate
│   └── ralph-reviewed/          # Iterative loop with Codex review
├── codex-overrides/skills/      # Codex-only skill overrides applied during sync
├── settings/settings.json       # Settings baseline (copy or merge into ~/.claude/settings.json)
├── statusline/                  # Zig statusline (build separately, see below)
├── hooks/direnv-bash-env        # BASH_ENV shim that loads direnv on subshell cd
├── scripts/                     # Usage tracking, codex sync, plugin version checks
└── analytics/                   # Submodule: claude-code-analytics (transcript analyzer)

Invoked with /<name> in Claude Code. Sources live in commands/.

Custom subagents in agents/. Claude Code delegates automatically when their description matches the task.

Best-practices skills in .claude/skills/ are auto-loaded when the file context matches their triggers. The full set:

This repo also doubles as a Claude Code plugin marketplace via .claude-plugin/marketplace.json. Two plugins ship from it:

# Inside Claude Code:
/plugin marketplace add alleneubank/claude-code
/plugin install ralph-reviewed@0xbigboss-plugins
/plugin install codex-reviewer@0xbigboss-plugins

Or install from a local checkout:

/plugin marketplace add ~/code/claude-code

Both plugins read ~/.claude/codex.json for sandbox/approval/timeout settings — install.sh puts a default copy there. See plugins/ralph-reviewed/README.md for the full schema.

settings/settings.json is an opinionated baseline you can adopt as-is or use as a reference:

• permissions.allow pre-approves common read-only and safe-write Bash patterns (git, npm/bun/yarn, zig, go, tilt, kubectl, docker, gh) plus a few skills.
• extraKnownMarketplaces declares plugin marketplaces; enabledPlugins controls which are turned on.
• statusLine.command invokes the Zig statusline binary (see below).
• env.BASH_ENV points at hooks/direnv-bash-env so subshells reload direnv on cd.

This file ships with author-specific marketplace pointers (e.g. private Send/Canton repos) and a hard-coded BASH_ENV path. If you adopt it, edit those fields to match your machine. The simplest path is to copy it once and treat ~/.claude/settings.json as yours:

cp settings/settings.json ~/.claude/settings.json

The author personally generates ~/.claude/settings.json via a private merge helper in the surrounding dotfiles tree (baseline + ~/.claude/settings.local.json overrides). That helper is not required to use this repo — direct copy works fine.

A small Zig statusline lives in statusline/. It reads JSON on stdin and prints one formatted status line.

cd statusline
zig build -Doptimize=ReleaseFast
# binary lands at statusline/zig-out/bin/statusline

Point Claude Code at it by setting statusLine.command in ~/.claude/settings.json (the baseline already does this). Minimum Zig: 0.16.0. See statusline/CLAUDE.md and statusline/SPEC.md for build, runtime contract, and design notes.

scripts/ contains optional utilities:

See scripts/README.md for the usage-tracking specifics.

If you also use the Codex CLI and want the same skills/commands available there:

scripts/sync-codex.sh --check   # report drift (exit 0 clean, 2 drift, 1 error)
scripts/sync-codex.sh           # apply

Codex skill resolution order during sync:

1. User skills from .claude/skills/
2. Plugin skills (with selective drops per scripts/sync-codex.skill-policy.tsv)
3. Codex-only overrides from codex-overrides/skills/ (win on name collision)

analytics/ is a submodule that analyzes Claude Code transcripts (skill usage, token consumption, tool patterns).

git submodule update --init analytics
cd analytics && uv sync
uv run cc-analytics skills

• Shared agent guidelines live in CLAUDE.md at the repo root. The installer links this into ~/.claude/CLAUDE.md.
• Personal local notes belong in ~/.claude/CLAUDE.local.md (or this repo's CLAUDE.local.md, which is gitignored). Do not move local-only content into the tracked CLAUDE.md — it is meant to be shareable.

The author keeps this repo as a submodule of a private dotfiles tree. When present, that tree's codex/codex.json is preferred by install.sh over the in-repo sample, and a private claude-bootstrap / claude-settings-merge pair manages additional symlinks and the settings merge. Neither is required to use this repo standalone — everything in this README assumes no parent tree.

Allen Eubank (@alleneubank)

Licensed under the Apache License, Version 2.0. See LICENSE.