dimeloper/second-brain-workflow

update-second-brain

Capture the current agent session's work into the Obsidian "second brain" vault and publish it: append to today's daily note, revise the project docs the session moved, propose and promote engineering practice notes, then commit and push. Runs from inside the…

원문 언어: 영어

extract-product-context

Draft a project's context/ — audience, voice, brand — from a product repo's own files rather than from memory, daily notes or store copy. Read-only. Use when writing or revising context/ for a project doc, when asked who a product is for, what it sounds like,…

원문 언어: 영어

check-follow-ups

Scan recent daily notes' Follow-ups sections and report what's still open, oldest first, leading with the ones for the repo you're in — plus anything ticked as dropped or handed off, which is closed without being finished. Read-only — walks back to the last…

원문 언어: 영어

obsidian-knowledge-base

Read the Obsidian vault and score current work against it — load this repo's project context, find the practice notes that apply to this stack, cite what was followed, and name drift and gaps. Read-only. Use before large or unfamiliar changes, when the user…

원문 언어: 영어

onboard-repo

Onboard a Cursor repo into the hot-path/cold-path standards system: sync second-brain-workflow rules, add a thin always-apply onboarding rule, point at relevant second-brain practices, and wire project-scoped MCP (Railway / Postgres / Logfire / PostHog) —…

원문 언어: 영어

mcp-per-project

Set up or fix per-project MCP isolation in Cursor and Claude Code, so concurrent agent sessions for different products (e.g. Acme vs Globex vs Initech) each get their own Railway, Postgres, Logfire, PostHog, etc. Use when the user mentions MCP bleed across…

원문 언어: 영어