ARCHETYPE
Orchestrator
A bench of specialised subagents. The main agent mostly delegates.
Copy this rig
# review before running: this installs third-party code
$ npx degit christianromney/dotfiles/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.
$ curl -fsSL --create-dirs -o .claude/agents/SKILL.md https://raw.githubusercontent.com/christianromney/dotfiles/main/dot_claude/agents/software-designer/SKILL.md $ curl -fsSL --create-dirs -o .claude/agents/design-principles.md https://raw.githubusercontent.com/christianromney/dotfiles/main/dot_claude/agents/software-designer/design-principles.md $ curl -fsSL --create-dirs -o .claude/agents/SKILL.md https://raw.githubusercontent.com/christianromney/dotfiles/main/dot_claude/agents/tech-writer/SKILL.md $ curl -fsSL --create-dirs -o .claude/agents/documentation.md https://raw.githubusercontent.com/christianromney/dotfiles/main/dot_claude/agents/tech-writer/documentation.md $ curl -fsSL --create-dirs -o .claude/agents/SKILL.md https://raw.githubusercontent.com/christianromney/dotfiles/main/dot_claude/agents/web-quality-tester/SKILL.md
This rig commits no guardrails. Here is the community baseline instead — the deny/ask rules most often found across all 16.2k rigs:
{
"permissions": {
"deny": [
"Read(./.env)",
"Read(./.env.*)",
"Read(**/.env)",
"Read(~/.ssh/**)",
"Bash(git push --force:*)",
"Read(**/*.pem)",
"Read(.env)",
"Read(~/.aws/**)",
"Read(**/*.key)",
"Read(**/.env.*)",
"Bash(git push --force*)",
"Bash(rm -rf:*)",
"Bash(rm -rf *)",
"Bash(sudo *)",
"Bash(sudo:*)",
"Bash(rm -rf /)",
"Bash(git push -f:*)",
"Read(.env.*)",
"Bash(git reset --hard*)",
"Bash(rm -rf /*)"
],
"ask": [
"Bash(git push:*)",
"Bash(git push *)",
"Bash(gh pr merge *)",
"Bash(git commit:*)",
"Bash(rm *)",
"Bash(gh pr merge:*)",
"Bash(gh pr create *)",
"Bash(git reset --hard:*)",
"Bash(npm publish:*)",
"Bash(git rebase *)"
]
}
} Subagents (5)
| software-designer | Use this agent when you need to analyze technical problems or design robust solutions. Examples: <example>Context: User is facing a complex system integration challenge with multiple legacy systems. u |
| design-principles | — |
| technical-writer | Use this agent when you need to create technical documentation for software. Examples: <example>Context: User has just implemented a new authentication system and needs comprehensive documentation. us |
| documentation | — |
| web-qa-engineer | Use this agent when you need comprehensive quality assurance testing, browser automation, or validation of application requirements. Examples: <example>Context: User has implemented a new login featur |
Similar rigs
felipebustillo/dotclaude
A complete reference for configuring Claude Code — agents, skills, rules, hooks, settings, and memory patterns
Orchestrator 300 tok · · Q0
jczhang02/dotfiles
ChengruiZhang's gentoo linux dotfiles, managed by GNU Stow
Pragmatist 661 tok · · Q8
edmund-io/edmunds-claude-code
—
Orchestrator 469 tok · · Q0
Hayashi-Takuto/edmonds-claude-code
"Edmund's personal Claude Code setup with 14 productivity commands and 11 specialized AI agents for modern web development"
Orchestrator 469 tok · · Q0