CodersBee logo — a yellow beeCodersBee· The AI ToolboxAsk on WhatsApp
🧰 The AI Toolbox · offering 2Ages 11+, with a parent as clientNeeds Claude Pro · you buy itOutline finished · session pages still being written

You write the spec.
Your kid ships it.

15 sessions in which your kid builds actual working software with Claude Code — and you are the client. You describe what you want. They scope it, build it, and hand it over. Then there is a demo day at your dinner table, and you either accept delivery or send it back with notes.

Your child builds and ships real software with an AI coding agent, and you play the client who signs it off.

Where this camp is today

The 15 sessions below are the finished outline: the order they run in, what gets built in each one, and the job you do while it happens. What is not finished is the written session pages — the step-by-step your kid follows at the keyboard. Those are being written now, and we are not putting a date on them. So read the whole outline before you decide, and ask Manisha where the writing has reached. There is no checkout here, so nothing is paid before that conversation.

💬 Join the builder campManisha replies on WhatsApp — there is no checkoutStart with the Claude PlayCampThe prerequisite · session 1 is free
Read this first

Two things you need before you buy.

Claude Pro — bought by you

Requires Claude Pro (about $20/month), purchased by you directly from Anthropic. Most families finish in about two months.

You are the one who buys it — directly from Anthropic, in your own name, on your own card. It is not part of what you pay CodersBee, it is not bundled into the price below, and it is not ours to refund. Treat it the way the Agentic camp treats Python: something the family arranges before day one, not something we sell you. If you would rather not take on a paid plan at all, do the Claude PlayCamp instead — it runs on a free account, start to finish.

The Claude PlayCamp, first

This camp assumes the two of you already did the Claude PlayCamp — that you know what a model is, why it makes things up, and how to check it. We do not re-teach any of that here, and a teenager who skips it spends this camp confused about why the tool behaves the way it does.

  • Ages 11+, with a parent as client
  • The account is still the grown-up's — Claude is an adults-only signup, 18+
  • Any laptop with a terminal. No prior Python needed
See the Claude PlayCamp →
How the grown-up fits in

You are the client, not the audience.

Nobody aged 14 wants to do a bonding activity with a parent. So this camp does not ask for one. It gives you a job instead — and it turns out that being taken seriously by your parent as a customer is a better afternoon than being praised as a kid. 6 of the 15 sessions run on that client relationship.

You write the brief
In session 2 you hand over the content for a family page. In session 8 you write the whole game spec on paper first — what you control, how you win, one thing it must never do.
They scope and build
They come back with questions, then with a plan, then with a working version. Claude Code is the workshop; the decisions are theirs.
You play it and say so
In session 10 you play for five minutes while they watch in silence and write down every place you hesitate. Every hesitation becomes a task before you sign it off.

What this is not: it is not a course where a teenager watches videos alone and you get a completion email. Every one of the 15 sessions gives you a job — a brief to write, a plan to read back, a bug report to file, a demo to sit through. If you would not do those things, this camp will not work in your house — and we would rather say that now.

The whole outline, nothing hidden

All 15 sessions.

Every session ends with something on the screen — a page, a commit, a bug found, a plan sent back. One game runs through the middle of the camp: session 8 builds it from your spec, 9 debugs it from your bug reports, 10 polishes it, 12 puts it on a link you can send. The capstone at 14 is the builder's own idea, start to finish.

This is the outline in full, and it is settled: each session's one idea, what happens at the keyboard, and which ones put you in the client's chair. It is also all that exists today — the written session pages are still being made, and nothing is hidden behind the price that is not on this page.

