Your Claude Weekend Plan: 5 Steps, With the Prompts
Most people open Claude, explain their business again, and get an answer that could be for anyone. Give it one weekend. These 5 steps set Claude up for your business, with the exact prompt for each one.
You don't learn Claude by reading about it. You learn it by setting it up for your business and using it every week.
Here's the weekend. Two steps on Saturday, three on Sunday. One prompt for each.
Before you start: download the Claude desktop app from claude.ai/download, sign in, and switch from Chat to Code at the top. When it asks for a folder, make a new folder called my-business and pick it. Every step below happens in that folder.
Step 1. Saturday morning: your business file
This is the file that tells Claude who you sell to, what you sell and what they struggle with. You write it once. After that, you never explain your business again.
Claude interviews you, one question at a time. Answer like you're talking to a friend. Short answers are fine.
Build my business file. It is one file called business.md in this folder. Interview me one question at a time. Wait for my answer before you ask the next one. Number each question, like "Question 3 of 8". Ask about these, in this order: 1. Who I sell to: one specific kind of person. 2. What I sell: each offer, what it is, and the price. 3. What they struggle with, in their own words. 4. What they've already tried that didn't work. 5. The result they want. 6. Why they buy from me and not someone else. 7. Where they find me (Instagram, YouTube, email, referrals). 8. The questions they ask me most. If an answer is thin, ask one short follow-up before you move on. Then write business.md, with a short section for each one. Use my words where you can. Then make CLAUDE.md in this folder if it doesn't exist, and put this line at the very top: @business.md That line makes you read business.md every time I start a chat here. Rules: - Use only what I tell you. If something is missing, write [ask me]. Never invent numbers, results, stories or quotes. - Plain words. No jargon. When you're done, show me business.md.
Claude Code asks before it saves a file. Say yes.
Step 2. Saturday afternoon: your proof file
Your real numbers. Your real stories. Your results.
AI got my numbers wrong more than once. Now it reads them from one file.
If your numbers aren't written down, AI fills the gap with a guess. A guess about your results in a post or on a sales page is a real problem. So put them in one file, and make Claude use only that file.
Gather what you have first: sales, students, client wins, your own story, messages people sent you. Then paste it all into the brackets below.
Build my proof file. It is one file called proof.md in this folder. It holds my real numbers, my real stories and my results, so you never have to guess them. Here is everything I have: [paste your real numbers, your stories and your students' or clients' results here] Then: 1. Sort it into 3 parts: My numbers, My stories, and Results (my students' or clients'). 2. Write every number exactly as I gave it. Next to each one, write when it happened and where it came from. If I didn't tell you when or where, ask me. Ask all your questions in one message, then wait. 3. Only write what I gave you. Never round a number, add to it or make one up. If something is unclear, write [check] next to it. 4. Add this line to the top of CLAUDE.md, under @business.md: @proof.md 5. Add this rule to CLAUDE.md: "Every number, result or story about me or my students comes from proof.md, word for word. If it's not in proof.md, ask me. Never guess." Show me proof.md when you're done.
When you get a new result, add it the same day. Paste "Add this to proof.md:" and the new result.
Step 3. Give each part of your business its own home
One for content. One for offers. One for clients. Each home is a folder with a short note inside that says what's going on in that part right now. So every chat already knows what's going on.
Give each part of my business its own home in this folder. Make 3 folders: content, offers and clients. In each one, make a CLAUDE.md file that says: - What this part of my business is for, in one or two lines. - What's going on right now, and what's next. - The files that live in this folder. - Any rules for this part. Before you write them, ask me what's going on right now in each part, all in one message. Then wait for my answers. Then add this to the main CLAUDE.md in this folder: ## My business has 3 homes - content/: my posts, scripts and emails. Read content/CLAUDE.md before any content work. - offers/: what I sell, my sales pages and launches. Read offers/CLAUDE.md before any offer work. - clients/: my clients and students. Read clients/CLAUDE.md before any client work. When something changes in one part, update that part's CLAUDE.md, and tell me what you changed. Use only what I tell you. If I don't know something yet, write [ask me].
Keep each home short. When a launch ends or a new one starts, tell Claude, and it updates that home.
Step 4. Sunday morning: connect your apps
Your email, your Google Drive, your calendar. So Claude works inside the tools you already use.
In the Claude desktop app, go to Settings, then Connectors. Add Gmail, Google Drive and Google Calendar, and sign in to each one. Only add the apps you really use. Every app you connect is more of your stuff Claude can read.
Then come back to your my-business folder in Code and paste this. It checks what works and writes your rules down, so Claude never sends or changes anything without asking you.
Check my connected apps. For each of these, tell me if you can reach it: Gmail, Google Drive and Google Calendar. - If you can, do one small read-only check: the subject line of my newest email, the name of one file in my Drive, or my next calendar event. Don't send, share, change or delete anything. - If you can't, tell me in plain steps how to add it, and that I may need to start a new chat after I add it. Then add this to CLAUDE.md in this folder, with the apps that work filled in: ## My connected apps - [the apps you can reach] Rules: read anything you need from these apps. Never send an email, share a file, or add or change a calendar event without asking me first.
Step 5. Sunday afternoon: turn one job into a skill
This is where most people stop too early.
A skill is a saved set of steps for one job. Claude follows it the same way every time, so you stop explaining the job again.
I have one for my reel scripts. The same rules are followed in every script so it sounds just like me.
Pick one job you do every week. Your weekly email. Your posts for the week. Your client check-in notes. Fill in the job, then paste this:
Turn one job I do every week into a skill, so you do it the same way every time. The job: [the job, like "write my weekly email to my list" or "plan my posts for the week"] Step 1. Ask me up to 6 questions about this job, all in one message, then wait for my answers. Ask: - When I do it, and what I need before I start. - The steps I follow, in order. - My rules for it: what to always do and what to never do. - What a great one looks like. Ask me to paste one I did before. Step 2. Write the skill as a file at .claude/skills/[short-name]/SKILL.md in this folder. Pick a short name with dashes, like weekly-email. Start the file with exactly this, filled in: name: [the short name] description: [what the job is, plus the words I'd use to ask for it, like "write this week's email" or "my newsletter"] Under that, write: - What to read first: business.md, proof.md, and the home folder that fits this job. - The steps, in order. - My rules. - The example I pasted, word for word, marked as the example to match. - This rule: any number, result or story about me comes from proof.md only. If a piece needs a story or detail that isn't there, leave a [my story: what's needed] blank for me to fill in. Never invent one, not even one line. Step 3. Tell me how to use it: start a new chat in this folder and ask for the job in my own words, or type / and the skill's name.
Claude Code asks before it saves the skill, because skills live in a hidden folder called .claude. Say yes.
Then start a new chat in the same folder and ask for the job, in your own words. Claude finds the skill and follows it. Every time you fix something in the result, ask Claude to add the fix to the skill. It gets better every week.
The limits, honestly
- The files only know what you tell them. Thin answers make thin files. Update proof.md and your homes when things change, or Claude works from old facts.
- Claude Code reads these files in the my-business folder. Open it in a different folder and it won't see them.
- Connected apps let Claude read your email, files and calendar. Only connect the ones you need, and keep the rule that it asks before it sends or changes anything.
- Keep private client details you don't need out of the clients folder.
- A skill is only as good as the example you give it. Paste a real one you were proud of, not a rough draft.