What's in the starter filesEvery folder stands in for a real system you already use.
Every folder stands in for a real system you already use.
Today it's a file. Next week it's a connection. Same command.
CLAUDE.md: the house rules. Two rules today: speak plainly, and staff up for big jobs. By the end of the hour, this file is your employee.context/: what a new hire needs. The studio, the team, this year's goals, and jess-notes.md, a messy brain dump off your phone.reviews/: Google, Facebook, and ClassPass, raw. The renewal answer is buried in here.feedback/: submissions from your website's contact form.inbox/: your Gmail. Twenty-three emails, including one that hurts.calendar/: your Google Calendar plus the booking system's fill report.tasks/: wherever your to-dos live. Notion, Linear, your head.meetings/: your meeting notes. The huddle, the landlord call, and a messy mentor call.messages/: your team chat. Slack, Teams, a group text.photos/: the shared Drive folder where instructors dump class shots. Here, an index with links.market/: a friend's competitor scan and where your members actually live. Fuel for the long game.templates/: how you like things formatted, and ten messages you actually sent.drafts/: empty. Anything that needs your yes lands here.sent/: empty. Where things go after you send them..claude/commands/: empty today. By the end of the hour it holds the two skills you built.
Hire Cora.
Give plain Claude some work, watch it earn the hire, then hire her live.
Read & Summarize the Business
A dozen messy files. Nobody compiled them. Nobody needs to.
Read everything in context/, reviews/, feedback/, and meetings/. Save what you learn to company-summary.md, then give me the short version: who we are and our goals.
- Claude works in your files, not a chat window
- Big piles spawn parallel workers
- The summary becomes a file. Every later step can read it
Audit Where My Time Goes
The goals say grow. The calendar says you can't.
From @calendar/this-week.md and @inbox/inbox.md: what share of my week goes to teaching, keeping the lights on, and growing the business? Then write what-to-delegate.md, what only I can do and what someone else could own.
- Percentages land harder than task lists
- Big findings become files. The next step reads them
- What stays yours is your call, not hers
Hire Her
The delegate list is the job. Now have the hiring conversation.
Step 1: Say what you need
You're my new chief of staff. The job starts with @what-to-delegate.md. Interview me for it with the AskUserQuestion tool, and ask what to call you. Don't write anything until I say go.
Step 2: Click what fits, say the rest
Step 3: Watch the file
Go. Write your job description into CLAUDE.md, keeping the house rules.
If she picked her own filename, fix it
Move that into CLAUDE.md. Only that file is read automatically at the start of every session.
CLAUDE.mdis read every session, automatically- Claude can interview you, with clickable questions
- Spoken answers become standing rules in a file
Put Her to Work
Don't assign the work. Ask what the work is.
Step 1: Ask. Five words is enough now
Cora, what needs me today?
Step 2: You decide, she executes
Agreed. Rosa first. Show me the draft.
Step 3: The draft sounds corporate. Teach her your voice
Rewrite it using @templates/jess-messages.md as the style guide.
Step 4: Keep it forever
Add "How Jess writes" to CLAUDE.md so you never lose it.
Step 5: Save the morning ritual as a skill
I want that list every morning. Save it as a skill called /prep-me.
Have some fun with this...
Add a sign-off to it: end every brief with one hype line. Best-friend-before-a-big-day energy, funny, a little snarky, never the same line twice.
- Prompts shrink as
CLAUDE.mdgrows - Voice is trained by example: ten real messages beat a paragraph about tone
- One sentence saves repeatable work as a skill
Find the Opportunity
Skill saved, desk handled. Now back to the thing the summary flagged: renewals.
Pull up @company-summary.md and go deeper on the renewal problem: is this demand or supply, and can my current team cover it? Check @calendar/fill-report.md and @context/team.md. What would you do?
- Ask the analyst question, demand or supply, and she brings receipts
- Good analysis ends in a verb. Hers is: hire
- She proposes. You decide. Same as day one
Staff It and Show It
She said hire. You agreed. Now the paperwork and the marketing.
Step 1: The hire that staffs the new mornings
Write the job post for the new morning teacher with @templates/job-posting.md. Into drafts/.
Step 2: The posts that fill them. Open the file in your browser
Pick the three best shots in @photos/drive-export.md and mock up three Instagram posts as one HTML page in drafts/.
- A photo folder is just another readable file
- Ask for HTML, get a prototype you can open
- The voice rules now apply to everything she writes
Put Her on the Clock
She works when you're not there. That's the whole point of staff.
Step 1: Say what you want. She'll ask what goes in it
I want an end-of-day digest of what still needs me, and a morning digest to prep my day. Ask me what to include, then set both up as routines on this machine's scheduler.
Answer in your own words. Ours: what needs me, ranked, and what's waiting on my yes
Step 2: Prove it. Hands off the keyboard
Schedule one extra morning run for two minutes from now. Hands off, we watch the folder.
If the scheduler acts up, this is all a clock does anyway
claude -p "/prep-me"
- A routine is a request plus a clock. Nothing new to learn
- The scheduled run is a brand-new session. She wakes up already knowing who she is, that's
CLAUDE.md - The rules hold at 6am: drafts still wait for your yes

