Claude Code Home Base — Virtually Structured
Virtually Structured
Claude Code Home Base
A Virtually Structured Resource

Claude Code
Home Base

Build It. Structure It. Let It Remember.

You're going to walk through a guided setup that gives Claude a permanent home in your business — one folder, organized your way, that Claude reads from and writes to every time you open it. No more re-explaining who you are and what matters every single session.

New to Claude Code? Here's the short version: Claude Code is a version of Claude that runs right on your computer instead of just in a browser chat window. That means it can actually see your files, create new ones, and organize folders for you — not just talk back and forth. Everywhere in this guide, "paste this to Claude" just means typing a message and letting it do the work. You don't need to know how to code.
Before You Start
A Claude account able to run Claude Code — a paid plan is required; we'll confirm this in Step 1
This guide open alongside your computer — a second window or a second monitor works great
10–20 minutes for your first setup session — you won't need to do this part again
1Get Claude Code Running
2Your Business Snapshot & Home Base
3Write Your CLAUDE.md
4Build Your Folder Structure
5Set Your Session Permissions
6Fill In Your Context
7Fill In Your Brand
8Connect Your Tools
9Test It & Build Your First Skill

Keep this guide open in one window. Open Claude Code in another. You'll paste each prompt directly into your Claude Code session.

Step 1 of 9 — Get Claude Code Running

Get the tool itself installed first.

Before you can build anything, Claude Code needs to actually be running on your computer. This part is a one-time setup — you won't do it again after today. Go slow here; every click is explained below.

What you need, once:
  • Two small background helper programs (Git and Node.js) that Claude Code relies on — if you don't already have them, each one is a quick download with default settings, nothing to configure
  • The Claude Code app itself, on a paid Claude plan — Claude Code requires a paid plan to run, so check yours at claude.ai/settings/billing before you install
  • A folder on your computer for it to work inside — create a new one now, or point it at one you already use, your call
Open the app and point it at your folder:
  • Once it's installed and open, look near the top of the window for a few tabs — something like Chat, Cowork, and Code. Click Code — that's the mode that can actually see and edit files, not just chat back and forth
  • Find the button to select or create your project folder, and choose the folder you made in the step above
  • The first time, it'll ask if you trust this folder. That's just double-checking it's really the one you meant — click to trust it and continue
One thing that surprises first-timers: Claude will pop up and ask your permission before it runs a command or creates or edits a file. That's not an error and nothing is broken — it's a safety feature so nothing happens without your OK. Click Allow (or Yes) and keep going.
Paste to Claude
Confirm you're set up and ready to go. Tell me the exact folder you're currently working in, then check whether the background tools you rely on (Git and Node.js) are installed and working. If anything's missing, tell me plainly what it is and walk me through installing it, one step at a time. Once everything checks out, let me know I'm ready to move on.
If something's missing, install it and paste this again. Claude will re-check. Once it confirms you're ready, move to Step 2.
Step 2 of 9 — Your Business Snapshot & Home Base

Give Claude a permanent home.

Everything from here builds inside one folder — the same one you pointed Claude Code at in Step 1. That folder holds every file Claude creates and every file you hand it, permanently. Nothing scattered across your Desktop or Downloads.

Paste to Claude
I'm setting up a permanent home base for you to work from in my business — this folder will hold everything you create and everything I hand you, from now on. Before we build anything, get a clear picture of my business. Ask me the following, one at a time:

1. What's my business called, and what do I do in one sentence?
2. Who do I serve — my ideal client or customer, described specifically?
3. What are the 1-2 things that deserve my best energy and attention right now? This becomes the lens you filter every future answer through, unless I say otherwise.
4. What are the different areas of my business where I do repeatable work? (For example: content & marketing, sales, client delivery, operations — list whatever actually applies to me, in my own words, not a generic list.)

Once I've answered all four, summarize what you heard back to me in a few sentences so I can confirm before we build anything.
Confirm the summary feels right. You'll reuse these exact answers in the next few steps, so it's worth getting them accurate now.
Step 3 of 9 — Write Your CLAUDE.md

Write the file Claude reads first.

CLAUDE.md is the front door — the file Claude automatically reads at the start of every session in this folder. It's a map and a set of defaults, not a manual. Keep it short. Paste this into the same Claude Code session.

Paste to Claude
Using what I told you about my business, write a CLAUDE.md file and save it at the root of this folder. Include these sections:

