~ / rigs / psteinroe / dotfiles

psteinroe/dotfiles

These are my Dotfiles

↗ GitHub ★ 7 MIT updated 3d ago personal setup Claude CodeCodex
share on X
ARCHETYPE
Orchestrator
A bench of specialised subagents. The main agent mostly delegates.
CONTEXT TAX · EVERY TURN
~9.1k tokens
Heavy · median rig: 2.3k · breakdown
GUARDRAILS
0/5
No committed guardrails · details

Copy this rig

# review before running: this installs third-party code
$ claude mcp add --transport http foilwick https://foilwick.com/api/mcp
$ claude mcp add scryfall -- pnpx scryfall-mcp-server
$ claude mcp add --transport http executor https://executor.getmateo.com/mcp/toolkits/developer
$ npx degit psteinroe/dotfiles/agents ./rig-dotfiles/agents

MCP servers are added to Claude Code at local scope; env vars are shown as YOUR_… placeholders — we never store values. Files are fetched with degit into a separate folder so you can review before merging.

$ claude mcp add --transport http foilwick https://foilwick.com/api/mcp
$ claude mcp add scryfall -- pnpx scryfall-mcp-server
$ claude mcp add --transport http executor https://executor.getmateo.com/mcp/toolkits/developer
$ npx degit psteinroe/dotfiles/agents/pi/skills/herdr .claude/skills/herdr
$ npx degit psteinroe/dotfiles/agents/pi/skills/rdev-recovery .claude/skills/rdev-recovery
$ npx degit psteinroe/dotfiles/agents/skills/background-tasks .claude/skills/background-tasks
$ npx degit psteinroe/dotfiles/agents/skills/iterate-pr .claude/skills/iterate-pr
$ npx degit psteinroe/dotfiles/agents/skills/pr-writer .claude/skills/pr-writer
$ npx degit psteinroe/dotfiles/agents/skills/spec-implementation-notes .claude/skills/spec-implementation-notes
$ npx degit psteinroe/dotfiles/agents/skills/sync-branch .claude/skills/sync-branch
$ npx degit psteinroe/dotfiles/agents/skills/weekly-update .claude/skills/weekly-update
$ curl -fsSL --create-dirs -o .claude/agents/UPSTREAM.md https://raw.githubusercontent.<redacted>-terminals/UPSTREAM.md
$ curl -fsSL --create-dirs -o .claude/agents/THIRD_PARTY.md https://raw.githubusercontent.<redacted>_PARTY.md
$ curl -fsSL --create-dirs -o .claude/agents/UPSTREAM.md https://raw.githubusercontent.<redacted>.md
$ curl -fsSL --create-dirs -o .claude/agents/UPSTREAM.md https://raw.githubusercontent.<redacted>.md
$ curl -fsSL --create-dirs -o .claude/agents/THIRD_PARTY.md https://raw.githubusercontent.<redacted>_PARTY.md
$ curl -fsSL --create-dirs -o .claude/agents/UPSTREAM.md https://raw.githubusercontent.<redacted>-context/UPSTREAM.md
$ curl -fsSL --create-dirs -o .claude/agents/SKILL.md https://raw.githubusercontent.<redacted>.md
$ curl -fsSL --create-dirs -o .claude/agents/SKILL.md https://raw.githubusercontent.<redacted>-recovery/SKILL.md
$ curl -fsSL --create-dirs -o .claude/agents/SKILL.md https://raw.githubusercontent.<redacted>-tasks/SKILL.md
$ curl -fsSL --create-dirs -o .claude/agents/SKILL.md https://raw.githubusercontent.<redacted>-pr/SKILL.md
$ curl -fsSL --create-dirs -o .claude/agents/SKILL.md https://raw.githubusercontent.com/psteinroe/dotfiles/main/agents/skills/pr-writer/SKILL.md
$ curl -fsSL --create-dirs -o .claude/agents/SKILL.md https://raw.githubusercontent.com/psteinroe/dotfiles/main/agents/skills/spec-implementation-notes/SKILL.md
$ curl -fsSL --create-dirs -o .claude/agents/SKILL.md https://raw.githubusercontent.com/psteinroe/dotfiles/main/agents/skills/sync-branch/SKILL.md
$ curl -fsSL --create-dirs -o .claude/agents/SKILL.md https://raw.githubusercontent.<redacted>-update/SKILL.md

This rig commits no guardrails. Here is the community baseline instead — the deny/ask rules most often found across all 7,204 rigs:

{
  "permissions": {
    "deny": [
      "Read(./.env)",
      "Read(**/.env)",
      "Read(~/.ssh/**)",
      "Bash(rm -rf *)",
      "Read(**/*.pem)",
      "Bash(rm -rf /)",
      "Bash(git push --force:*)",
      "Bash(sudo *)",
      "Read(.env)",
      "Bash(rm -rf /*)",
      "Read(./.env.*)",
      "Read(~/.aws/**)",
      "Bash(git push --force*)",
      "Bash(rm -rf:*)",
      "Read(**/*.key)",
      "Read(**/.env.*)",
      "Bash(sudo:*)",
      "Bash(git reset --hard*)",
      "Bash(git reset --hard:*)",
      "Read(.env.*)"
    ],
    "ask": [
      "Bash(git push:*)",
      "Bash(git push *)",
      "Bash(git commit:*)",
      "Bash(rm *)",
      "Bash(rm:*)",
      "Bash(git rebase *)",
      "Bash(wget *)",
      "Bash(npm publish:*)",
      "Bash(git commit *)",
      "Bash(gh pr merge *)"
    ]
  }
}

MCP servers (3)

serversourceest. tokens
foilwick.com · "foilwick" remote · remote 2.5k
scryfall-mcp-server · "scryfall" npm 2.5k
executor.getmateo.com · "executor" remote · remote 2.5k

Skills (8)

Subagents (14)

UPSTREAM—
THIRD_PARTY—
UPSTREAM—
UPSTREAM—
THIRD_PARTY—
UPSTREAM—
herdrUse inside Herdr when a task needs a branch or PR workspace, even if the request does not name Herdr; also use for explicit Herdr pane, tab, workspace, or persistent-agent operations. Manage project w
rdev-recoveryRecover the rdev exe.dev machine after an OOM, disk exhaustion, freeze, failed SSH, or reboot. Use to reclaim safe remote disk space, restart the VM, verify remote Herdr and Pi restoration, identify i
background-tasksRun and manage session-scoped background subagents and long-lived commands. Use for delegated Mapper/Librarian/Oracle/Worker work, dev servers, watchers, streaming builds, log tails, long test suites,
iterate-prIterate or merge a pull request through actionable review feedback and CI failures. Use when asked to fix CI, address PR feedback, get a PR green, merge after checks pass, or explicitly bypass review
pr-writerCreate or refresh GitHub pull requests with direct gh commands. Use when opening a PR, updating an existing PR after material changes, or drafting a PR title/body.
spec-implementation-notesImplement a provided spec while maintaining a running implementation-notes.md file. Use when the user asks to implement a spec, plan, ticket, or requirements document and wants ongoing notes about des
sync-branchSync current branch with main. Use when the user wants to update their feature branch with the latest changes from the main branch. Fetches, rebases, and handles conflicts.
weekly-updateGenerate a two-week status update from PRs. Use when the user wants a summary of their work for the last two weeks. The user must specify the repository (owner/repo).

Similar rigs

copied ✓