Insights
Arguments we are willing to be wrong about in public, each dated so you can tell how old the claim is.
The instruction you write once instead of every session
What a skill is, why the description is the only part always loaded, what belongs in one versus AGENTS.md, and how to work out why yours is not firing.
GitHub for people who do not write the code
Git, GitHub, commits, branches and the four levels of undo — the version control a vibe coder actually needs, and the hacks that recover a lost day.
Six decisions before your first prompt, and why each one is there
GitHub, a model, a host, a stack, a guardrail and a first prompt — the setup a vibe coder makes once, and what each piece is actually protecting.
Vibe coding, and the first week that does not end in a mess
What vibe coding is, where it genuinely works, where it stops working, and the answers to what people actually ask before their first serious attempt.
What breaks when vibe coding meets a repository other people work on
The failure is rarely bad code. It is code that is locally reasonable and globally wrong, because the convention it broke was never written down.
What to move out of Obsidian, and what to leave in it
A line you can apply per note — if being wrong about it would mislead somebody else, it has outgrown a personal vault. What moves, and where to.
Your Obsidian vault cannot be your AI agents' knowledge base
Obsidian is a thinking tool for one person. Agents need project knowledge that is shared, cited, and provably current — three things a vault cannot be.