caotrongtin99/nextjs-nestjs-claude-code-setup
Next.js setup with Claude AI integration for automated code generation, review, and optimization workflow
ARCHETYPE
Pragmatist
A balanced, no-drama setup: some rules, some tools, nothing extreme.
Copy this rig
# review before running: this installs third-party code
$ npx degit caotrongtin99/nextjs-nestjs-claude-code-setup/.claude ./rig-nextjs-nestjs-claude-code-setup # 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/code-reviewer.md https://raw.githubusercontent.com/caotrongtin99/nextjs-nestjs-claude-code-setup/main/.claude/agents/code-reviewer.md $ curl -fsSL --create-dirs -o .claude/agents/performance-optimizer.md https://raw.githubusercontent.com/caotrongtin99/nextjs-nestjs-claude-code-setup/main/.claude/agents/performance-optimizer.md $ curl -fsSL --create-dirs -o .claude/agents/senior-developer.md https://raw.githubusercontent.com/caotrongtin99/nextjs-nestjs-claude-code-setup/main/.claude/agents/senior-developer.md $ curl -fsSL --create-dirs -o .claude/agents/tech-lead.md https://raw.githubusercontent.com/caotrongtin99/nextjs-nestjs-claude-code-setup/main/.claude/agents/tech-lead.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 *)"
]
}
} Subagents (4)
| code-reviewer model: sonnet | after implementation |
| performance-optimizer model: sonnet | - After code review passes\n- Before production deployment\n- When performance issues are detected\n- During performance audits |
| senior-developer model: sonnet | coding implementation |
| tech-lead model: sonnet | planning phase |
Slash commands (4)
/code/optimize/plan/review
Similar rigs
felipebustillo/dotclaude
A complete reference for configuring Claude Code — agents, skills, rules, hooks, settings, and memory patterns
Orchestrator 300 tok ·
AizenvoltPrime/claude-setup
—
Pragmatist 1.2k tok ·
IvanKuzyshyn/dotfiles
Dotfiles optimized for speed, coffee, and questionable life choices. 😜
Pragmatist 3.0k tok ·
HGInsights/claude-code-setup
Production-tested Claude Code harness configuration: hooks, skills, subagents, and automated review loops
Pragmatist 1.9k tok ·