convez.ai
SkillDevOps & InfraestruturaAvançado
richardbowman

Claude Config

richardbowman/claude-config

Sincronização de config + bootstrap automatizado para Claude Code

Ver no GitHub
InicialPluginScore · de 0 a 100

Sistema de configuração pessoal para Claude Code que sincroniza settings, plugins, skills e dotfiles entre máquinas. Inclui bootstrap automatizado que instala dependências, clona repositórios de skills, configura regras customizadas e expõe CLIs utilitários para gerenciamento de workspaces e desenvolvimento.

Instalação

$npx convez-ai richardbowman/claude-config

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
0
Acompanhando
0
Saúde
28%
Último commit
há 6 dias
Versão
—
Issues abertas
0
Contribuidores
2

Casos de uso

  • Sincronizar configurações do Claude Code entre múltiplas máquinas
  • Automatizar setup inicial com bootstrap de skills e dependências
  • Gerenciar git worktrees com CLIs especializadas (wtcc, wtadd, wt-ff-main)
  • Integrar skills terceirizadas e rules customizadas de forma centralizada

Veredito

Config robusta para quem trabalha em múltiplos ambientes e precisa de setup reproduzível. Bem arquitetada com separação clara entre settings, skills, rules e CLIs — mas exige familiaridade com shell scripting e gestão de dotfiles para aproveitar ao máximo.

README

A tradução para o português deste README ainda está na fila.

claude-config

Personal Claude Code machine setup — settings, dotfiles, shell config, and CLIs synced across machines.

Skills live in a separate repo: agent-skills. Bootstrap pulls it in automatically.

What's in here

  • settings.json — permissions allow-list, enabled plugins, model preference
  • plugins/known_marketplaces.json — registered plugin marketplaces
  • skills.txt — third-party skills to install via npx skills add
  • scripts/ — shared TypeScript utilities (run via npx tsx)
  • rules/ — custom CLAUDE.md-style rules synced to ~/.claude/rules/ (e.g., context7.md)
  • bin/ — CLIs added to ~/.local/bin on bootstrap
  • bootstrap.sh — thin thunk that verifies Node is installed, then execs bootstrap.js
  • bootstrap.js — does the real work: symlinks settings/plugins/rules/bin into ~/.claude/, clones + bootstraps agent-skills, installs third-party skills

Skills

Hand-authored skills live in richardbowman/agent-skills — cloned as a sibling of this repo (e.g. ~/GitHub/agent-skills/) and symlinked into ~/.claude/skills/ by bootstrap.

Third-party skills (installed via npx skills add, listed in skills.txt):

SkillPurpose
find-skillsDiscover and search available skills in the marketplace.
defuddleParse and extract clean content from web pages.
json-canvasCreate and edit Obsidian JSON Canvas files.
obsidian-basesWork with Obsidian Bases (database views).
obsidian-cliControl Obsidian via CLI commands.
obsidian-markdownObsidian-flavored Markdown — callouts, embeds, properties.

Included CLIs

  • nextdev — scoped Next.js dev-server manager. Start/stop/restart/list servers by worktree, logs, doctor. Safely avoids wildcard process kills. See skills/nextjs-local-dev/SKILL.md for full reference.
  • worktree-bootstrap — one-command prep for a fresh git worktree (install deps, copy .env.local, start Podman Postgres, inject DATABASE_URL, launch nextdev). See skills/worktree-bootstrap/SKILL.md.
  • wtcc [name] — fetch + fast-forward main, then launch Claude Code in a new git worktree. Defaults to a timestamped branch name (work-YYYYMMDD-HHMMSS) so each invocation always gets its own branch. Runs /worktree-bootstrap on entry.
  • wtadd <path> [branch] [...] — safe wrapper around git worktree add: fast-forwards main first, then creates the worktree. Prevents branching off a stale base.
  • wt-ff-main — fetch origin and fast-forward local main if behind. Used internally by wtcc and wtadd; can also be run standalone.

Setup on a new machine

macOS — one-shot

Recommended: clone first. Homebrew's installer needs an interactive TTY to prompt for your password (piped curl | bash can't give it one, which surfaces as misleading "not an administrator" errors):

xcode-select --install   # if not already installed
git clone https://github.com/richardbowman/claude-config.git ~/Projects/claude-config   # or ~/GitHub, ~/code, etc.
~/Projects/claude-config/scripts/setup-mac.sh
~/Projects/claude-config/scripts/setup-mac-apps.sh   # optional: personal apps

One-liner (the script now detects piped-stdin and reattaches to /dev/tty when possible):

