Three Ways to Build a Second Brain — Pick by Who Can Read It
A hosted project, a local Markdown vault, or a folder in git. The features barely differ; what differs is whether a brand-new agent session can answer from your notes with zero uploads. Here are the three layouts, the honest catch in each, and the structure I'd copy.
- #second-brain
- #knowledge
- #claude-code
- #obsidian
Sign in to keep reading
Three Ways to Build a Second Brain — Pick by Who Can Read It — A hosted project, a local Markdown vault, or a folder in git. The features barely differ; what differs is whether a brand-new agent session can answer from your notes with zero uploads. Here are the three layouts, the honest catch in each, and the structure I'd copy.
Your first guide is free. Sign in with Google or LinkedIn to read the whole library and get new guides as they ship — no cost.
Keep reading
More guides like this one.
A Claude Code Plugin Adds No New Powers. It Adds Everyone Else.
Everything a plugin does, a loose .claude/ folder already does. What packaging buys you is distribution — and it costs you your command names. Here is the manifest, the install commands, and the rule for when that trade is worth making.
Four Places to Run Claude Code — and What Each One Silently Drops
A cloud session clones your repo into a fresh Anthropic VM — so your personal skills, agents and every MCP server you added with `claude mcp add` are simply not there. Surface choice isn't a UI preference, it's a capability choice. Here's the decision rule by task shape, plus the commit that makes your setup portable.
Your Weekly Setup Review Needs a Delete Column
Adding your 30th skill can quietly make the other 29 harder to find: the skill listing gets ~1% of the context window, and Claude Code drops descriptions from the skills you invoke least. Here is the Friday ritual, the routing table for each lesson, and the subtraction pass everyone skips.