Internal/ Session Startup
Claude · Instructions
CLAUDE.md · active
← All docs
Session Protocol

Session Startup

What Claude does at the start and end of every session in this project. Also: no Oxford commas. Ever.

Always

Keep MD and HTML in sync

Every .md file in this project has an HTML equivalent in internal/. Whenever you update an MD file, update its HTML counterpart too — and vice versa. The two must always stay in sync.

📄

Key internal doc locations

These shorthands always mean the same files — never guess:

"ERD"internal/erd.html — the JavaScript-rendered SVG entity relationship diagram.

"Schema"internal/schema-reference.html — detailed entity reference with field-level descriptions.

"Your file" or "session startup"CLAUDE.md — these instructions.

ERD

ERD and schema conventions

Always surface junction tables as explicit entity boxes in both the ERD and the schema — never as implied M:N arrows. Use plural display names (e.g. MarketAnchors, AlertUsers). Assign junction entities to the jct group in the ERD. When a junction table carries extra payload fields beyond its two FKs, note it explicitly.

🔗

Accessing links — always use Chrome extension

When Janice shares a URL and asks you to look at it, always access it via the Claude Chrome extension. Never use web_fetch or other tools for links Janice shares. Steps: list_connected_browsersselect_browsertabs_context_mcpnavigateget_page_text.

zsh

Git staging — paths with square brackets

When running git add on paths inside [market]/ or any directory with square brackets, always wrap the path in single quotes. Bare brackets are interpreted as glob syntax by zsh and fail with "no matches found".

git add 'app/dashboard/[market]/some-file.tsx'

Session Start
1

Read the project brief

Located at internal/territori-project-brief.html. Familiarise with the product vision, goals and current priorities before doing anything else.

2

Check Airtable tasks

Connect to the Project Management Airtable base (appZ36ZxHvKBm8unT) and review the Tasks table in full — both completed and open — to understand what has been accomplished and what remains.

Also check the User Stories table for context on priorities and epics.

3

Read all internal docs

Read every HTML file in internal/ at session start. The docs are tightly interconnected and reading them all upfront saves more time than selective reading. Use ls internal/ to get the list, then read each file. Skip only files that are clearly data exports or assets (images, CSS, etc.).

4

Read journal entries

Read markdown/journal.md. Get up to speed on what was done in previous sessions and exactly where things were left off.

After all four steps: Give Janice a warm, encouraging, motivating summary of where things stand — one that keeps her excited about what she's building.
Session End

A session ends when Janice says goodnight, that she's going to bed, or stops responding for 30 minutes.

1

Update Airtable

Update the Tasks table in the Project Management base (appZ36ZxHvKBm8unT) to reflect progress made during the session.

2

Update the project status page

Update internal/project-status.html to reflect current epic statuses, task counts, pipeline state and any new timeline entries.

3

Write a journal entry

Summarise what was accomplished, decisions made and exactly where to pick back up next session. Append to markdown/journal.md with a ## YYYY-MM-DD heading.