For anyone designing sites, this is an insane Fable 5 UI/UX hack. https://www.tasteskill.dev/

~ link <---

Hey everyone. Love that so many of us are building second brains now. I wanted to open a discussion on the architecture underneath, because I think that's where it gets interesting. Most of what I see here is file-based: @Daniel Agrici YouTube Brain and the per-client Obsidian brains in SEO Office, markdown on disk the agent reads. For those of you running that, how are the results holding up as the brain grows? Does the agent still pull the right context, or does it start grabbing too much? What challenges/issues are you facing with this approach? On my side I've built a few systems with RAG and vector databases feeding the agent, and they've worked really well, especially once the knowledge base gets big and retrieval matters more than just reading a folder. I'm designing a couple of second-brain architectures right now and deploying them soon, so I'm genuinely curious how the two approaches compare in the wild. Open question: what are you running, files, vector, or a hybrid? And what actually worked vs what broke once real usage hit it?

~ link <---

Claude SEO just crossed 10K on GitHub. Schema, audits, GEO, and answers to the questions everyone's asking. Built with you 😇