1. Who I am — one or two lines about me and my business
2. Top priority right now — the 1-2 lenses I gave you that should color every answer unless I say otherwise
3. Where things live — a table you'll fill in as we build folders together in the next step (leave placeholders for now)
4. Connected tools — a placeholder section we'll fill in later
5. Simple rules — write 5 short, non-negotiable rules for how you should work with me (for example: match my voice, never invent facts, ask when unsure, keep answers brief unless I ask for depth, plus one more that's specific to my business)

Keep the whole file short — this is a map, not a manual.
Read what Claude wrote. Edit anything that doesn't sound like you before moving on — this file sets the tone for every future session.
Step 4 of 9 — Build Your Folder Structure

Build the system that holds everything.

Now create the actual folders Claude will organize your work into — matched to how your business actually runs, not a generic template.

A typical setup includes: rules/ (behavior rules), context/ (who you are, priorities, decisions), clients/ or customers/ (one file per client), brand/ (voice, offers), skills/ (step-by-step instructions for repeatable tasks), workflows/ (longer multi-step processes), scratch/ (throwaway working files), assets/ (images, logos). Your version might look different — that's the point.
Paste to Claude
Now let's build the folder structure inside this home base. Create the following folders for me:

- rules/ — where your permissions and behavior rules will live
- context/ — where my business profile and current priorities will live
- clients/ (or customers/, whatever fits my business) — one file per client or customer
- brand/ — my voice and my offers
- skills/ — with a subfolder for each business area I told you about in step 2
- workflows/ — with the same subfolders as skills/
- scratch/ — throwaway working files that don't need to persist
- assets/ — images, logos, reusable files

Adjust the names and subfolders if something I described doesn't fit this exact structure — build the version that actually matches my business. Once it's built, update the "Where things live" table in my CLAUDE.md to match what you actually created.
Check that it matches how you actually think about your business. Rename anything that feels off before moving on — this structure is doing a lot of the work.
Step 5 of 9 — Set Your Session Permissions

Decide what Claude can do without asking.

This one file does more to reduce friction than anything else in this system. Without it, Claude asks permission for routine file edits every single session.

Paste to Claude
Create a file at rules/session-permissions.md. Keep it to a couple of short lines: tell me you can read, edit, and create files in this folder without asking first, and that anything permanent or hard to undo — like deleting files or sending something on my behalf — you'll check with me before doing.
This is the whole file. Don't let it grow longer than a few lines — the shorter it is, the more likely you'll actually follow it.
Step 6 of 9 — Fill In Your Context

Give Claude your long-term memory.

This folder is allowed to grow over time — add more as things become relevant. Start with two files. Paste this into the same Claude Code session.

Paste to Claude
Create two files inside context/:

1. context/about-me.md — write my full profile based on everything I've told you so far: my business, how I like to work, my priorities. Ask me any follow-up questions you need first.
2. context/current-priorities.md — a short, living list of what's active right now. Ask me what's currently on my plate before you write it.

Tell me when both are done so I can review them.
Read both files back. This is what Claude will draw on in every future session — it's worth getting right the first time.
Step 7 of 9 — Fill In Your Brand

Make sure Claude sounds like you.

Before Claude writes anything public-facing, it should know how you actually sound — not generic AI voice. Paste this into the same Claude Code session.

Paste to Claude
Create two files inside brand/:

1. brand/voice-and-tone.md — ask me to describe how I sound when I'm at my best (warm? direct? funny? formal?), then ask me for 2-3 real examples of things I've written that sound like me. Write the file based on my answers, including what to avoid.
2. brand/offers.md — ask me to list my current products or services, one line each, so you never have to guess what I sell.

Then add a rule to my CLAUDE.md that says to check brand/ before writing anything public-facing.
The examples matter more than the description. Claude will pattern-match off the real writing samples you give it, not the adjectives.
Step 8 of 9 — Connect Your Tools

Plug in what you actually use.

Claude can act directly in the tools you're already connected to, instead of you copy-pasting between windows. Connect your tools first — then come back and tell Claude what's live. This step also builds your first custom shortcut: a simple command called /close that wraps up every work session the same way, so nothing falls through the cracks.

What's a "custom shortcut"? It's a saved instruction you trigger just by typing something short, like /close, instead of retyping the same request every time. Claude Code lets you build your own. You'll create your first one below.
Paste to Claude
I've connected these tools: [list the tools you connected — e.g. project management, calendar, file storage, email]. Add a "Connected Tools" section to my CLAUDE.md listing them, so you know what's available without guessing.

Then build me a custom shortcut called /close, for wrapping up a work session. When I type /close, I want you to:

1. Look back over what we worked on this session
2. Save a short summary to a notes file dated today — what got done, what's still open, what to pick up next time
3. If anything we did should change how you work with me going forward, update my CLAUDE.md or the right context file so I don't have to explain it again
4. Tell me, in a few short lines, what you saved and what to do next

Save this as a command file so I can trigger it just by typing /close.
Try typing /close at the end of your next real session. That's how you'll know it's working. Once it feels natural, you can build another one the same way — a lot of people also build a /review for a quality check before publishing something.
Step 9 of 9 — Test It & Build Your First Skill

Give it a real task.

The system isn't done until you've actually used it. This step tests everything you just built and creates your first reusable skill file at the same time.

Paste to Claude
Let's test this system with a real task. I want your help with: [describe something actually on your plate right now].

As you help me, pay attention to whether this is something I'll ask for again. If it is, once we're done, write it up as a skill file in the right skills/ subfolder — step-by-step instructions for how to do it again next time, based on exactly what we just did together.
Check the results. Did Claude read your priorities correctly? Did it skip asking permission for routine file work? Did the output land in the right folder? If the voice felt off, go back and sharpen brand/voice-and-tone.md with better examples.

Your home base is built.

Everything Claude needs to work like it already knows your business is now in place — organized the way you actually work, not a generic template.

What You've Built
Claude Code installed and running, pointed at your own folder
A CLAUDE.md front door that tells Claude who you are and what matters right now
A folder system organized around your real business areas — not a generic template
Session permissions so Claude stops asking for routine work
Context and brand files so nothing has to be re-explained every session
Your first tested skill file, built from a real task
Your Next Session
Open a new Claude Code session in this folder. It reads your CLAUDE.md automatically — no re-explaining.

The next time you catch yourself explaining the same process twice, that's your signal: build another skill file.

Your home base is built. Now let it grow with you.
Copied to clipboard