The Library

Self-contained playbooks you can use today - copy-paste prompts, setup walkthroughs, and curated tool lists for getting more out of Claude Code. Cut your token bill, give Claude a memory that survives between sessions, stop it from hallucinating, build your first skill, wire up a five-agent crew, and stand up the starter files every beginner needs. Each resource is complete on its own and grouped into stacks so you can go as deep as you want. No email gate, no fluff.

Step-by-step how-tos for everything Claude Code - from the initial claude code install and claude code login, through setting up MCP servers, writing your first CLAUDE.md, and building the multi-agent workflows that let you ship an entire feature in an afternoon. Each guide is task-specific: you land, you follow the steps, you leave with something working. Patterns here come from real projects and are updated whenever Claude Code by Anthropic ships a change that affects the workflow.

Concrete things to build with Claude Code - SaaS MVPs, internal dashboards, content pipelines, browser automations, and client tools. Every use case walks through the actual approach: which MCP servers to wire up, how to structure the task for a claude code agent, what a realistic time investment looks like, and where to use a claude code skill to encode the repeatable parts. These are not toy examples - they are the kinds of projects 5,000+ builders in the club have shipped.

Plain-English explainers for every concept worth knowing before you start building. What is Claude Code and how is it different from ChatGPT? How does the claude code CLI work? What is an MCP server and why does it matter? How do you manage context windows on a large project? Each explainer goes deep enough to be genuinely useful - not just a one-liner definition, but the mental model you need to make better decisions when you are actually building.

Field notes from people who ship with Claude Code daily. You'll find specific workflow playbooks - how to run Claude Code in headless mode inside a GitHub Action, how to build a useful CLAUDE.md from scratch, how to structure a subagent for a complex data task - alongside honest write-ups of what went wrong and why. Posts are published by David Iya, Duncan Rogoff, and active Club members, so the perspective is always from someone who actually uses the tool, not someone summarizing documentation.

Honest, specific side-by-sides: Claude Code vs Cursor, Claude Code vs GitHub Copilot, Claude Code vs Replit, Claude Code vs ChatGPT for building, and more. Each comparison covers real differences in capability, workflow fit, pricing model, and the kinds of projects each tool handles well. The goal is to help you pick the right tool for your specific situation - not to declare a winner, but to give you enough information to make the call yourself.

Every term you'll encounter in the Claude Code ecosystem - the claude code CLI, MCP servers, agents, subagents, skills, slash commands, hooks, headless mode, IDE integration, context windows, tokens, and more - each defined in enough depth to actually be useful. If you land on a guide or use case and hit a term you don't recognize, the glossary is where to go. Definitions are written for builders, not for people who already know the answers.

The full primer for anyone asking 'what is Claude Code' for the first time. It covers what the tool actually does, how it differs from the regular Claude chat interface and from other AI coding assistants, who it is designed for, what a realistic first session looks like, and how to get started today - including the claude code install and claude code login steps. If you are sending this page to a client or colleague who has never heard of Claude Code by Anthropic, this is the right link.

Honest, direct answers to the questions people actually ask before joining Claude Code Club - how fast can a non-coder ship something real, what makes this different from a course that went stale, what happens if you get stuck, why the price is $9 a month, and what the commitment actually looks like. Answers are grounded in what 5,000+ builders in the club have experienced, not in what sounds good in a pitch. If you have a specific question not covered here, you can ask it directly in the community.