Maison Cler · Claude Code Bookclub · Self-Study

FOUNDATIONS

A beginner's guide to Claude Code —
and why it changes everything for founders,
operators, and builders.

SHIFT

Something changed

Not long ago,
if you had an idea —

you had two options.

Learn to code. Months. Maybe years.
Or hire someone to build it. Expensive. Slow. Dependent.

Most ideas died between the idea and the execution.

That gap just closed.

The new reality

It's already
happening.

Founders are building their own Shopify apps.
Operators are automating entire sales flows.
People with zero coding background are shipping real software — not prototypes, not demos — real, working products.

This isn't hype.

The question is: how long can you afford not to learn this?

Two kinds of AI help

You've used AI before.
This is different.

You type something. It replies. You ask for an email. It writes one. That's conversational AI — useful, but reactive. It waits for you. It answers one question at a time.

Agentic AI is different.

Imagine you say: "Plan my customer onboarding flow, build the emails, connect it to my CRM, test it, and tell me when it's done."

A chatbot helps you think through it. An agent just goes and does it. It reads files. Makes decisions. Takes actions. Comes back only when there's a real choice to make.

It's the difference between having a conversation and having a contractor.

The Claude family · 1 of 3

Claude.ai

The chat interface in your browser. You type. It replies. Great for thinking, writing, problem-solving.

But Claude.ai is still a chat window. Nothing gets built. Nothing gets saved to a project. Nothing gets deployed.

It's the equivalent of texting a really smart friend. Helpful — but they're not going to come over and build you a shelf.

The Claude family · 2 of 3

Cowork

Claude's desktop tool — designed for people who want to automate tasks on their computer without writing code.

Think: file management, document workflows, repetitive tasks across your apps. It can click buttons, move files, fill in forms.

More powerful than Claude.ai — it can actually do things on your machine. But it's still at the level of your desktop. It organizes and automates what you already have.

It doesn't build new software. It makes your existing software easier to use.

The Claude family · 3 of 3

Claude Code

This is where things get serious.

Not a chat window. Not a desktop helper. A full AI agent that can read your project files, write code across multiple files, run tests, fix errors, commit changes, and ship working software.

You describe what you want to build. It builds.

It understands your entire codebase — not just the message you just typed. It works in a terminal or in your browser at code.claude.com.

All three, side by side

Three products. Different jobs.

	Claude.ai	Cowork	Claude Code
Where it lives	Browser	Desktop app	Terminal / Browser
What it does	Thinks & writes with you	Automates desktop tasks	Builds actual software
Think of it as	A smart friend you text	A personal assistant on your laptop	A contractor you hand a brief to
Best for	Thinking, drafting, researching	File & task automation	Shipping real products

Claude Code is the one that builds. The rest of this guide is about Claude Code.

Meet your contractor

Imagine you're
building a house.

You don't need to become a builder. You don't need to learn how to lay bricks or wire electricity.

What you need is a great contractor — someone you hand a brief to, who knows their craft, and who comes back with results.

Claude Code is that contractor.

You describe the house. It builds. You don't tell it which nails to use — you tell it how many bedrooms you want and what the kitchen should feel like.

How a session works

Six steps.
Same every time.

You open a project folder.
Claude Code reads your files and understands the context.
You describe what you want — in plain language.
It plans. It codes. It runs. It fixes errors. It iterates.
It asks your permission before anything risky.
You end up with working, committed code.

You describe the outcome. It figures out the path.

What it looks like on screen

Three windows.
One view.

your-project — VS Code

Files

▶ company-context/

CLAUDE.md

index.html

styles.css

README.md

Editor
1# My Coffee Brand
2
3## Brand voice
4Warm, editorial,
5understated.
6Never exclamation.

Claude Code
› build me a landing page
  for our coffee brand.
claude is thinking...
✓ created index.html
✓ created styles.css

Files on the left. Code in the middle. Claude Code on the right. Everything in one place.

YOU

Why this matters

What Claude Code
can do for your job.

If you're a founder: describe a landing page and have it live by dinner — instead of waiting two weeks on a freelancer.
If you're in sales: hand Claude a list of 50 prospects. It enriches each profile, scores fit, and drafts the opener — in 12 minutes instead of 4 hours.
If you write copy: five product descriptions, on-brand, in three tone options — 8 minutes instead of 2 hours.
If you run operations: "Pull this week's numbers and format my report." Same template, every Monday. 3 minutes.

The goldfish problem

Every session
is day one.

Here's something that trips up everyone the first time:

Claude forgets everything between sessions.

It doesn't remember your project setup. It doesn't know your tech stack preferences. It doesn't know that you always want dark backgrounds, or that you hate exclamation marks in copy.

So it has to rediscover all of this every single time. That's slow. And it leads to inconsistent results.

Like hiring a new contractor every single day — and re-explaining everything from scratch.

The fix

CLAUDE.md

A simple text file that lives in your project folder. Claude Code reads it automatically at the start of every session.

Think of it as the onboarding document you'd give a new contractor before they touch your project. Everything they need to know — written once, used every time.

Your project's tech stack and architecture
Your brand voice and style preferences
Libraries you use (and ones to avoid)
Your "never do this" rules
Anything a smart contractor needs before day one

How to build it

Don't write the perfect
CLAUDE.md on day one.

Start with 10 lines. The basics.

Then, every time Claude does something you don't like — uses the wrong colors, adds a feature you didn't ask for, deploys without permission — add a rule.

After two weeks, your CLAUDE.md will be perfectly calibrated. It will have caught every bad habit and corrected it.

your-project/ ├── CLAUDE.md # Rules and preferences ├── company-context/ │ ├── COMPANY.md # Who you are, your numbers │ ├── BRAND-VOICE.md # How you sound │ └── PERSONAS.md # Your 3 main customer types

Split your business context into separate files. Claude reads all of them at the start of every session.

Why sessions go bad

Claude's brain
is a whiteboard.

Every message you send, every file it reads, every error it encounters — all of it gets written on the whiteboard.

Start Whiteboard is clean. Claude is sharp, focused, precise.

20 min in First request, third revision, an error — all stacked up.

1 hour+ Whiteboard is full. Forgets constraints. Contradicts itself. Builds things you told it not to.

Sessions don't go bad because Claude got dumber. They go bad because the whiteboard is full.

The fix

/clear

Erases the whiteboard. Completely. Fresh start. Your CLAUDE.md reloads automatically — so Claude still knows your project and your rules. It just loses the clutter.

This is the single highest-ROI habit you can build. Use it between tasks. Use it when things feel off.

/compact

Squeezes the whiteboard — keeps the important context, removes the noise.

For when you're deep in a build and a full reset would lose momentum.

Rule of thumb: one task per conversation. Start new task? /clear.

Repeatable playbooks

Skills turn great
one-off results
into a system.

Even with a great CLAUDE.md, you'll find yourself doing the same kinds of tasks over and over. "Review this for SEO." "Build a product page using our layout." "Write a customer email in our voice."

Skills are saved, reusable instructions you can trigger on demand. Instead of re-explaining your SEO process every time, you create a skill called /seo-review.

Think of it like a restaurant recipe book. The chef doesn't reinvent the carbonara every Tuesday — they follow the recipe. New staff learn it. The result is consistent.

Skills are how Claude Code stops being a tool you use — and starts being a system that runs.

The full picture

Three pieces.
One system.

CLAUDE CODE

The agent that builds. You describe what you want — it reads your files, writes code, fixes errors, and ships.

+

CLAUDE.MD

The brain that remembers you. Your rules, your brand, your stack — loaded automatically every session.

+

SKILLS

The playbooks that repeat consistently. One command triggers a full workflow, every time.

Together, these three things turn a powerful tool into a reliable business system.

You already have
the ideas.

Now you have
the contractor
to build them.

Start small. Start today.
The system builds itself as you learn it.

FOUNDATIONS

Not long ago,if you had an idea —

It's alreadyhappening.

You've used AI before.This is different.

Claude.ai

Cowork

Claude Code

Three products. Different jobs.

Imagine you'rebuilding a house.

Six steps.Same every time.

Three windows.One view.

What Claude Codecan do for your job.

Every sessionis day one.

CLAUDE.md

Don't write the perfectCLAUDE.md on day one.

Claude's brainis a whiteboard.

/clear

/compact

Skills turn greatone-off resultsinto a system.

Three pieces.One system.

You already havethe ideas.

Now you havethe contractorto build them.

Not long ago,
if you had an idea —

It's already
happening.

You've used AI before.
This is different.

Imagine you're
building a house.

Six steps.
Same every time.

Three windows.
One view.

What Claude Code
can do for your job.

Every session
is day one.

Don't write the perfect
CLAUDE.md on day one.

Claude's brain
is a whiteboard.

Skills turn great
one-off results
into a system.

Three pieces.
One system.

You already have
the ideas.

Now you have
the contractor
to build them.