lrendina/claude-code-setup
My Claude Code build: state-colored terminals, auto tab titles, session memory, plan gates, a context-weather mod, and a safe installer
ARCHETYPE
Minimalist
Lean instructions, few tools, tiny context tax. Lets the model think.
Copy this rig
# review before running: this installs third-party code $ npx degit lrendina/claude-code-setup/agents ./rig-claude-code-setup/agents $ npx degit lrendina/claude-code-setup/skills ./rig-claude-code-setup/skills $ npx degit lrendina/claude-code-setup/hooks ./rig-claude-code-setup/hooks
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 lrendina/claude-code-setup/skills/token-efficient-work .claude/skills/token-efficient-work $ curl -fsSL --create-dirs -o .claude/agents/explorer.md https://raw.githubusercontent.com/lrendina/claude-code-setup/main/agents/explorer.md $ curl -fsSL --create-dirs -o .claude/agents/researcher.md https://raw.githubusercontent.com/lrendina/claude-code-setup/main/agents/researcher.md $ curl -fsSL --create-dirs -o .claude/agents/worker.md https://raw.githubusercontent.com/lrendina/claude-code-setup/main/agents/worker.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 *)"
]
}
} Skills (1)
Subagents (3)
| explorer model: opus | Read-only codebase exploration. Use to locate code, trace call paths, and summarize how something works before planning or editing. |
| researcher model: opus | Looks up external docs, APIs, and library behavior. Use when an answer depends on current documentation rather than the codebase. |
| worker model: opus | Implements a scoped, already-planned change — edits plus the tests that cover them. Use after the plan is fixed. |
Similar rigs
jaqubowsky/fleet
Runs Claude Code and pi agents in parallel on your Mac, one Docker sandbox per issue. A host agent hands out the work, watches every sandbox and brings back tested, reviewed pull requests.
Minimalist 566 tok · · Q0
dnotitia/akb
AKB — Agent Knowledgebase. Organizational memory for AI agents: vault-scoped docs / tables / files unified by URI graph, served over MCP.
Pragmatist 6.9k tok · · Q28
AegeanWorks/AIKit
Crash-resilient governance and delivery gates for AI coding agents: versioned task ledger, commit-level verification, secret scanning and per-project gates. Free for personal use under AL-1.1; commercial use under ACL-1.0.
Orchestrator 4.2k tok · · Q23
iuliandita/agents
Global prompts and subagent roles for coding agents, deployed to every harness you use.
Orchestrator 1.5k tok · · Q3