Seven Things to Build in Your First Week With Claude

You have typed something into Claude, got back something almost useful, and had no idea what to do next.

That is the most common thing people write to me, and thank you to everyone who has. The most common version of it is three words long: where to start.

The trouble is not that this is difficult. It is that nobody tells you when you are finished. "Explore it" has no end in it, so there is never a moment where you get to feel you have learned something. So here is a week with seven endings in it. One small thing a day, about half an hour each, and every evening something exists that did not exist that morning.

Day 01. A room for one thing you do often.

Pick one recurring part of your life that quietly drains you. Planning the week. Keeping up with a course. Handling the same kind of message over and over. Make a Project, which is simply a named workspace, and call it after that job in plain words.

Then write down the four things that are true every single time: who you are, what kind of help you want, how it should sound, and your standing rules. That block is the room. From now on, every conversation you open inside it already knows your situation, and you stop explaining yourself from the beginning.

About twenty minutes, and you will use it again tomorrow.

Day 02. One request you will reuse every week.

Choose something that comes back on a schedule. A weekly update. A note to the same group of people. The summary you always end up writing on a Friday.

Write it out in full, once: the background, the kind of writer you want Claude to be, what finished looks like, the exact shape you want back, the tone, and the things it must never do. Run it on this week's real material. Fix whatever missed, and keep the fixed version.

Next week everything in it stays the same except the new details you paste in. That is the difference between a lucky answer and something you own.

Day 03. A small tool you will actually use.

Something small and real. A tip splitter. A tracker for one habit. A countdown to a date that matters to you. Small and useful beats ambitious and vague, especially today.

Describe it in plain English: what it is for, who uses it, what goes in, what comes out, and what should happen if somebody leaves a box empty. It gets built in front of you, on the screen, and you use it. No installing, no code.

Then ask for a list of ways to break your own tool, and work through the list yourself. Most first builds hide two or three problems, and finding them is really the point of the day.

Free Claude toolkit. The companion pack for my Claude book is free: ready-made Project instruction templates, and more than five hundred numbered prompts you can copy and paste. No card, and you can leave the list in one click. Get the toolkit →

Day 04. One job too big for a single message.

Planning an event. Drafting something with several sections. Researching a decision you actually have to make. The kind of job you avoid asking for because it will not fit into one request.

Ask for a numbered plan first, and read it before anything else happens. That one step is worth more than everything that comes after it. Approve it, or change it in a line or two, then let the first step run and look at each piece as it arrives.

Count how many times you stepped in. For a well-described job it is usually three or four times across the whole thing, and that small number is what steering looks like when it is working.

Day 05. Your method, saved so you stop retyping it.

Take Tuesday's request, the one you now know works, and save it as a Skill: your method kept in one place, so it runs the same way every time you call for it.

Six questions decide whether it will hold, and I wrote them out one by one in teach Claude your way of doing something, once. Half an hour, and the thing you worked out on Tuesday stops depending on you remembering it.

Day 06. One gentle automation.

Something that reads and prepares and never sends. A short note about what today holds, waiting for you in the morning. A folder of drafted replies for one kind of message, sitting ready for you to read and send with your own hand.

Give it access to the one app the job needs, and nothing else. The rule for the whole day fits in a sentence: it may read, it may draft, and it may not send, delete or buy anything. The worst that can happen is a note you glance at and ignore.

If you want that rule in full, with the reasoning behind it, it is in what not to let run unattended.

Day 07. Hand one of them to somebody else.

Take the best of the six and write down how it works, step by step, clearly enough that another person could follow it without you in the room.

This sounds like an optional extra and it is the day that changes things. Writing the steps down is what shows you whether you understand what you built. It is also the line between something you did once and something you can do again in March.

What this will not do.

This will not show you everything Claude can do. It is seven small pieces, chosen because each one finishes. There is a great deal more, and it will still be there next week, which is rather the point of not chasing it now.

It will not run smoothly on all seven days either. Something will come back wrong, usually around day three or four. That is ordinary, and it is not a sign you missed a step earlier. Ask again with one more detail added, and watch what that detail changes.

And it will not stay accurate about buttons. Menus get moved and renamed. The seven things are what matters here, not where anything sat on the screen in July.

One thing to do before the next post.

Write the seven days on a piece of paper, one line each, and put a real date beside every one of them. Not a plan for someday. Seven dates you can cross off.

And if seven feels like a lot this evening, do Day 01 on its own. Setting up one Project is the twenty minutes that pays back fastest, and nothing about it can go wrong.

If you want the whole system rather than one week of it, that is what I wrote Claude AI Bible (7 Books in 1) for. Seven books in one volume, one behind each of these seven days, with the full walkthrough for every one and more than five hundred numbered prompts to copy.

This post is part of my Claude series. The one that started it is Why Claude Gave You a Great Answer on Monday and a Flat One on Tuesday.

Tomasz