frankanaya.com
This entire site — a full brand, a design system, and 40+ pages — designed and shipped by directing AI, not hand-coding it alone. The thing you’re reading is the proof.
Astro · a token-driven design system See it →
The Build Log · proof, not promises
I don’t talk about AI. I build with it.
Most people teaching AI have never shipped anything with it. I build real tools and systems — an Obsidian plugin, a slide engine, this whole website and design system — by directing AI, not just prompting it. This is the receipts page.
The next decade of knowledge work
In the AI era, the people who build win. Everyone else gets automated.
Consuming AI content makes you a spectator. Prompting it for one-off answers makes you a user. Building with it — owned tools, systems, and work only you could make — is the only position that compounds. That’s the whole bet, and it’s why I do this in public: so you can watch it, then do it.
The receipts
Things I’ve built with AI.
Not screenshots of a chat. Real, owned, shipped tools and systems — most of them for the exact work I teach.
Oak
A plugin I built so capturing a thought into Obsidian takes seconds, not clicks. Real software — shipped to real users — built with AI at my side.
Obsidian · fast capture See it →
Slide Studio
Turns any script into a branded, on-brand slide deck — the ones in my videos. Runs 100% offline, no per-deck AI cost. An owned tool, not a subscription.
Node · Marp · offline Built with AI
The Field Log
A daily publishing system with a printable toolkit and an 8-prompt AI Playbook — built end to end with AI, from the landing page to the PDFs to the render pipeline.
System · PDF pipeline See it →
Freeform
A visual board for thinking out loud and teaching — ideas arranged in space, not trapped in a list. Built to match how I actually think.
Obsidian · visual thinking Built with AI
Bark Trail
The tokens, type, and reusable components — like the connection graph in my videos — that keep everything on-brand. A system that compounds, not a one-off.
Tokens · components See it →
Why this matters for you
This is what I mean by a system you own.
Every one of these started the same way: my own thinking, captured and owned — then AI aimed at it to build something real. That’s the difference between taking notes and building. One fills a folder. The other ships things only you could make.
You don’t have to become a developer. You have to stop being a consumer. If you’re an expert who’s tired of just learning about AI — and ready to build with it — that’s exactly who I teach.
The consumer
- Watches AI tutorials
- Collects prompts and tools
- Ships nothing they own
- Replaceable by the next tool
The builder
- Aims AI at their own thinking
- Owns the tools and the output
- Ships work only they could make
- Compounds — and can’t be copied
Stop consuming. Start building.
Build something that’s yours.
I’ll show you how to turn your own expertise into owned systems that ship — the same way I built everything on this page. Watch the method free, or build it with me.