Read project context from the Claude Brain Logseq graph and present it to Claude so work can continue seamlessly across sessions and devices.
Prerequisites
Resolve the graph path per skills/_shared/path-resolution.md.
Loading a Specific Project
When the user says "load " or similar:
-
Find the project page using the algorithm in
references/matching.md. -
Read the matched project page using the section-targeted-read pattern in
skills/_shared/section-locator.md. In brief mode, read only Properties + Overview + Current Plan + last 3 Session Log entries (target ≤80 total lines). In full mode, read all sections but still section-by-section, never as a single big Read. -
Read related context (full mode only). Follow
[[link]]references inside the project page if they're critical (e.g., a linked design doc). Skip in brief mode. -
Read today's journal (
journals/yyyy_MM_dd.md) if it exists — captures session notes from earlier today.
-
Check active Jira tasks. If the project's Current Plan section references task IDs (e.g.,
PROJ-1234), and the task folder is accessible, optionally readplan.md. Full mode or explicit user ask only — in brief mode, just mention task IDs and status. -
Apply staleness rules. Use
skills/_shared/staleness.mdagainst the project'slast-updated::andstatus::. -
Surface session continuity hints. From the most recent Session Log entry: what was last worked on, any
open-questions::, any blockers. Frame as: "Picking up where you left off — last session ([date]): [summary]. Open questions: [list]." -
Present a context summary conversationally: project name + status + staleness, current plan/task, continuity hint, key recent decisions (full mode only), suggested next actions.
-
Write a journey-log entry per
skills/_shared/journey-log.mdwith activity line:loaded [[Projects/<MatchedName>]] (brief)orloaded [[Projects/<MatchedName>]] (full).
Loading General Context
When the user says "load brain" without a project:
- Read
pages/Index.mdfor the list of all projects. - Read
pages/Meta.mdfor user preferences and conventions. - Present a high-level overview: active projects, cross-project decisions, user preferences.
- Write a journey-log entry:
loaded brain overview.
Searching Across the Brain
When the user asks "what do we know about X" or similar, follow the algorithm in references/search.md. After presenting findings, write a journey-log entry: searched "X" · N hits.
Load Modes: Brief vs Full
Brief mode (default — "load "):
- Properties (type, status, last-updated)
- Overview (first 5 bullets only)
- Current Plan (full)
- Session Log (last 3 entries only)
- Skip Implementation, Decisions, linked context
Full mode ("load full", "load everything about "):
- All properties
- Full Overview
- Full Current Plan
- Full Implementation
- All Decisions
- Last 10 Session Log entries
- Related context pages (follow
[[links]]) - Today's journal entry
In brief mode, mention that more is available: "Loaded brief context. Say 'load full' for decisions, implementation details, and full history."
Important Notes
- Be selective about reads. Token budget matters — use the section-targeted-read pattern in step 2 of "Loading a Specific Project" rather than reading whole pages.
- After loading, confirm what's available and suggest next actions.
- All graph content is Logseq outliner format. See
CLAUDE.mdfor invariants.