carlvellotti/claude-code-everyone-course
Claude Code for Everyone - Learn Claude Code in Claude Code
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 carlvellotti/claude-code-everyone-course/course-materials/.claude ./rig-claude-code-everyone-course # 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/barista-lead.md https://raw.githubusercontent.com/carlvellotti/claude-code-everyone-course/main/course-materials/.claude/agents/barista-lead.md $ curl -fsSL --create-dirs -o .claude/agents/exec.md https://raw.githubusercontent.com/carlvellotti/claude-code-everyone-course/main/course-materials/.claude/agents/exec.md $ curl -fsSL --create-dirs -o .claude/agents/product-designer.md https://raw.githubusercontent.com/carlvellotti/claude-code-everyone-course/main/course-materials/.claude/agents/product-designer.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 (3)
| (•‿•) Barista Lead | Ground-level operations perspective - knows what customers actually say and do |
| (ಠ_ಠ) Exec | Leadership perspective - focused on ROI, metrics, and business impact |
| (◠‿◠) Product Designer | UX/experience perspective - focused on user emotions, journeys, and engagement |
Slash commands (13)
/start-1-1/start-1-2/start-1-3/start-1-4/start-1-5/start-1-6/start-1-7/start-1-8/start-2-1/start-2-2/start-2-3/start-2-4/start-2-5
Similar rigs
roadhero/claude-code-setup
My actual Claude Code setup: a stack-agnostic engineering spine, auto-activating rule packs, 50 scoped subagents across web/Android/iOS/compute, safety hooks, and a repo scaffolder. From the book "42: The AI Builder's Stack."
Orchestrator 7.3k tok ·
FlorianBruniaux/ccboard
Monitor Claude Code sessions, costs, config, hooks, agents & MCP servers from a single Rust binary — TUI (9 tabs) + Web interface with live process tracking, budget alerts, and 30-day forecasting
Fort Knox 11.3k tok ·
circleone1980/claude-enterprise-starter
Enterprise-grade Claude Code template with Agent Team, Rage Mode, TDD workflow, and production-ready configurations
YOLO Cowboy 16.3k tok ·
JHamidun/claude-code-config-pack
Depersonalised Claude Code configuration pack — 314 skills, 74 agents, 155 commands, 18 rules, 33 plugins. One-shot deploy via install.ps1 / install.sh.
YOLO Cowboy 72.7k tok ·