WEBBLABSCLAUDE · DAY ONEJoin the 30-Day Challenge ↗
An open graphite laptop on a dark stone desk, with a warm orange light across the wall.
WEBB LABS / CLAUDE SETUP GUIDE

Your Claude setup
starts here.

Ready for tomorrow.
One useful step at a time.

GUIDED DEMO01 · StartIllustrated interface · no accounts connect here
ClaudeWhat can we work on?
How can I help you today?
+ChatCowork↑

A question. Some notes. One small job.

Chat for a conversation. Cowork for a task.
Claude Code is for building software; you won’t need it today.
First, open Claude.
This is where you ask.
Give it something real.
One detail changes the plan.
Your next 30 days.
Choose what carries forward.
Give this job a home.
Create “My week.”
Set the rules for this job.
Now make it sound like you.
Now, bring in an app.
Choose Connectors.
Find Google Calendar.
Read what it can access.
Finish sign-in in your app.
Test one event you know.
The time comes in.
Then the request.
Then the details.
Let it ask before it guesses.
Check the source, not the tone.
Keep a chat out of memory.
Bring it together.
Tomorrow looks different.
Make the proven job repeat.
The pieces now work together.
THE FIRST WIN

You have a plan.
Now use it.

Check the times. Read the draft. Take the first action. Keep the setup simple until it earns a place in your day.

Keep the steps handy ↓
YOUR TAKE-WITH-YOU GUIDE

Every step.
Every prompt.

Open a chapter for its steps and prompts. Your checkmarks stay in this browser.

Download the fictional practice notes ↓
01–05Your first useful answer
01First, open Claude.

Claude is an AI assistant you can talk to, give files to and ask to help with work. Get the app, sign in, then keep it beside this guide.

Check: You can see a new conversation in your own Claude account.

02This is where you ask.

Choose New in the sidebar. Type a request in the message box and send it. Start with one small job: getting ready for tomorrow.

I want to prepare for tomorrow. What details do you need from me? Ask one question at a time.

Check: Claude asks for your commitments or the job you want to prepare for.

03Give it something real.

Claude needs the facts before it can make a useful plan. Copy these fictional notes into the same conversation. You can finish the whole guide with them.

# Prepare for tomorrow · fictional practice material

Everything below is invented for this tutorial. No private account connection is needed to use this file.

## About Alex

I coordinate internal training at a fictional company. Keep answers short and practical.

## Calendar example

Tomorrow, local time:
- 9:30–9:45 a.m.: team check-in.
- 10:00–10:30 a.m.: training planning meeting.

## Email example

Subject: Agenda for tomorrow

Alex, could you send a short agenda before our 10 a.m. planning meeting? We need to decide which session to run first and who will prepare the worksheet. Thanks, Sam.

## Project notes example

Meeting: training planning.
Decision 1: Run the email-writing session or the meeting-notes session first.
Decision 2: Choose who will prepare the practice worksheet.
No decision has been made yet. No owner has been assigned.

## Three writing samples

Nice: Thanks for getting this together. Thursday works for me. I'll bring the notes.
Firm: We need the final version by noon. Please flag anything that's still missing.
Quick: Got it. I'll check and get back to you this afternoon.


Summarize tomorrow’s meeting, the request and the two decisions. Keep it short. Do not plan a preparation slot yet.

Check: The meeting is at 10, Sam needs an agenda, and both decisions remain open.

04One detail changes the plan.

Tell Claude you need 20 quiet minutes before a meeting. One useful slot is 9:10–9:30; 9:30–9:45 is already taken. Earlier slots work too if they leave a full 20 minutes.

I'm Alex. I coordinate internal training. I need 20 quiet minutes to prepare before a meeting.
Keep answers short and practical. Ask when a missing detail changes your answer.

Using the fictional tomorrow-demo material, suggest a preparation slot before the 10 a.m. meeting. Check it against every other commitment. Keep your answer to three lines.

Check: A full 20 minutes, with no overlap. Check it against the practice notes.

05Choose what carries forward.

Instructions are preferences you choose. Memory is context Claude can carry forward. In your app’s Settings, review personal preferences and Memory separately.

Check: You know where to review saved context; you have not assumed every chat is remembered.

06–09Your project. Your voice.
06Give this job a home.

Projects keep a job’s conversations, instructions and material together. Click Projects in the sidebar.

Check: The Projects page opens.

07Create “My week.”

Choose New project. Name it My week and keep it private. Add the practice notes to its files or knowledge area.

Check: Your project contains the fictional notes, and you can open them.

08Set the rules for this job.

In the new project, find project instructions. Add this rule sheet. Start your next conversation inside My week.

This project is for preparing for my week. Use the notes and files I provide. Name the source of times, requests and decisions.
Keep the final brief under 150 words. Do not invent people, deadlines or decisions. Draft replies for me to check. Do not send them or change my calendar.

Check: The answer names its sources and drafts replies for you to check.

09Now make it sound like you.

Give Claude three writing samples in the project conversation. Ask it for a short rule sheet, then remove anything it guessed. Save the useful rules with the project instructions.

Here are three things I wrote:
1. Thanks for getting this together. Thursday works for me. I'll bring the notes.
2. We need the final version by noon. Please flag anything that's still missing.
3. Got it. I'll check and get back to you this afternoon.

Write a short rule sheet called "How I write." Use only patterns you can see in these samples. Then draft a reply to Sam's agenda request in tomorrow-demo using those rules. Keep the reply under 40 words. Do not send it.

Check: The draft sounds closer to your samples. Correct one phrase yourself.

10–15Connect an app
10Now, bring in an app.

A connection lets Claude use a source you choose. Open Customize near the bottom of the left navigation.

