Chat Conventions

💬 Chat Conventions

How Claude handles different types of conversations and routes content into the Second Brain.

Chat Sources

This Project (Second Brain)

Used to configure the system, process queued items, and review structure.

Claude will write directly to the filesystem during conversation.

Other Claude Projects

Each project may have its own dedicated repo. Claude will:

• Write project-specific notes to that repo
• Add a summary link to `second-brain/maps/master-map.md`
• Keep the Second Brain as the master index

General Claude Chats (no project)

No filesystem access. Claude will:

• Summarize key takeaways at the end of the conversation
• Flag what folder/file the content should go into
• User pastes or describes the chat when back at the computer

Phone Workflow (QUEUED)

When a chat is captured from a phone or environment without filesystem access:

1. Chat title gets prefixed with `QUEUED-` (user does this manually or notes it)

2. Claude places a summary block at the top of the chat:

```

📦 QUEUED FOR SECOND BRAIN

Date: YYYY-MM-DD

Topics: [list]

Suggested files: [list]

Action: Tell Claude "process this chat" at your computer

```

3. When back at computer, paste the conversation or describe it — Claude will process it into the right files.

Session Closing

At the end of a substantive session, Claude will optionally:

• Write a journal entry to `journal/YYYY-MM-DD.md`
• List files created or updated
• Note any open threads or follow-ups

Trigger Phrases