How to Organize Your Notes for AI: Everything Is a Markdown File Now

Everything is a markdown file now.

That's not a joke. That's how I work.

Anthropic's Claude Cowork, Claude Code, Cursor — whatever tool you use — they all have one thing in common: they're only as good as the context you give them.

You can have the smartest model on the planet. Ask it to plan your week, and it'll give you a generic template. Ask it to review a client's account, and it'll give you textbook advice.

Not because it's dumb. Because it doesn't know you.

The problem nobody talks about

Most people have their knowledge scattered everywhere. Some on Google Drive, some on Notion, some in random Slack messages, and most of it in their head.

That worked fine before AI. You could just... remember stuff.

But AI can't read your mind. And 85% of what makes you good at your job lives undocumented — in your head, your inbox, or that one Slack thread from three months ago.

That's not a good setup in the AI era.

One book changed everything for me

"Building a Second Brain" by Tiago Forte. Written before the AI era even started. More relevant now than ever.

The book teaches you one thing: write stuff down. In a structured way.

Tiago created a system called PARA:

• Projects — Things you're working on now
• Areas — Ongoing parts of your life (work, health, side projects)
• Resources — Stuff you're learning or interested in
• Archives — Finished things you might need later

Four categories. That's the whole system.

I'm not saying PARA is the only way. But you need some system. The specific framework matters less than the habit of writing things down in a consistent place.

Why this is gold for AI

Imagine you have notes about:

• Your projects and what you're trying to achieve
• Your writing style and preferences
• Decisions you've made (and why)
• Research you've collected
• Client conversations and meeting notes

Now your AI can access all of that.

Want help planning your week? It knows your projects. Need a first draft? It knows your style. Stuck on a decision? It has your context from the last three conversations about it.

The AI goes from generic assistant to something that actually knows your work.

Real example

I had to create a new SEO Content Agent for a client. Instead of starting from scratch, I asked Claude: "Check my notes for previous projects and create a rough draft for the new project."

It pulled in my notes from the previous project. Read the JSON files from the n8n flows I'd built before. Read the to-do's I noted as "Next Steps" at the end of the last project. Pulled in context from the client based on my conversation notes.

All of this was available because I'd written it down. In markdown files. In a consistent structure.

Without that system, I would have spent an hour digging through old projects, trying to remember what I'd built and what I'd learned. Instead, Claude had a rough draft ready in minutes.

Your notes become instructions

This is the mental shift most people miss.

Your notes aren't just for you anymore. They're instructions for AI.

• A meeting note about client preferences becomes brand context
• A project retrospective becomes a "what to avoid" guide
• A decision log becomes reasoning the AI can reference
• A reading list with highlights becomes domain knowledge

Every note you write today makes every future AI conversation better. That's compound interest on your documentation.

How I set it up

My setup is embarrassingly simple:

1. Apple Notes — where I capture everything. Quick notes, meeting notes, ideas, to-dos
2. An MCP server — so Claude can access my Apple Notes directly
3. Markdown files in project folders — structured context that lives with the code

That's it. Nothing fancy. Nothing complex.

The tool doesn't matter. Apple Notes, Obsidian, Notion, a folder full of .md files — pick one and use it consistently. The habit of writing things down matters infinitely more than the tool.

Start here

If you're new to this:

1. Read "Building a Second Brain." Seriously. It'll change how you think about notes
2. Pick one system and commit to it. PARA, Zettelkasten, whatever — just pick one
3. Start with your current projects. Write down what you're working on, what the goals are, what decisions you've made
4. Make it accessible to your AI tool. An MCP connection, a project folder, whatever works
5. Watch what happens when your AI actually knows your context

Your notes become instructions. Your documents become context. Your system becomes your unfair advantage.

The better your markdown files are, the better your AI results will be.