PRB's personal Claude Code config, mounted at ~/.claude.
git clone git@github.com:PaulRBerg/dot-claude.git ~/.claude
cd ~/.claude
just install
ccc # Make your first commit with the claude wrapperSee Installation for full setup and Configuration for customization.
- Node.js: Husky/lint-staged automation (
npm install) - Just: command runner for build scripts (
brew install just) - Python 3.13+ and uv: Python package/project manager
git clone git@github.com:PaulRBerg/dot-claude.git ~/.claude
cd ~/.claude
just install # Node deps, Python deps, and CLI utilitiesjust full-check # Run all code checks
just test-hooks # Run hook tests
claude # Run ClaudeAll JSONC files in settings/* merge into settings.json on commit via Husky + lint-staged.
Edit only settings/**/*.jsonc (never settings.json directly). Merging happens on commit, or run just merge-settings
manually.
Settings layout:
basics.jsonc: core config, env vars, status linehooks.jsonc: event hooksplugins.jsonc: enabled pluginspermissions/*.jsonc: permission rules (bash, mcp, read, write, tools)
CLAUDE.md is user-level context loaded by Claude Code across all projects. Keep repo-specific guidance in project
CLAUDE.md / AGENTS.md files; keep only durable personal workflow defaults here.
Append flags to prompts to trigger behavior:
-s: subagents-c: auto-commit-t: testing-d: debug-n: skip linting
Flags compose, e.g. implement API -s -t -c.
Use just for common tasks like just full-check, just merge-settings, and just test. See justfile for the full
command list.
commands/ contains thin entry points that invoke skills. Commands still matter because they support directory nesting,
which enables namespaced patterns like /yeet:issue-cc and /agents-context:brain-polish.
Skills are managed in PaulRBerg/dot-agents and installed via Vercel's
skills CLI. This repo keeps symlinks from skills/ to ~/.agents/skills/.
See dot-agents for installation guidance.
Examples: agents-context-management, commit, vitest, effect-ts, cli-gh, find-tool, yeet.
agents/ includes specialized subagents:
- docs-finder: find library/framework documentation
Invoke via -s or the Task tool.
MCP servers are configured in .mcp.json (currently none). Permission rules for MCP tools live in
settings/permissions/mcp.jsonc.
Hooks provide event-driven Claude Code automation. See hooks/README.md.
Active hooks from settings/hooks.jsonc:
- add_plan_frontmatter.py: add YAML frontmatter to plan files (
PostToolUse) - copy_prompt_to_clipboard.py: copy submitted prompts to the macOS clipboard (
UserPromptSubmit)
Available hook scripts also include settings sync helpers under hooks/SessionEnd/.
No plugins are enabled in settings/plugins.jsonc. plugins/ stores marketplace metadata and caches; refresh them with
just update-plugins.
Note
The claude wrapper runs Claude with --dangerously-skip-permissions and auto-loads MCP servers from .mcp.json.
See this issue.
Optional shell utilities from utils.sh:
ccc [args]: streamlined commits via/commit(defaults to--all)cccp: commit and push (feature branches)ccbump [args]: quick release bumping via/bump-releaseclaude [args]: enhanced CLI wrapper with MCP auto-loading
Source them in your shell config:
source ~/.claude/utils.shMIT. See LICENSE.md.