From logseq-brain
Load project context from the Claude Brain Logseq graph into the current session. Triggers: "load brain", "load <project>", "resume <project>", "continue work on <project>", "what do we know about <topic>". Don't fire for write operations (use brain-save), generic questions about Logseq itself, or "open <file>" / "switch to <branch>" requests that mean opening files or switching git branches rather than loading project memory.
npx claudepluginhub jame581/skillsmith --plugin logseq-brainThis skill uses the workspace's default tool permissions.
Read project context from the Claude Brain Logseq graph and present it to Claude so work can continue seamlessly across sessions and devices.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Checks Next.js compilation errors using a running Turbopack dev server after code edits. Fixes actionable issues before reporting complete. Replaces `next build`.
Guides code writing, review, and refactoring with Karpathy-inspired rules to avoid overcomplication, ensure simplicity, surgical changes, and verifiable success criteria.
Share bugs, ideas, or general feedback.
Read project context from the Claude Brain Logseq graph and present it to Claude so work can continue seamlessly across sessions and devices.
Resolve the graph path per skills/_shared/path-resolution.md.
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 read plan.md. Full mode or explicit user ask only — in brief mode, just mention task IDs and status.
Apply staleness rules. Use skills/_shared/staleness.md against the project's last-updated:: and status::.
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.md with activity line: loaded [[Projects/<MatchedName>]] (brief) or loaded [[Projects/<MatchedName>]] (full).
When the user says "load brain" without a project:
pages/Index.md for the list of all projects.pages/Meta.md for user preferences and conventions.loaded brain overview.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.
Brief mode (default — "load "):
Full mode ("load full", "load everything about "):
[[links]])In brief mode, mention that more is available: "Loaded brief context. Say 'load full' for decisions, implementation details, and full history."
CLAUDE.md for invariants.