From ai-brain
Reconstruct the chronological evolution of thinking around a topic or anchor thought. Walks the timeline around a seed, hydrates the most substantive neighbors, and produces a citable narrative.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ai-brain:brain-threadThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Trace how your thinking on a topic evolved over time. Given a seed — either a topic (free text) or a thought ID — walk the chronological neighbors via `timeline_thoughts`, hydrate the most substantive ones, and produce a cited narrative.
Trace how your thinking on a topic evolved over time. Given a seed — either a topic (free text) or a thought ID — walk the chronological neighbors via timeline_thoughts, hydrate the most substantive ones, and produce a cited narrative.
mcp__ai-brain__search_thoughts, mcp__ai-brain__timeline_thoughts, and mcp__ai-brain__get_thoughts must be available. If not, tell the user to install/update the AI Brain plugin and stop.
$ARGUMENTS — Required:
/brain-thread "COPA remodel"/brain-thread thought:abc123xyz or /brain-thread abc123xyz--type <decision|person_note|idea|meeting_note|task|reference> — filter the timeline to one thought typeParse $ARGUMENTS to extract:
seedInput — the non-flag portion (quoted topic or ID)type — the --type value if presentDetect whether seedInput is an ID or a topic.
^thought:[a-zA-Z0-9_-]+$ or a bare identifier of at least 16 chars (Convex IDs are longer).If ID: strip the thought: prefix (if present) and use it directly as seedId. Skip to Step 2.
If topic:
mcp__ai-brain__search_thoughts with query: <topic>, limit: 10, and type: <type> if a type filter was provided./brain-init if your brain is empty." Stop.thought:<id>)."Multiple possible seeds for "[topic]":
1. [summary] (`thought:<id>`) — [snippet preview]
2. [summary] (`thought:<id>`) — [snippet preview]
...
Which one should I thread from? (number, or paste another ID)
Wait for the user's pick. Use their selection as seedId.Call mcp__ai-brain__timeline_thoughts with:
seedId: the resolved seedbefore: 10after: 10type: <type> if provided, omit otherwiseThe result is an ordered array of up to 21 compact index rows, seed included. If only the seed is present (no neighbors), tell the user: "This thought has no chronological neighbors yet — there's nothing to thread. Try a broader topic or come back after more captures." Stop.
From the timeline, select the 3-5 most substantive neighbors (plus the seed) to hydrate. Signals of substance:
decision or meeting_note over reference when both are presentCall mcp__ai-brain__get_thoughts with ids: [<selected IDs including seed>].
Write a markdown narrative with this optional structure:
## Thread: [short topic inferred from seed]
**Before the turn**
<1-2 paragraphs covering thoughts chronologically before the seed or pivotal point. Cite each claim as `thought:<id>`.>
**The turn**
<1 paragraph covering the seed thought itself — the pivotal moment the thread centers on. Cite as `thought:<seedId>`.>
**After**
<1-2 paragraphs covering how thinking evolved after. Cite each claim as `thought:<id>`.>
---
**All thoughts in this thread** (for reference):
- `thought:<id>` — <summary> (<date>)
- `thought:<id>` — <summary> (<date>)
- ...
If the thread is very short (3-4 thoughts), simplify to a single narrative paragraph followed by the reference list.
Never write a claim without a citation. If a statement doesn't map to a hydrated thought, remove it.
After the narrative, suggest:
/brain-thread thought:<seedId> --type decision or increase the range by running again."/brain-context <date> anchored on that thought's createdAt."npx claudepluginhub flippyhead/ai-brain-plugin --plugin ai-brainProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.