A Practical Guide to Claude Setup
Most people use Claude like a search engine — type a question, get a generic answer, spend the next ten minutes rewriting. The fix isn't a better prompt. It's a system. This course walks you through building one — file by file, lesson by lesson — until Claude works the way you do.
New to Claude Code? Sign up at claude.ai → (we both get a free credit)
Not sure where to start? Take the 10-minute Skills Assessment first → It diagnoses your weakest dimension and tells you which lesson to do first.
What You'll Build
By the end of this course you'll have a working set of context files that route every task to the right specialized voice — for writing, communications, technical work, presentations, and your specific domain.
A CLAUDE.md file that introduces you to Claude once and routes every future task to the right specialized file. Not a bio — a system.
A CLAUDE_CONTEXT.md that captures what's actually happening right now — projects, relationships, frameworks — with a built-in review date.
A three-file writing system that produces first drafts in your voice, your structure, your phrase bank. No more rewriting AI slop.
A RIPEN-structured prompt library that gets better every time you use it. Your most-repeated tasks, never built from scratch again.
A comms file that handles your internal voice — the sensitive emails, the peer navigation, the board briefings. Different instrument, same values.
An adaptation layer for faith-based leaders — theological framing, stewardship principles, and the human moments Claude must never touch.
The Curriculum
Each lesson links to Don's full article in Notion, distills the key concepts, gives you a concrete assignment with a tangible deliverable, and lets you check it off as you go.
Haven't installed Claude Code yet? Sign up at claude.ai (we both get a free credit), then start with the 10-minute Setup lesson →
Take-Home Resources
/model
Quick file edits, doc lookups, simple refactors, tight iteration loops. The default when speed and cost matter more than depth.
Most coding, most writing, most analysis. If you don't have a specific reason to reach for Haiku or Opus, this is it.
Hard architecture decisions, complex multi-file refactors, code review, anything where wrong-answer cost outweighs token cost.
Default to Sonnet. Drop to Haiku for repetitive work. Reach for Opus deliberately — the cost difference per session is real.
Don's writing on the intersection of innovation, AI, and faith — including "A Practical Guide to Claude Setup," the series this curriculum is built on.
The official Anthropic docs for Claude Code — the CLI, slash commands, hooks, MCP servers, and Skills.
Don's tool for building RIPEN-structured prompts by answering a few questions. Pairs directly with Lesson 5.
Building Claude into your own tools? Both links open Anthropic's official console and API documentation.
The wider Innovation portfolio — FaithBot, the AI Canvas, and other production tools built on the patterns in this course.
Stuck on a file? Want a second pair of eyes on your CLAUDE.md? Reach out and start a conversation.
Monday Morning Action Plan
Don't leave with inspiration. Leave with an assignment. Each of these is a concrete first step into the curriculum — pick one and do it before Friday.
If you haven't already, install Claude Code, point it at a working folder, and run your first session. Five minutes. Then you can do everything else in this course.
SetupYou don't need a project to start. You need a folder. Then Claude has somewhere to live.
~/work/claude is fine. The path doesn't matter; the habit does.cd ~/work/claude && claude. Confirm you can see the prompt.Pro tip: if your IT environment restricts CLI installs, Claude Code is also available through claude.ai/code in the browser. Start there if you have to.
20 minutes. Lesson 1's assignment. Write down who you are, who you serve, and how you communicate. This single block changes every output Claude gives you from that point forward.
Lesson 1The most common reason Claude outputs feel generic is the simplest: you never introduced yourself. Fix that first.
~/.claude/CLAUDE.md (Mac/Linux) or %USERPROFILE%\.claude\CLAUDE.md (Windows). This is the global location Claude Code reads every session. If the .claude directory doesn't exist yet, run mkdir -p ~/.claude in your terminal first.Time budget: 20 minutes. If you're at 45 and still going, stop — you can refine later. The first version is the one that matters.
Pick the task you do most often and don't love writing each time. Build one structured RIPEN prompt for it. That single entry is the start of a compound-interest prompt library.
Lesson 5RIPEN = Role, Instructions, Parameters, Examples, Notes. Use it as a brief template. Build one. Reuse it forever.
Shortcut: Don built ripen.donbarger.com — answer a few questions, get a structured prompt out.
Ten minutes. Six dimensions. Get an honest read on where your current Claude setup is weak — and a tailored recommendation for which lesson to do next.
DiagnosticThe Skills Assessment is not a quiz. It's a diagnostic — designed to surface the weakest dimension of your current setup so you don't waste time on lessons that aren't your gap.
Open the assessment: assessment.html →
Common Questions
Quick answers for first-time visitors. Click any question to open.
Claude Code is Anthropic's command-line tool that runs Claude on your computer with persistent memory of your work, your files, and your context. It's the version of Claude that reads the CLAUDE.md files this curriculum teaches you to build.
You install it once. Lesson 0 walks you through it from scratch — press Cmd+Space, type Terminal, follow eight numbered steps. No prior CLI experience required.
No. Most of the curriculum is about teaching Claude who you are — your voice, your context, the frameworks you actually use — not writing code. Pastors, nonprofit leaders, coaches, operators, and writers benefit just as much as developers.
Lesson 8 (CLAUDE_CODING.md) is the one technical lesson, and even it has a path for non-developers: have Claude interview you about your technical context and write the file for you.
Each lesson is roughly 20–45 minutes of focused work — reading the article, building the file, and testing it. Most people pace themselves at one lesson per evening over 2–3 weeks. The Skills Assessment itself takes about 10 minutes and auto-saves your progress if you get interrupted.
No — the curriculum, samples, and assessments are free. Claude Code itself requires a Claude account from Anthropic (free tier available; paid plans start around $20/month for unlimited use). This site is independent and not affiliated with Anthropic.
If the curriculum is useful, the floating "Support this Ministry" button at the bottom of the page funds the global missions work this content was originally built for.
The Skills Assessment measures your personal mastery of the Claude Setup system — how well you've built your CLAUDE.md, your voice files, your prompt library, your domain file. Take it if you're building your own setup.
The Org Readiness Assessment measures your organization's overall AI readiness across leadership, data, technology, people, process, and ethics. Take it if you're leading or advising AI adoption.
Most useful taken together — see both on the assessments page.
Open the lesson modal and use the "See worked samples →" button to jump to filled-in examples on the Samples & Helpers page — there's a starter template plus two real-world examples for every file in the system.
Still stuck? Reach out to Don via the LinkedIn link in the Resources section above.
You can browse the curriculum, samples, and start the assessments without signing in. Signing in (Google) lets you save lesson-complete checkmarks and your assessment results across devices, plus track your skills score over time. Sign-in is shared across the curriculum and both assessments — one click, everywhere.
Director of Innovation & AI Strategy · International Mission Board
Don leads AI strategy and innovation at the International Mission Board, where Claude Code is the daily working tool behind FaithBot, the AI Canvas, the document translation engine, and a dozen smaller production tools. He wrote "A Practical Guide to Claude Setup," the series this course is built on, because most people stop at "Claude is amazing" and never build the system that makes it actually work for their specific job.