~ / rigs / levu304 / claude-code-boilerplate

levu304/claude-code-boilerplate

Universal coding standards and AI agent configurations for Claude Code projects

↗ GitHub ★ 130 MIT updated 6mo ago project Claude Code
share on X
ARCHETYPE
Orchestrator
A bench of specialised subagents. The main agent mostly delegates.
CONTEXT TAX · EVERY TURN
~14.5k tokens
Heavy · median rig: 2.2k · breakdown
GUARDRAILS
0/5
No committed guardrails · details

Copy this rig

# review before running: this installs third-party code
$ npx degit levu304/claude-code-boilerplate/.claude ./rig-claude-code-boilerplate  # 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 levu304/claude-code-boilerplate/.claude/skills/review-local-changes .claude/skills/review-local-changes
$ npx degit levu304/claude-code-boilerplate/.claude/skills/review-pr .claude/skills/review-pr
$ curl -fsSL --create-dirs -o .claude/agents/bug-hunter.md https://raw.githubusercontent.com/levu304/claude-code-boilerplate/main/.claude/agents/bug-hunter.md
$ curl -fsSL --create-dirs -o .claude/agents/business-analyst.md https://raw.githubusercontent.com/levu304/claude-code-boilerplate/main/.claude/agents/business-analyst.md
$ curl -fsSL --create-dirs -o .claude/agents/code-quality-reviewer.md https://raw.githubusercontent.com/levu304/claude-code-boilerplate/main/.claude/agents/code-quality-reviewer.md
$ curl -fsSL --create-dirs -o .claude/agents/contracts-reviewer.md https://raw.githubusercontent.com/levu304/claude-code-boilerplate/main/.claude/agents/contracts-reviewer.md
$ curl -fsSL --create-dirs -o .claude/agents/fullstack-developer.md https://raw.githubusercontent.com/levu304/claude-code-boilerplate/main/.claude/agents/fullstack-developer.md
$ curl -fsSL --create-dirs -o .claude/agents/historical-context-reviewer.md https://raw.githubusercontent.com/levu304/claude-code-boilerplate/main/.claude/agents/historical-context-reviewer.md
$ curl -fsSL --create-dirs -o .claude/agents/principal-engineer.md https://raw.githubusercontent.com/levu304/claude-code-boilerplate/main/.claude/agents/principal-engineer.md
$ curl -fsSL --create-dirs -o .claude/agents/qa-engineer.md https://raw.githubusercontent.com/levu304/claude-code-boilerplate/main/.claude/agents/qa-engineer.md
$ curl -fsSL --create-dirs -o .claude/agents/security-auditor.md https://raw.githubusercontent.com/levu304/claude-code-boilerplate/main/.claude/agents/security-auditor.md
$ curl -fsSL --create-dirs -o .claude/agents/solution-architect.md https://raw.githubusercontent.com/levu304/claude-code-boilerplate/main/.claude/agents/solution-architect.md
$ curl -fsSL --create-dirs -o .claude/agents/test-coverage-reviewer.md https://raw.githubusercontent.com/levu304/claude-code-boilerplate/main/.claude/agents/test-coverage-reviewer.md
$ curl -fsSL --create-dirs -o .claude/agents/uiux-designer.md https://raw.githubusercontent.com/levu304/claude-code-boilerplate/main/.claude/agents/uiux-designer.md

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

{
  "permissions": {
    "deny": [
      "Read(~/.ssh/**)",
      "Read(**/.env)",
      "Bash(rm -rf *)",
      "Read(./.env)",
      "Bash(rm -rf /)",
      "Bash(git push --force:*)",
      "Bash(sudo *)",
      "Read(**/*.pem)",
      "Bash(rm -rf /*)",
      "Read(~/.aws/**)",
      "Bash(rm -rf:*)",
      "Read(.env)",
      "Bash(git push --force*)",
      "Read(**/*.key)",
      "Read(./.env.*)",
      "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(wget *)",
      "Bash(npm publish:*)",
      "Bash(gh pr merge *)",
      "Bash(chown *)",
      "Bash(docker *)"
    ]
  }
}

Skills (2)

Subagents (12)

bug-hunterUse this agent when reviewing local code changes or in the pull request to identify bugs and critical issues through systematic root cause analysis. This agent should be invoked proactively after comp
business-analyst
model: sonnet
Expert business analyst. MUST BE USED to analyze requirements, create user stories, define acceptance criteria, and translate business needs into technical specifications.
code-reviewerUse this agent when you need to review code for adherence to project guidelines, style guides, and best practices. This agent should be used proactively after writing or modifying code, or for reviwin
contracts-reviewerUse this agent when reviewing local code changes or pull requests to analyze API, data models, and type design. This agent should be invoked proactively when changes affect public contracts, domain mo
fullstack-developer
model: sonnet
Expert full-stack developer specializing in modern web technologies. MUST BE USED for all implementation tasks including backend APIs, frontend applications, database operations, and full-stack featur
historical-context-reviewerUse this agent when reviewing local code changes or pull requests to understand the historical context of modified code, including past issues, patterns, and lessons learned. This agent should be invo
principal-engineer
model: sonnet
Senior principal software engineer. MUST BE USED to review code quality, architecture, design patterns, best practices, and investigate technical issues. Proactively reviews after any code changes and
qa-engineer
model: sonnet
Expert QA/QC engineer. MUST BE USED for all testing tasks, test plan creation, test execution, and quality assurance. Use for unit tests, integration tests, and test coverage analysis.
security-auditorUse this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes o
solution-architect
model: sonnet
Expert solution architect. MUST BE USED to design system architecture, create technical specifications, define data models, and make technology stack decisions based on analyzed requirements.
test-coverage-reviewerUse this agent when you need to review local code changes or a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or tests updated, to ensure t
uiux-designer
model: sonnet
Expert UI/UX designer. MUST BE USED to review application design, ensure consistent user experience, validate accessibility, review visual hierarchy, and provide design recommendations.

Similar rigs

copied ✓