From logseq-brain
Save session context, decisions, progress, and plans to the Claude Brain Logseq graph. Triggers: "save to brain", "save this", "remember this", "store this decision", "log this", "save progress", "before I quit", "wrap up". Don't fire for read operations (use brain-load) or status checks (use brain-status).
npx claudepluginhub jame581/skillsmith --plugin logseq-brainThis skill uses the workspace's default tool permissions.
Persist session context — decisions, progress, plans, implementation details — to the Claude Brain Logseq graph for cross-session and cross-device continuity.
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.
Persist session context — decisions, progress, plans, implementation details — to the Claude Brain Logseq graph for cross-session and cross-device continuity.
Resolve the graph path per skills/_shared/path-resolution.md.
Six categories — see references/categories.md for each one's format and rules. The orchestrator decides which apply based on what the session covered:
references/decisions.md for conflict + cross-project rules)pages/Meta.md)Identify target project(s). Look for project names mentioned, files/repos discussed, or explicit user statements ("we're working on X"). If multiple projects, save to each. If unclear, ask: "This touched [X] and [Y] — save to both?"
Verify project page exists. Glob for pages/Projects___<ProjectName>.md. If missing:
brain-init "Adding a New Project" flow, then continue.Read the current project page selectively using the section-targeted-read pattern in skills/_shared/section-locator.md. Read only the sections you'll touch (Session Log, Decisions, Current Plan, Implementation) — never the whole file. The read serves two purposes: detect duplicates before appending, and provide enough surrounding lines for the Edit old_string to be unique.
Prepare the updates for each applicable category from references/categories.md.
Write the updates using the Edit tool — surgical updates per section, never rewrite the whole page:
references/decisions.md)last-updated:: to today's dateUpdate the journal — ## Sessions. Append a rich cross-reference to today's journals/yyyy_MM_dd.md:
- ## Sessions
- [[Projects/ProjectName]]: Brief summary of session
Update pages/Meta.md if new user preferences emerged (see references/categories.md category 6).
Update pages/Index.md if a project status changed or new cross-project info emerged.
Write a journey-log entry per skills/_shared/journey-log.md with activity line: saved [[Projects/<ProjectName>]].
Confirm to the user in plain language what was saved. List each thing written.
See references/auto-suggest.md. Suggestion only — never auto-save.
CLAUDE.md for Logseq invariants.## heading.journals/ doesn't exist, create it (Bash mkdir -p) before writing the journal entry.