Sessions to run — ready-to-paste prompts (2026-07-02)

Each block = a self-contained prompt. Open a fresh Claude Code session (PC or VM), paste ONE, say go. Focused, timed, done.

1. HOME PORTAL REBUILD → run on the VM (all git+cloud)

Full prompt: docs/HANDOFF_HOME_PORTAL_REBUILD.md (home-portal section). Read the deep-dive + twin mockup first.

2. HSS WEBSITE REBUILD → run on the PC (may want brand assets)

Full prompt: docs/HANDOFF_HOME_PORTAL_REBUILD.md (HSS section) + HookStreetServices-Site/SERVICES_CONCEPT.md. The 6 invisible offers + the villa/advisory split.

3. 2025 TAXES → continue where Sam left off

PASTE:
"""
You're picking up Sam's 2025 tax work. Read .claude/projects/C--Users-ztrei-OneDrive-2--Hook-Street-05--2026-BH/memory/reference_cpa_and_2025_tax_status.md + grep docs/ + Gmail (both inboxes) for 'Zell', 'Ettinger', 'tax', 'CPA', '$9,750', 'Passover Ventures'. Reconstruct: what's the exact current state of 2025 taxes across all entities (Hook Street Capital, Treitel/Passover Ventures, personal), what's the $9,750 blocker, what documents are needed, what's overdue. Then produce ONE tax-status briefing (outputs/, forced-light) with: where each entity stands, the blocker, the exact next 3 actions + who (Sam / CPA Zell & Ettinger), and any deadline risk. Do NOT file anything; this is get-Sam-un-stuck. Card the actions. Ping Sam the top decision.
"""

4. KIDS' SCHOOL REGISTRATION → the thing that "should already be done"

PASTE:
"""
You're handling Sam's kids' school registration (he flagged it overdue, 'my kids can't start already'). Search Gmail (both inboxes) + the command queue for the school(s), registration forms, financial-aid deadlines (Darchei — Amy Kurtz x222 is a known contact; card #116). Reconstruct: which kids, which schools, what's outstanding (registration forms? tuition? aid application?), deadlines. Produce a one-page action list (outputs/, forced-light): per child/school — exact next step + link/contact + deadline. Draft any needed emails (Gmail drafts, don't send). Card + ping Sam the single most time-sensitive one.
"""

Scheduling note

These can be run anytime; #3 and #4 are the "real life" ones Sam wants gotten-done. Consider a Cloud Routine or a set time so they're not perpetually deferred.

5. ONEDRIVE → GOOGLE DRIVE MIGRATION (the "one safe place" build — prepared, not urgent)

GOAL: everything currently PC-only (the "05. 2026 BH" OneDrive folder — archives, statements, Passover 35GB, plus the memory files) gets a canonical, browsable, PC-independent home so nothing lives only on one machine.
PASTE:
"""
You're running Sam's OneDrive→Google Drive migration. READ docs/HOW_IT_ALL_LIVES.md + docs/CONNECTIONS.md first. The goal: a single safe, browsable home for everything that's currently PC-only, so no file lives only on one machine.
PLAN (propose to Sam before moving anything — this is his data):
1. INVENTORY the OneDrive "05. 2026 BH" tree: what's already in git (safe), what's PC-only (the risk) — big archives (Passover ~35GB), statements, screenshots, the raw memory .md files.
2. Decide the canonical home per class: (a) git/GitHub stays the source for docs+outputs+code; (b) the heavy archives + statements → a Google Drive folder tree (browsable on phone, the OneDrive-outputs feeling Sam wants back); (c) the MEMORY files → decide ONE canonical location both PC + VM sync from (Drive or a private git submodule) so they stop drifting (this closes the 3h-drift caveat).
3. Set up the sync: rclone (OneDrive→Drive) OR the Google Drive MCP for the structured stuff; a scheduled job (VM cron) that keeps it current. Verify a sample file round-trips + is browsable on Sam's phone.
4. Organize + index it so Sam can tap through Drive like he used to tap through OneDrive/outputs.
Do NOT bulk-move without Sam's confirmation on the folder structure. Card the steps. This is the "everything's safe in one place, PC-off" endgame.
"""