curl -fsSL https://raw.githubusercontent.com/richardbowman/claude-config/main/scripts/setup-mac.sh | bash

Installs Xcode CLI tools, Homebrew, git, fnm + Node LTS, Claude Code, gh, podman, Vercel CLI, and runs bootstrap.sh. Idempotent — safe to re-run.

After the script finishes (interactive steps, one-time per machine):

exec zsh -l          # login shell — sources .zprofile so brew, fnm, etc. resolve
claude               # first run prompts login
gh auth login        # authenticate GitHub CLI
vercel login         # authenticate Vercel CLI
podman machine init  # ~1GB download — skip if podman-desktop will manage this
podman machine start

Verify everything wired up:

ls -la ~/.claude/settings.json            # should be a symlink -> <projects-dir>/claude-config/settings.json
ls ~/.claude/skills/                      # should list all synced skills
nextdev doctor                            # should report node + brew-installed tools

Linux / manual

git clone git@github.com:<user>/claude-config.git ~/Projects/claude-config   # any directory works
~/Projects/claude-config/bootstrap.sh

Prereq: Node 18+. If node isn't on PATH, bootstrap.sh prints install instructions and exits. Recommended:

# macOS
brew install fnm && fnm install --lts && fnm default lts-latest

# Linux
curl -fsSL https://fnm.vercel.app/install | bash
fnm install --lts && fnm default lts-latest

# Windows (native)
winget install Schniz.fnm
fnm install --lts && fnm default lts-latest

# add to ~/.bashrc, ~/.zshrc, or PowerShell $PROFILE
eval "$(fnm env --use-on-cd)"

The script symlinks files from this repo into ~/.claude/ (settings, marketplaces, skills) and into ~/.local/bin/ (CLIs), so later edits in either location stay in sync. Existing non-symlink files at the target are backed up to *.backup.<timestamp>.

Make sure ~/.local/bin is on your PATH (add export PATH="$HOME/.local/bin:$PATH" to ~/.bashrc or ~/.zshrc if not).

Status line

The status line is configured in settings.json to run bin/statusline-command.sh from this repo (symlinked into ~/.local/bin/ via bootstrap.sh).

It shows:

  • nextdev URL — dynamically looks up the running nextdev port for the current workspace (e.g. http://localhost:3001). Hidden if no server is running.
  • Git branch — current branch name.
  • PR number — if a GitHub PR exists for the branch (via gh), appended as PR #123.

The script hashes the workspace's absolute path with SHA1 to find the right nextdev state dir under ~/.local/state/nextdev/, so it correctly tracks per-worktree servers.

Machine-specific overrides

Use ~/.claude/settings.local.json for anything that shouldn't be shared (per-machine paths, private tweaks). That file is not managed by this repo.

Typical contents on a fresh machine — adjust paths for macOS (/Users/<you>) or Windows (C:\\Users\\<you>):

{
  "permissions": {
    "additionalDirectories": [
      "/home/<you>"
    ]
  }
}

additionalDirectories grants read/edit access outside the current project root without prompting. Paths are absolute and differ per OS, so they can't live in the synced settings.json.

Adding a skill

Hand-authored skill: add it to agent-skills — create <name>/SKILL.md, run node <projects-dir>/agent-skills/bootstrap.js, add the trigger to ~/.claude/CLAUDE.md.

Third-party skill: install locally (npx skills add <name>), add its name to skills.txt, commit and push — other machines pick it up on next bootstrap run.

Adding a plugin

Plugins sync via two pieces, both already handled by bootstrap.sh:

  1. Enable the plugin — add it to enabledPlugins in settings.json:
    "enabledPlugins": {
      "vercel-plugin@vercel": true,
      "some-plugin@some-marketplace": true
    }
    
  2. Register the marketplace in plugins/known_marketplaces.json if it isn't there yet. Easiest: install the plugin once with /plugin install <id>@<marketplace> in Claude Code; it writes the marketplace entry, and since that file is symlinked, the change flows back to the repo.

Not synced: ~/.claude/plugins/installed_plugins.json (machine cache — absolute paths, timestamps) and ~/.claude/plugins/cache/ / marketplaces/ (downloaded content). Claude Code re-fetches on first run based on enabled + known marketplaces.

Not included (intentionally)

Secrets, runtime state, and caches are never committed: .credentials.json, sessions/, projects/, history.jsonl, shell-snapshots/, cache/, backups/, plugins/cache/, plugins/data/, plugins/marketplaces/, etc.

Ver o original no GitHub

Bom para

Relacionados