Stop fragmenting your notes across locations. A single Obsidian vault with everything—seeds, drafts, posts—creates connections you’d never see otherwise.

Inspired by Teresa Torres, I built a single command that pulls my calendar, email, and newsletters into a daily briefing document—then syncs it everywhere.

Stop documenting your work manually. Configure AI to silently capture insights, decisions, and mistakes while you focus on actual thinking.

Stop separating ’the work’ from ‘writing about the work.’ When you work with AI, the conversation itself is the content.

Why the gap between thought and article kills most ideas, and how dialogue with AI bridges it.

How I automated the generation of 29 blog cover images in minutes using Gemini and MCP.

Why the process of building can become the content itself, and a new paradigm for AI collaboration.

Stop cluttering your desktop or project folders. Learn how a simple ’try’ function can revolutionize your experimental workflow.

The Idea

The process of creating content can itself be content.

Expanded

When working with AI assistants, the conversation itself - the prompts, the iterations, the decisions made - forms a narrative that others can learn from. Instead of just publishing the “finished product,” document the entire creation process.

This applies to:

• Building systems with AI help (this very system was built this way)
• Debugging sessions that reveal thought patterns
• Design decisions made through dialogue
• The evolution of ideas through iteration

Why It Matters

1. Authenticity: Shows real work, not polished facades
2. Educational: Others learn from the process, not just the result
3. Efficiency: No separate “documentation” step - work IS documentation
4. Content multiplication: One work session = multiple content pieces

This Session as Example

This very conversation demonstrates the concept:

• User wanted a system to capture prompts/ideas/misses
• The conversation itself is content about building that system
• Meta-recursion: we’re documenting the documentation system

Related

• /session-to-blog skill - transforms sessions into posts
• /thought-dialogue skill - captures thinking process
• Show Your Work (Austin Kleon) - the philosophy

Content Angle

Multiple posts possible:

The Idea

One vault to rule them all - consolidate all knowledge artifacts into a single Obsidian hub.

Context

While building a content seed capture system, initially created a separate .content-seeds/ directory. User redirected: “BrainFucked will be hub for every idea, content, post.”

The insight: don’t fragment knowledge across multiple locations. One searchable, linkable graph.

Raw Quote

“Brain Fucked will be hub for every idea, content, post”

Why It Matters

Fragmentation kills knowledge work:

• Seeds in one place, drafts in another, posts elsewhere
• No cross-linking between related content
• Multiple search locations
• Sync/backup complexity

Single hub enables:

• Obsidian graph shows connections
• One search to find anything
• Wikilinks across all content types
• Simpler backup (one folder)

Expansion Potential

• The case for monorepo-style knowledge management
• How Obsidian’s linking creates emergent structure
• “Folder taxonomy” vs “tag + link” organization