# The setup prompt

Claude Code looks through your files, interviews you about your work, proposes a folder structure for your approval, moves everything with an undo log, then writes the CLAUDE.md that briefs every future session.

## Before you paste

- Start a new session, choose Local and select your home folder (the one with your name), not the whole disk, so it can reach Desktop, Documents and Downloads.
- A Mac will ask whether Claude can access those folders, and you need to say yes or it can't see the files.
- Use Manual mode, so you approve every write and every move, and Esc stops it at any point.
- Set aside 30 to 60 minutes because long quiet stretches are normal, and either change the folder name in square brackets at the top of the prompt or leave it and it'll ask.

## The prompt

Copy everything inside the fence and paste it into Claude Code as one message.

````text
I want you to set up this computer so you can do real work with me from now
on. That means two things: gather my work files into one clean folder, and
then write the files that brief you about my work, so every future session
in that folder starts with the context instead of from zero.

Read this whole prompt before doing anything. You design the structure, you
ask me what you need to know, and you build it. I answer questions and
approve things.

The new folder: [~/Documents/Work]. If that's still in square brackets, ask
me what to call it and where it should live before you start.

=== HOW TO WORK WITH ME ===

- Short messages. One thing at a time. No long lists of filenames.
- Show me simple trees and counts, not paragraphs.
- If you're unsure, ask. Don't guess silently.
- Facts about my work have to come from me. If something isn't clear from
  what I've said, ask a follow-up instead of filling it in.

=== WHAT DONE LOOKS LIKE ===

1. One folder holding my work files, organised so simply that I never have
   to think about where something goes. I'll open every future session here.
2. Desktop, Documents and Downloads are no longer full of scattered work
   files. This is a reorganisation: files move, they aren't copied.
3. A CLAUDE.md and a context/ folder good enough that when I open this
   folder next week and ask you about my work, you already know the
   background.
4. A short report telling me what changed and how to use it.

You decide the structure. Don't copy a template: design it around what you
find and what I tell you. It should follow these principles:

- Shallow. One level of folders wherever possible.
- Plain names, in my words. Fewer than eight things at the top level.
- An inbox/ folder for anything I can't be bothered to file. You sort it
  later, with me, so I never have to make a filing decision in the moment.
- One tasks.md as the only task list. New items get the date. Nothing is
  deleted from it; done items are marked done.
- A context/ folder for the detail, so CLAUDE.md itself stays short.
- A review-for-deletion/ folder. You never delete anything. Anything that
  looks outdated, duplicated or dead goes there, and I empty it myself.

=== BOUNDARIES ===

These hold for the whole session, including for any subagents you start.

- Only touch my own files: Desktop, Documents, Downloads, and any obvious
  work folders at the top of my home folder.
- Never read, list or go near ~/Library, hidden folders such as ~/.ssh,
  keychains, password managers, or anything holding credentials. If you
  come across a file that looks like it holds passwords, bank details or ID
  documents, don't open it. Note that it exists and ask me where it goes.
- Never delete. review-for-deletion/ instead, every time.
- Log every move. Before you move anything, create moves-log.md in the new
  folder and add one line per move: original path -> new path. That log is
  the undo button for the whole session, so keep it complete.
- Don't install anything, add connectors or plugins, or set up hooks or
  scheduled tasks in this session. If you think one would help, put it in
  the report as a suggestion.
- There are two stop points below. At each one, stop and wait for a clear
  yes. I'd rather wait than undo.

=== PHASE 1: LOOK (read only) ===

First, tell me in one line which tools and connections you can use in this
session (for example email, calendar or a cloud drive). It changes what's
possible later.

Then look through the areas above. If there's a lot, use subagents in
parallel, each one given the boundaries above. File names often don't say
what a file is, so open documents where you need to. Change nothing.

Tell me briefly what you found: roughly how many files, what kinds, and
what looks like work, personal, or junk.

=== PHASE 2: ASK ME ===

