~ / rigs / nickvigilante / dotfiles

nickvigilante/dotfiles

Configuration files for development environment

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

Copy this rig

# review before running: this installs third-party code
$ npx degit nickvigilante/dotfiles/home/dot_claude ./rig-dotfiles  # inspect, then merge into .claude/

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.

$ npx degit nickvigilante/dotfiles/home/dot_claude/skills/chezmoi .claude/skills/chezmoi
$ npx degit nickvigilante/dotfiles/home/dot_claude/skills/code-comments .claude/skills/code-comments
$ npx degit nickvigilante/dotfiles/home/dot_claude/skills/commit-and-pr .claude/skills/commit-and-pr
$ npx degit nickvigilante/dotfiles/home/dot_claude/skills/markdown .claude/skills/markdown
$ npx degit nickvigilante/dotfiles/home/dot_claude/skills/packages .claude/skills/packages
$ curl -fsSL --create-dirs -o .claude/agents/code-searcher.md https://raw.githubusercontent.com/nickvigilante/dotfiles/main/home/dot_claude/agents/code-searcher.md
$ curl -fsSL --create-dirs -o .claude/agents/curl-runner.md https://raw.githubusercontent.com/nickvigilante/dotfiles/main/home/dot_claude/agents/curl-runner.md
$ curl -fsSL --create-dirs -o .claude/agents/data-extractor.md https://raw.githubusercontent.com/nickvigilante/dotfiles/main/home/dot_claude/agents/data-extractor.md
$ curl -fsSL --create-dirs -o .claude/agents/git-archaeologist.md https://raw.githubusercontent.com/nickvigilante/dotfiles/main/home/dot_claude/agents/git-archaeologist.md
$ curl -fsSL --create-dirs -o .claude/agents/log-triage.md https://raw.githubusercontent.com/nickvigilante/dotfiles/main/home/dot_claude/agents/log-triage.md
$ curl -fsSL --create-dirs -o .claude/agents/repo-mapper.md https://raw.githubusercontent.com/nickvigilante/dotfiles/main/home/dot_claude/agents/repo-mapper.md
$ curl -fsSL --create-dirs -o .claude/agents/test-runner.md https://raw.githubusercontent.com/nickvigilante/dotfiles/main/home/dot_claude/agents/test-runner.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 *)"
    ]
  }
}

Skills (5)

Subagents (7)

code-searcher
model: haiku
Fast, cheap read-only code/file exploration. Use PROACTIVELY for "where is X", "find usages of Y", "which files touch Z", or summarizing a file's structure — any locating/reading task that does not ne
curl-runner
model: haiku
Runs HTTP requests with curl and returns a trimmed summary. The only place curl may run — the permission prefilter denies curl in the main session and every other agent, with a message pointing here.
data-extractor
model: haiku
Use PROACTIVELY to pull a specific answer out of large structured data — JSON/NDJSON, CSV, big API responses, query results, jq/awk/sql output — without loading the whole blob into the main context. R
git-archaeologist
model: haiku
Use PROACTIVELY to answer "when/why did X change", "who last touched this", "what introduced this bug/behavior", or to trace a line/function's history. Digs through git log/blame/show/bisect — high-vo
log-triage
model: haiku
Use PROACTIVELY to scan large or noisy logs (app logs, CI output, build/deploy logs, server logs) and return only the errors, warnings, and their surrounding context. Keeps multi-thousand-line logs ou
repo-mapper
model: sonnet
Use PROACTIVELY when you need a structural overview of an unfamiliar repo or subsystem — "how is this codebase organized", "where does X live", "what are the main components and how do they connect".
test-runner
model: haiku
Cheaply runs tests, linters, or builds and reports only the failures. Use PROACTIVELY when asked to "run the tests", "check the build", "run lint" — the mechanical run + triage doesn't need Opus. Retu

Slash commands (2)

/chezmoi-sync/distill-learnings

Similar rigs

copied ✓