Claude Code Vibe Coding for real teams, not just demos.
This site is organized for real adoption: first-time setup, command tutorials, daily workflow, gradual project configuration, team rollout, and then the deeper reference material. It is meant to teach Claude Code in the order a team can actually absorb it.
What this site does
Learn first, configure later
Beginners start with setup, commands, and daily workflow instead of heavy repo policy.
Project setup is treated as a capstone that builds on skills, hooks, and workflow habits you already understand.
Team rollout, reference, and advanced chapters stay available without becoming the on-ramp.
Starter files and download packs are still here once you are ready to standardize the repo.
Workflow Before Configuration
Learn the session loop first. Add shared repo structure only after the team understands how good Claude Code work feels day to day.
Verification First
Give Claude something concrete to verify against: tests, screenshots, expected outputs, or smoke commands.
Progressive Team Baseline
Start with a tight CLAUDE.md and shared settings. Add skills, hooks, and plugins only where they remove real friction.
Getting Started
Install Claude Code, sign in with the right account, tune the terminal, and choose a bootstrap path without diving into heavy repo configuration yet.
Tutorials
Learn Claude Code through guided sessions that introduce commands, daily work habits, skills, hooks, and project setup in a safe order.
Workflows
Turn the tutorial habits into a repeatable daily operating loop before you scale or standardize anything.
Configuration
Assemble a reusable repo baseline only after the workflow feels familiar.
Team Rollout
Standardize only the parts the team is ready to live with, then scale from there.
Reference
Keep the command surface, curated links, glossary, troubleshooting notes, and release changes close at hand.
Advanced
Deep-dive the reference surfaces once the daily flow and the team baseline are already working.
Core Commands
Start with the slash commands you will use constantly before you touch team-wide configuration.
OpenYour First Feature
Get a first win with a concrete explore -> RED -> GREEN -> review flow you can repeat tomorrow.
OpenDaily Workflow
Turn the tutorial habits into a repeatable day-to-day operating loop once the basics are comfortable.
OpenProject Setup
Build the shared repo baseline only after you understand what each piece is buying you.
OpenBest Links
Jump to the official docs, release notes, and the best supplemental community tutorials from one page.
OpenRelease Changes
The March-April 2026 changes that materially affect real Claude Code workflows.
OpenMethodology
Explore → Plan → RED → GREEN → Review → Ship
The site uses Anthropic's verification-first guidance and the Superpowers framing together: no production behavior change until a failing verification artifact exists.
Repository Structure
The recommended repo layout is part of the product.
The downloadable files on this site mirror this structure so teams can unpack the code into the right filenames instead of manually reconstructing the tree from prose.
repo/
├── CLAUDE.md # Project rules (< 200 lines)
├── .claude/
│ ├── settings.json # Team-shared: hooks, permissions, model
│ ├── settings.local.json # Personal overrides (gitignored)
│ ├── hooks/
│ │ ├── require-test-first.sh # PreToolUse TDD gate
│ │ ├── run-related-tests.sh # PostToolUse async feedback
│ │ ├── auto-format.sh # PostToolUse formatter
│ │ ├── block-dangerous.sh # PreToolUse security gate
│ │ └── defer-production-ops.sh # PreToolUse CI/CD human gate
│ ├── rules/
│ │ ├── frontend-testing.md # Scoped to apps/web/**
│ │ └── backend-testing.md # Scoped to services/api/**
│ ├── skills/
│ │ └── test-forward/
│ │ └── SKILL.md # Verification-first skill
│ ├── agents/
│ │ └── code-reviewer.md # Custom reviewer subagent
│ └── plans/ # Stored plans
└── tests/