Interview me about my work. One question at a time, one sentence each, and
wait for my answer before the next. Ask as many as you need. At least find
out: what I do and for whom, what a normal week looks like, who I work
with, what I keep redoing from scratch, what eats my time, and anything
from the look-through that confused you.

Push for specifics. "The usual clients" isn't an answer: ask which ones. My
answers are the raw material for everything you write later, so getting
them right matters more than finishing fast.

Before you move on, show me the folder names you have in mind and ask
whether they're the words I'd actually use. Challenge any vague catch-alls
like "misc" or "resources". A name I won't recognise in a month is a name I
won't use.

=== PHASE 3: DESIGN, then STOP ===

Propose, keeping each part short:
1. The folder structure, as a tree, one line per folder.
2. Where my existing files will go, as counts per destination ("about 40
   proposals -> clients/", "120 old installers -> review-for-deletion/"),
   not filenames.
3. What CLAUDE.md and context/ will hold, in a few plain sentences.

STOP. Ask me what I'd change. Wait for a clear yes before you build.

=== PHASE 4: MOVE ===

Create the structure, then move files into it one area at a time (Desktop,
then Downloads, then Documents), logging every move in moves-log.md as you
go.
- Genuinely unsure where something belongs -> inbox/, not a guess.
- Looks outdated, duplicated or dead -> review-for-deletion/.
After each area, tell me in one line what moved. When all areas are done,
show me the final tree with counts and confirm the log is complete.

STOP. Let me look at the tree. Fix anything in the wrong place now, before
you write the documentation. Wait for my okay.

=== PHASE 5: WRITE THE BRIEFING ===

Show me each file before you write it.

CLAUDE.md, at the top of the new folder. You read this at the start of
every session, so write it for yourself, and keep it under about 150 lines:
depth goes in context/. Put the date it was last updated at the top. Cover
briefly: what this folder is; who I am and what my work is; a one-line map
of every folder; how to work with me (the section above, compressed); the
standing rules (inbox/ is unsorted, so offer to file it; tasks.md is the
only task list; never delete, use review-for-deletion/; log every move in
moves-log.md); and how to keep yourself current:
- when I tell you something new about my work, offer to add it to the
  right context/ file
- when the structure changes, update the map and the date
- if the date is more than a month old, say so and ask what's changed

context/, the detail. You decide how to split it, but include at least:
- how-i-work.md: everything from the interview. This is the most valuable
  file in the folder, so make it thorough.
- voice.md: a stub for now. It will hold real examples of how I write, for
  drafting later.
Date every file.

tasks.md: a heading, ready to append to.

tidy.md: a short routine for when I say "tidy". Suggest homes for anything
in inbox/ and file it on my say-so; flag anything in the wrong place; mark
done tasks and show me the oldest open ones; flag anything in CLAUDE.md or
context/ that no longer matches reality; update the dates. It never deletes
and never moves anything without asking.

start-here.md, for me, not you. Half a page, plain English: what this
folder is, where things go, four or five things I can say to you to get
value out of it (including "tidy"), and one line saying moves-log.md can
put anything back where it was. Assume I've forgotten this whole session.

=== PHASE 6: CHECK YOUR OWN WORK ===

Re-scan the areas you reorganised and confirm the numbers add up: every
file is in the new folder, in inbox/, in review-for-deletion/, or
deliberately left where it was and listed. Every move is in moves-log.md.
If anything doesn't reconcile, say so plainly and fix it. Then tell me in
two lines how many files moved and how many are waiting in inbox/ and
review-for-deletion/.

=== PHASE 7: REPORT ===

Write setup-report.md in the new folder: the final tree with counts, what
you were unsure about, what you left in place and why, and the two to four
jobs in my week you think are most worth handing to you next, with your
reasoning. Be willing to disagree with what I said I wanted.

Then tell me in two or three sentences how to use this from tomorrow: where
to open you, and what to say first.

This will take a while, and phases 1 and 4 have long quiet stretches.
That's it working. Don't rush past the stop points.
````
