farty-bobo

Farty Bobo

Opinionated configuration for Claude Code, Claude Desktop, and Codex (partial support) that actually works. Built for software engineers who need to ship fast — custom skills, hooks, settings, and MCP servers wired into a parallel workflow so nothing sits waiting. Clone it. Symlink it. Stop suffering.

fartybobo.com

Supported Platforms

Platform	Support
Claude Code	Full — skills, hooks, settings, MCP servers, commands
Claude Desktop	Full — MCP servers via claude_desktop_config.json symlink; .skill archives extracted into active skills-plugin slot
Codex	Partial — skills load, but steps using Agent/SendMessage/TaskCreate silently no-op

Repo Structure

├── .claude-plugin/      # Claude Code plugin manifest — makes this repo an installable plugin
│   ├── plugin.json
│   └── marketplace.json
├── CLAUDE.md            # Project-level instructions
├── settings.json        # Claude Code settings (model, hooks, permissions, etc.)
├── .mcp.json            # MCP server configuration
├── commands/
│   └── statusline-command.sh
├── hooks/
│   ├── post-edit-check.sh
│   └── README.md
└── skills/
    └── *                # All skills, including /install for à la carte setup

Setup on a New Machine

Prerequisites: nvm must be installed. The setup script installs the pinned node version (see .nvmrc) automatically.

1. Clone the repo

   git clone <repo-url> ~/dev/farty-bobo
   

2. Run the setup script

   cd ~/dev/farty-bobo
   ./setup.sh
   

   The script will:

   • Create ~/.claude if needed
   • Symlink all config files and directories into ~/.claude
   • Symlink claude_desktop_config.json into Claude Desktop's config dir (macOS)
   • Extract each .skill archive from claude-desktop/skills/ into Claude Desktop's active skills-plugin slot (macOS; warns if a skill needs a one-time UI import to register server-side)
   • Create .env from .env.sample if it doesn't exist
   • Install the pinned node version via nvm and symlink it to ~/.local/bin

3. Fill in .env

   open .env   # or edit with your preferred editor
   

   Each variable is documented with inline comments in .env.sample. If you re-run setup.sh after a git pull, check .env.sample for any new keys and add them manually to .env.

4. Ensure ~/.local/bin is on your PATH (if the script warns about it)

   echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc
   

5. Import Desktop skills once. setup.sh always generates .skill ZIP archives under $TMPDIR/farty-bobo-skills/ (e.g. /var/folders/.../farty-bobo-skills/). Open Claude Desktop → Skills → + and import each .skill file from that directory. This is a one-time step per skill — it registers the skill server-side. Future setup.sh runs keep the skill content up to date automatically.

6. Restart Claude Desktop for MCP server changes to take effect.

7. Verify

   ls -la ~/.claude/settings.json ~/.claude/CLAUDE.md ~/.claude/.mcp.json ~/.claude/commands ~/.claude/hooks
   

   Each entry should show -> pointing to the repo paths.

Customization

• Edit files in this repo, then git commit and git push — changes propagate to every machine via git pull.
• To override settings on a single machine without affecting the repo, remove the symlink for that file and create a local copy instead.

Useful Links

• Claude Code Hooks

Adding MCP Servers to a Project

MCP servers are configured per-project via a .mcp.json file at the repo root — not globally. This means servers only load when Claude Code is running inside the relevant repo, so env vars and credentials don't need to be available everywhere.

Use the /add-mcp-server skill to add an MCP server to any project. It will:

• Create or update .mcp.json at the project root
• Use ${VAR_NAME} syntax for secrets (Claude Code expands these at runtime)
• Add missing env vars to .env and ensure .env is gitignored
• Keep .mcp.json safe to commit

Useful servers