Check: Customize opens. These clicks are illustrated; follow them in your own app.

11Choose Connectors.

Choose Connectors at the top. This is the app directory. Skills and plugins do different jobs; adding one does not prove an account is connected.

Check: You can see or search for the app you want.

12Find Google Calendar.

Find Google Calendar and open its connection controls. A plus starts setup; a check means an existing connection is shown.

Check: You have opened the Calendar connection details.

13Read what it can access.

On the connection’s detail page, review its capabilities. Then use the Connect or Install control shown in your app. Wording can vary.

Check: You know which account and permissions the next screen is asking for.

14Finish sign-in in your app.

Check the account and requested permissions before approving. Return to Claude after the provider finishes. Already connected? Inspect the existing connection instead.

Check: Claude shows the connection as connected. If access is blocked, use the practice notes.

15Test one event you know.

For this quick connection test, choose New. Replace the brackets with a real event and date. Compare the answer with Google Calendar, then return to your My week practice conversation.

Use Google Calendar to find my event named [event name] on [date]. Give me the start time, time zone and calendar name. Include a source link if available. Tell me if you cannot access it. Do not create, change or delete anything.

Check: Event, calendar, time and time zone match. A missing source link alone does not mean the connection failed.

16–20Use it. Check it.
16The time comes in.

Return to My week and the fictional Alex notes. Keep the real-event test separate. In this example, Calendar contributes a 10 a.m. meeting: a time to plan around.

Check: Example only. Your account is not connected to this page.

17Then the request.

If you choose to add Gmail, repeat the connector setup. Ask for a named message. In our example, Sam needs an agenda before the meeting.

Check: The brief adds what you owe, alongside when it is due.

18Then the details.

A Notion page can add the project notes. Connect it only if you need it, and name the page Claude should use. Here, two decisions join the brief.

For connected accounts:

Use only the connected sources I name and have permission to use. Start with my calendar for tomorrow. List the meetings that need preparation, their times, and a link to each source. Do not create, change or delete anything.

If Gmail is connected, find the agenda request for that meeting and add what I owe. If Notion is connected, use the project page I name to add the decisions to prepare. Ask me for that page if I have not named it.

Keep it under 150 words. Tell me if a source is unavailable. Do not invent missing information, send messages or edit files.

Using the practice notes instead:

Using only the fictional notes in this conversation, give me the meeting time, what Sam asked for, and the two decisions to prepare. Name the source section for each fact. Keep it under 150 words. Do not use connected accounts, invent decisions or send anything.

Check: More useful context, not a guarantee of a correct answer. You still check the result.

19Let it ask before it guesses.

One missing detail can change the plan. Ask for up to five questions, answer the useful ones, and have Claude update the affected part.

Before you plan tomorrow, ask me up to five questions that would change the plan. Use the material already supplied so you don't ask what you already know. Then wait for my answers.

Check: You learn that Alex needs 10 minutes to walk there. The plan leaves 9:50–10:00 free.

20Check the source, not the tone.

Compare the time with the calendar, the request with the message, and the decisions with the notes. If a link is unavailable, compare the source details yourself.

Check that brief against the source material. Which facts did you actually verify? Which parts are assumptions or still uncertain? Name the source for the meeting time, the agenda request and the two decisions. Correct any mismatch. Keep it short.

Check: Every important fact traces to a source. An unknown decision owner stays unknown.

21–25Your next useful job
21Keep a chat out of memory.

For a separate incognito chat, leave the Project and start a new chat. Look for the ghost control in the upper-right corner. Turn it on and check for the Incognito label before typing.

Check: Incognito is visibly on. Read its notice, then return to your My week conversation to finish this practice job.

22Bring it together.

In the same project conversation, ask for your brief. Practice notes work too. You want one short result: preparation time, decisions, a draft reply and the first action.

Help me prepare for tomorrow using the material I supplied.
Return:
1. My meeting time and a 20-minute preparation slot that does not overlap another commitment.
2. The two decisions I need to prepare for.
3. A short draft reply to the agenda request, using my writing rules if available.
4. The first thing I should do.

Keep it under 150 words and name the source of each fact. Ask if a missing detail changes the answer. Do not send anything or change my calendar.

Check: A brief under 150 words, grounded in the material you supplied.

23Tomorrow looks different.

Apply the walking detail to your full brief. Alex needs ten minutes before the meeting; preparation still fits at 9:10–9:30. Check the time and make the draft sound right before using it.

I also need 10 minutes to walk to the 10 a.m. meeting. Recheck the preparation slot against the 9:30–9:45 check-in. Change only what that affects.

Check: The plan respects the check-in and the walk. The reply is still a draft, ready for your review.

24Make the proven job repeat.

After the job works by hand, explore Scheduled. Review the time zone, sources and output before saving. Check your account’s plan requirements first.

Help me set up a weekday preparation brief at 5 p.m. in my local time zone. Use only the calendar, email and project sources I explicitly choose. Reuse the format we just tested: tomorrow's commitments, preparation needed, a draft reply and my first action. Do not send messages or change any source.

Before saving a schedule, show me the time zone, sources, output location and whether it runs remotely or needs this computer. Wait for me to confirm.

Check: You know when and where the task runs, and where to pause it. Never assume local work runs with the computer off.

25The pieces now work together.

The meeting, the request and the notes become a brief you can use. That’s the point of the setup: less gathering, more time for the work.

Check: Your next move: prepare the agenda. Check and send the draft yourself when it is ready.

YOU DID ONE. KEEP BUILDING.

The next
30 days.

Build with Claude, ChatGPT and the other tools, with a clear path and people building alongside you.

$197one-time · tool plans cost extra
Join the 30-Day Challenge ↗

See the current dates, tool costs and full terms on the Challenge page.