Starter

5 Claude Code Files Every Beginner Needs

7 minute readUpdated June 2026Explore more

TL;DR

Five files turn Claude from a generic chatbot into something that knows you, sounds like you, and builds the way you build: CLAUDE.md (your rules), soul.md (your story), design.md (your look), voice.md (your writing), and audience.md (your buyer's exact words). You set them up once, and every session after gets better. No coding required - each file has a copy-paste prompt below.

Before you start: import your memory

The fastest way to give Claude useful context immediately: in Claude's settings, look for the option to import memory from other AI providers. It hands you a prompt - paste that into ChatGPT, Gemini, or your existing Claude chats, then paste the results back. Now Claude has a base layer of context about you before you write a single file.

File 1: CLAUDE.md - the orchestrator

The master file that loads every session. Keep it short. Its job is to tell Claude your rules and where to find everything else - not a life story, a pointer system. Include how you like to work, what to always do, what to never do, and when to read each of your other files.

Create my CLAUDE.md file using the rules below. Just output the file, no explanation.

Structure:
- Who I am: [brief description of your work and goals]
- Operating rules: [how you want Claude to approach tasks]
- Always do: [list]
- Never do: [list]
- When to read other files: soul.md (creating content), design.md (building visuals), voice.md (writing copy), audience.md (writing marketing content)

File 2: soul.md - your origin story

This is who you actually are: backstory, beliefs, the human behind the work. Claude cannot sound like you until it knows you, and this is not your resume. The easiest way to build it is to have Claude interview you rather than writing from a blank page.

I need to create my soul.md file, a document about who I actually am that you will use to write content in my voice. Do not generate anything yet. Instead, interview me. Ask me these questions one at a time and wait for my answer before moving to the next:

1. How did you end up doing what you do?
2. What did you walk away from to get here?
3. What is the opinion you hold about your industry that most people in it would push back on?
4. What is a specific moment that changed the way you work or think?
5. What do you believe about your audience that most people in your space get wrong?

After I answer all five, create the soul.md file.

File 3: design.md - your visual identity

This tells Claude how you look: brand colours, typography, layout rules, visual aesthetic. The fastest way to build it is to find a reference you love (search your aesthetic - minimalist, editorial, bold - and screenshot it), then hand the screenshot to Claude with one instruction. Claude generates an HTML file you can look at and a design.md it can read. Save design.md globally so every visual stays consistent.

Turn this into a design system in an HTML file and a design.md file.

File 4: voice.md - how you talk

This is how Claude learns to write the way you write: sentence structure, vocabulary, what you avoid, your tone. The more real examples you feed it, the sharper the outputs. Pull your best-performing writing - top posts, emails, anything that got real engagement.

Create my voice.md file. Follow these steps in order:

Step 1: Mine what you already know. Go through everything I have written in this conversation. Pull out every pattern you can find: sentence length, vocabulary, what I avoid, how I phrase things.

Step 2: I am going to paste in some examples of my best-performing writing. Analyze these and add the patterns to your findings.

Step 3: Generate my voice.md file with: tone descriptors, sentence structure patterns, vocabulary preferences, what to avoid, and 3 to 5 example sentences that demonstrate my style.

[Paste your best posts, blog content, or any writing that performed well here]

File 5: audience.md - your buyer's exact words

The file that changes conversions. Not just who your audience is, but the exact words they use - because when your content uses their language, it resonates. Build it in two passes: an interview, then research that pulls real quotes from where your audience already talks.

I need to create my audience.md file. Do this in two steps:

Step 1, interview me. Ask these questions one at a time:
- Who are you trying to reach? Describe them in plain terms.
- What is the main problem you help them solve?
- What do you sell, and what does it cost?
- Where does your audience hang out online?

Step 2, after I answer, search Reddit and the web for threads where people like my audience talk about this problem. Find the most engaged posts and pull exact quotes. Also search reviews of similar products or communities. Extract: recurring complaints (exact phrasing), dream outcomes (exact language), fears, and phrases that repeat.

Then generate my audience.md file with all of this included.

How the files work together

The key design is that these files are connected but only load when needed. CLAUDE.md loads every session - it is the orchestrator. soul.md loads when creating content. design.md loads when building anything visual. voice.md loads when writing copy. audience.md loads when writing marketing or sales copy. This selective loading keeps token usage down: instead of one massive file loading on every request, Claude pulls only what it needs. That is how you run a full AI operation for a few dollars a day.

Common questions

  • Do I really not need to code for this?

    Correct. Every file here is plain markdown that Claude writes for you from the prompts above. You answer a few questions and paste in examples; Claude produces the files. There is no programming anywhere in the process.

  • Where do these files live?

    Save CLAUDE.md at ~/.claude/CLAUDE.md so it loads globally across every project. The other four can live alongside it or in a project folder; what matters is that CLAUDE.md tells Claude when to read each one.

  • What is the difference between CLAUDE.md and the other files?

    CLAUDE.md is the orchestrator - short, always loaded, and mostly a set of rules plus pointers. soul, design, voice, and audience are deeper reference files that only load when the task calls for them. Keeping CLAUDE.md thin and the rest specialised is what keeps your token usage low.

  • How long does it take to set all five up?

    About 30 to 45 minutes if you do them in one sitting, since most of the time is answering the interview questions and pasting in writing samples. You can also build one a day - start with CLAUDE.md and voice.md, which you will feel immediately.

  • Do I have to write everything from scratch?

    No - that is the point of the interview-style prompts. For soul.md and audience.md, Claude asks you questions one at a time and assembles the file from your answers. You are talking, not writing documents.

  • How often should I update them?

    Treat soul.md and voice.md as living documents - whenever something significant happens or you find writing that performed well, tell Claude to add it. CLAUDE.md should be updated whenever Claude makes a mistake you do not want repeated.

Want to set these up with a community behind you?

Get the other 3 in the starter stack - free, with 5,000+ builders.

Join the Club