Unit 1 · The agent in your folder
Session 1
Meet Claude Code
Claude Code is not a chat window. It lives in one folder on your computer, reads the files there, changes them and runs commands — read, act, check, repeat, until the job is done.
At the keyboard: Set up a fresh projects folder, ask Claude Code to look around and describe what it found, then give it a one-line change and watch every step of the loop go past.
Session 2
First Build — the family page
A real project starts with a real brief. The person who wants the thing describes it; the builder turns that description into files that run.
At the keyboard: The parent supplies the content — names, a photo, three places the family loves, one line each. The child hands that brief to Claude Code and opens the finished page in a browser.
You are the client
Session 3
Small Asks Win
One big vague ask gets you a mess you cannot review. Three small, checkable asks get you three things you can accept or send back one at a time.
At the keyboard: Take the leftover complaints from the family page and split them into three separate asks — colour, layout, wording — running and reviewing each one fully before starting the next.
You are the client
Session 4
Plan First
Plan mode makes the agent say what it intends to do before it touches a single file. Reading a plan is always cheaper than undoing the work.
At the keyboard: Switch on plan mode, ask for a new section of the site, read the plan together line by line, and send it back at least once with a change before anyone approves it.
You are the client
Unit 2 · Habits of a real developer
Session 5
Save Points
A commit is a save point, the way a game has save points. Once you have them you can break anything on purpose, because getting back is one command.
At the keyboard: Commit the working site, then deliberately ask for something awful, look at the damage together, and roll all the way back to the save point.
Session 6
Teach It Your Project
A CLAUDE.md file is a standing instruction the agent reads every time, so you stop repeating the same three sentences in every message.
At the keyboard: Write the project's house rules into CLAUDE.md — spacing, tone, which files must never be touched — then repeat an earlier request and see exactly what changed.
Session 7
Skills & Memory
A skill is an instruction that packs itself up. You write it once, and the agent reaches for it on its own when the job matches — no reminder needed.
At the keyboard: Bundle the family's own style into one skill — the colours, the sign-off, the shape of a good headline — then start a brand-new page and watch it get applied without being asked.
Unit 3 · Build something real
Session 8
Big Build I — start the game
Big things get built in slices, and slice one is the smallest version that already runs. Ugly and playable beats beautiful and imaginary.
At the keyboard: Build slice one of a browser game from the parent's spec: something you can actually play, however rough it looks, by the end of the session.
You are the client
Session 9
Debug Like a Pro
You cannot fix what you cannot reproduce. Steps first, then the smallest test that still shows the problem, then — and only then — a fix.
At the keyboard: Work three real bug reports end to end: reproduce each one exactly, cut it down to the smallest case, find the cause, fix it, then check the other two still work.
Session 10
Big Build II — finish and polish
Polish is a list, not a feeling: a title, a score, a restart button, one sound. Ship the list and you can tell when you are finished.
At the keyboard: Turn the polish list into numbered tasks, work through them with small asks and save points, and keep the game playable after every single change.
You are the client
Session 11
Claude's Toolbelt
Connectors give the agent hands outside your folder. Reading something and changing something are two different permissions, and you grant them one at a time, on purpose.
At the keyboard: Add one read-only connector, ask a question that genuinely needs it, then go back and look at exactly what the permission prompt agreed to.
Unit 4 · Ship it, check it, show it
Session 12
Ship It
Software nobody else can open is just a folder on your laptop. Deploying is what turns it into a link you can send.
At the keyboard: Deploy the game to a free host, test the live link on a phone, fix whatever only breaks on the phone, then send it out.
Session 13
Agents That Check Their Own Work
An agent that checks its own work is really two agents: one that builds, and one whose only job is to look for what is wrong. Building that loop from scratch in Python is what the Advanced Agentic AI PlayCamp is for — here you use it.
At the keyboard: Plant one bug on purpose, then send the change to a second agent whose only instruction is to review it, and compare what it caught with what you know is in there.
Session 14
Capstone Build
Everything so far in one project, chosen by the builder: a brief, a plan, small asks, save points, a review pass at the end.
At the keyboard: The child picks their own idea and takes it end to end in one sitting — plan mode first, commits as they go, small asks throughout, a reviewer pass before they call it done.
You are the client
Session 15
Capstone Showcase
A demo is a story in three parts: here is the problem, here is the thing I made, and here is the bit that nearly beat me.
At the keyboard: Run a live demo of the deployed project for whoever is in the house, take real questions, then write down the next thing they want to build.
Price

$149 once. Or free, if you already learn with us.

$149· about ₹12,900
One payment for the camp. Separate from the plan you buy from Anthropic.
  • The whole 15-session outline above — each session's idea, its build, and your job in it
  • The written session pages as they land. They are being made now, and we do not put a date on them
  • Help when a build gets stuck — spelled out in full below

Free with 1:1 classes

Already taking live 1:1 classes with us? This camp is included at no extra cost, like every other PlayCamp we make. The 1:1 track stays the best deal in the shop. See all offerings →

What the plan costs, honestly

The figure in the requirement above is Anthropic's, and it is theirs to change — check their pricing page before you commit. It is a monthly charge from them, on top of this camp, and you cancel it with them whenever you like. Plenty of families keep it for the couple of months the camp runs and then decide.

What we do and do not promise

The honest bit.

Help when you are stuck, and office hours

Help with the course comes over WhatsApp whenever the two of you are stuck — send the prompt, what came back and where it went wrong — plus office hours when we run them, announced on WhatsApp, for the questions that are easier to talk through than to type.

A stuck evening is that message, then — not a lookup. There is no written troubleshooting page for each session, because the session pages themselves are still being written.

That is all of it. This camp carries no class times and no per-family slot on a teacher's timetable. If you want live teaching, that is what the 1:1 classes are for.

Things we are not claiming

  • An independent course. CodersBee wrote it; we are not affiliated with Anthropic, and nothing here is endorsed by them. Claude Code is their tool — we teach families to use it
  • The paid plan is bought by the family, from Anthropic, and is not part of this price
  • Not a software-engineering qualification. No certificate, no grades — what you keep is the software your kid built and the notes the two of you wrote while reviewing it
  • Claude Code changes fast, and a step of ours will sometimes name a menu Anthropic has since moved. We teach what the tool is doing rather than where the button sits, but tell us on WhatsApp when a step stops matching and we will fix it and say so plainly

Tell them what you need. See what comes back.

Start with the Claude PlayCamp if you have not done it — session 1 is free and takes an evening. Then come back here with a plan and a brief.

CodersBee homeClaude PlayCampFree session 1WhatsApp us

An independent course about Claude Code, written and taught by CodersBee. We are not affiliated with Anthropic, and nothing on this page is endorsed by them. Claude, Claude Code and the plans that unlock them are Anthropic's — families buy those directly from Anthropic, not from us.

© 2026 CodersBee