PROJECT SETUP — HOW TO USE THESE FILES

Three files ready to upload to a new Claude Project on claude.ai:

1. CONTEXT.md — Who you are, active fires, tech stack, what Claude should do
2. OBLIGATIONS.md — Current obligations, installments, mortgages, cards
3. CONSULTING_PACKAGE.md — Service framework for Hook Street engagements

STEP-BY-STEP SETUP (5 minutes)

1. Create the Project

• Go to claude.ai on your laptop or phone
• Left sidebar → "Projects" → "+ New project"
• Name: Hook Street OS
• Description: Personal operating context for Sam Treitel

2. Upload the files

• Click "Add to knowledge base"
• Upload all 3 files at once (or one at a time)
• Confirm they show in the project knowledge panel

3. Set custom instructions

Paste this into the "Project instructions" field:

You are Sam Treitel's Chief of Staff. Read CONTEXT.md, OBLIGATIONS.md, and CONSULTING_PACKAGE.md before every response.

Sam is voice-dictated, on the go, phone-first. Respond direct. No validation. No "great question." No recap of steps taken. Output first, questions last.

When Sam asks about current state (emails, calendar, market, sheets) — pull live data with tools. When he asks about context (obligations, projects, consulting) — the files are the truth.

End responses with one actionable question when appropriate: "What do you want to move on first?" Not every response needs a question.

If Sam asks you to save something, create a Gmail draft without asking permission.

Format for phone reading: short paragraphs, scannable, minimal markdown unless specifically useful.

4. Test it

Open a new conversation in the project. Say: "What's due this week?"

If it pulls from OBLIGATIONS.md and gives you a clean list — it's working.

HOW TO KEEP IT CURRENT

Weekly refresh (every Sunday night, 5 min)

1. Open Cursor → export latest CONTEXT.md from hookstreet-workspace repo
2. Update OBLIGATIONS.md with any new paid items / new bills
3. Re-upload to the Project (replaces old version automatically)

When to update right now

• Obligation paid or added
• New client or project
• Major state change (Orlando trip, Eden Gardens milestone)
• Fire gets put out (delete it from Active Fires section)

When NOT to update

• Minor changes
• Daily fluctuations
• One-off events already captured in Gmail drafts

Rule: if it's a weekly+ pattern, it belongs in the Project. If it's today-only, it belongs in a chat.

WHAT THIS GIVES YOU

Before: Every mobile chat started cold. You had to explain context. I made mistakes.

After: Every mobile chat starts with full context. You ask your question. I already know the players, the fires, the structure.

What it doesn't give you:
- Live Gmail/Calendar/Sheets access — that's still tool calls per session
- GitHub sync — you still manually export
- Replacement for Cursor — code work stays there

DON'T

• Don't upload everything you have. Less is more. 3-5 files max.
• Don't upload PDFs unless absolutely needed. Markdown parses cleaner.
• Don't let it go stale. Weekly refresh or it's worse than nothing.
• Don't treat it as the truth if it's older than 2 weeks. Always defer to GitHub CONTEXT.md.

NEXT FILES TO CONSIDER ADDING (later)

• MILDRED_SOP.md — her exact responsibilities, hours, handoff protocol
• MIS_RULES.md — VIX thresholds, regime logic, earnings penalty
• EDEN_GARDENS.md — client-specific context, the 21 action items
• STR_PROPERTIES.md — Orlando homes, vendors, booking status
• MALCA_YENTA.md — LevSMS project, entity filings pending

Don't add these yet. Start with the 3 core. If you find yourself explaining something repeatedly in chats, THAT's when you add the file.