Build a working app from scratch with Claude — no coding experience required. Ten hands-on lessons from a plain-English idea to a running app.
Who it's for: Physicians with zero coding background who want to build a real, working app with Claude
Build a working app from scratch with Claude — no coding experience required. Across ten hands-on lessons you go from a plain-English idea to a running app on your own computer, directing Claude every step of the way. You'll set up your machine, write a spec, scaffold a website, build a backend and database, and wire in Claude itself to power 'The Consult Room' — a council of AI advisors that weigh in on a question and explain the answer plainly. Educational only, not for clinical decisions.
10 lessons · $299 · lifetime access · certificate of completion
Takeaway: Coding with Claude is a loop: you describe what you want, Claude writes the code, you run it and refine — and you stay the architect throughout. An app is three parts — a frontend, a backend, and a database — and this course walks one idea all the way to a working program on your own laptop. No computer science degree required; your clinical judgment is the rarest input.
Takeaway: Your workshop is built. You opened a terminal, you installed four free tools — Node.js, Claude Code, VS Code, and Git — and you verified each one with a version command instead of hoping it worked. And you learned the simplest possible success signal: an exit code of zero means the last command succeeded; anything else means look closer. You only do this once, and you've done it. From here on, we build.
Takeaway: You turned an idea into a plan. A spec Claude can build from answers four things — what it does, the one page, the data, and the stack — and our whole app fits in one paragraph. Underneath it sits a simple data model: a Question, the Answers, and a Verdict. And written into the spec from the start is the boundary that keeps it honest — this is a learning tool, educational only, never for clinical decisions, and no real PHI. The blueprint is done. Next, we build.
Takeaway: You just built your first website. One create command scaffolded a Vite React app; 'npm run dev' put it on localhost:5173; and a plain-English request turned the starter page into the front door of The Consult Room — a title, a textarea, and an 'Ask the Room' button. The button doesn't do anything yet, and that's exactly where we're headed next. You directed every step. Claude did the typing.
Takeaway: A web app has four parts: a frontend you see, a backend that thinks, a database that remembers, and an API that lets the frontend and backend talk — using HTTP to make requests and JSON to carry the data. Map that onto The Consult Room: a React page on 5173, a FastAPI backend on 8000, a SQLite file behind it. Every button click is one round trip — click, request, work, response, screen. See that shape once, and you'll see it in every app you use.
Takeaway: The backend is where your app does real work. We built one route — POST slash-ask — that takes a question, saves it to a single-file database called SQLite, and returns an answer. For now that answer is a placeholder, and that's on purpose: we proved the whole pipe works before adding anything clever. One command, uvicorn, brings it to life on localhost port eight thousand. You now have a server with a memory — and every future feature is just another route shaped like this one.
Takeaway: Your app thinks now. You installed the Anthropic SDK, stored your key safely in dot-env — and never commit that file — and made one call to Claude with a model, a system prompt, and the question. The system prompt decides who the advisor is, and changing it changes the whole answer. Your slash-ask route returns Claude's real reply where the placeholder used to be. The real apps reach the same Claude through AWS Bedrock for data control — but the direct API you used today is exactly right for where you are.
Takeaway: A council is just one model wearing three hats. You define three advisors — the Generalist, the Skeptic, and the Specialist — as three short system prompts, loop your question through all three to collect three answers, then add a Chair that weighs them into one balanced verdict. Four Claude calls, almost no new code, and your app now reasons like a room instead of a single voice. That's the LLM-Council pattern — and you built it.
Takeaway: Feynman is the council's clarity step: one more system prompt that takes the Chair's verdict and re-explains it with no jargon and a single good analogy — the way you'd teach a bright beginner. You added one Claude call, returned one new field from /ask, and rendered one new section on the page. The pipeline is now complete: question, council, Chair, Feynman, page. You've built a real multi-step AI app — and it explains itself.
Takeaway: You can now run your app with two commands, fix what breaks by pasting the error to Claude, and you know the bright lines: no real patient data in a learning app, and this is a tool for understanding, not a clinical decision-maker. You took one idea from a blank screen to a working, multi-step AI application — and you understand every piece. The method is yours now: describe, build, run, refine. Keep going.