How to Build an AI Second Brain for Design Work
For freelance designers and creatives · Based on Matt Giaro AI Second Brain Build
// TL;DR
Freelance designers lose track of the tutorials, articles, and inspiration they consume, and generic AI advice doesn't reference what they've actually studied. This framework builds a three-pillar system in Obsidian and Codex: a Wiki seeded with your design content, a Journal that grounds responses to creative blocks in your own saved material, and a CRM for clients and collaborators. When you journal 'I feel creatively blocked,' the AI replies by citing a video you saved two weeks ago — not boilerplate advice. Use it to stop losing inspiration and to make AI a studio partner that knows what you know.
Why do designers keep losing their best inspiration?
You save a brilliant typography breakdown, bookmark a motion design tutorial, and watch a YouTube deep-dive on colour theory — then never see any of it again. This is the Dumping Ground Problem: information goes in and never comes back out. Most note systems are passive archives. The AI Second Brain Build fixes this by adding an active processing pipeline that turns everything you save into a cross-linked, queryable wiki.
As a freelance designer, your edge is the breadth of references and techniques you can pull from. A second brain that actually resurfaces them when you're staring at a blank artboard is worth far more than a folder of forgotten bookmarks.
How do you set up the three pillars for design work?
Start with the non-negotiable core: the Wiki/Knowledge Base. Install Obsidian, create a vault, and add the Obsidian Web Clipper to Chrome. Configure it to save to a RAW folder. Now every design article, Behance breakdown, or YouTube tutorial you clip — including the full video transcript — lands in RAW untouched.
Open the vault folder as a project in Codex, prompt it to build the wiki architecture from Karpathy's LLM Wiki blueprint, and configure your agents.md to extract entities like design tools, techniques, and principles. Seed 5–10 sources to kickstart cross-linking.
Then add two custom pillars:
- Journal — for working through creative blocks with AI grounded in your own saved content.
- CRM — to store notes about clients and collaborators you meet at events.
What does a grounded response look like for a creative block?
Here's the payoff. When you start a chat with the trigger word `journal` and write 'I feel creatively blocked on this client brief — everything I make looks generic', the system doesn't hand you recycled motivational advice.
Instead it gives a Grounded Response: 'You saved a video two weeks ago about design constraints as creative fuel — it suggested deliberately limiting your palette to three colours. You also clipped an article on working from reference boards.' The AI anchors its answer to material you've already deemed valuable, making the advice land because it's yours.
Over time, Pattern Detection kicks in: the journal scans past entries, notices you tend to feel blocked at the start of every client project, and factors that recurring theme into future responses.
How do you keep track of clients and collaborators?
After a conference or client call, open Codex and say 'Add to CRM: Jordan Lee — met at Config, discussed design systems, art director at a fintech startup, follow up about a possible rebrand project.' The system creates a contact file, maintains an alphabetical index with a short bio, and cross-links Jordan to any wiki pages on design systems.
Months later you can ask 'What did I discuss with Jordan about design systems?' and get an answer drawing from both the CRM record and your wiki.
How do you keep it running without manual effort?
Set up the hourly automation in Codex so new clips are processed automatically — you just clip and forget. Connect a private GitHub repo so everything backs up every hour. Then watch the Obsidian graph view: as design tools, techniques, and client names interconnect, you'll see your creative knowledge becoming a living web.
Next step: Install Obsidian and the Web Clipper, then clip the five best design resources you've saved this month into a RAW folder and run your first processing pass in Codex.
// FREQUENTLY ASKED QUESTIONS
Can I use this for visual references, not just text articles?
Yes. The Obsidian Web Clipper saves web pages and YouTube videos into RAW, and you can store attachments in the optional RAW/Assets folder. While the AI processes text and transcripts into wiki pages, you can link image references to those pages. The graph view then connects your visual inspiration to the techniques and principles extracted from written sources.
How does journaling about creative blocks actually help?
Because the journal grounds responses in your own saved content rather than generic advice. When you write about a block, it cites specific videos or articles you clipped on that exact topic. Over time, Pattern Detection notices recurring struggles — like feeling stuck at the start of every project — and factors those patterns into increasingly personalised, relevant suggestions.
What if I don't need a CRM as a solo designer?
Swap it for any domain-specific pillar — the CRM is fully customisable. You could use it for a 'Project Log' tracking past client briefs and what worked, or a 'Techniques' log of methods you want to master. Only the Wiki/Knowledge Base is non-negotiable. Configure whatever relational layer fits your workflow in agents.md.