KP81

Vibe coder

[KP81 @KP81X]

No matter what idea I throw at Claude or GPT, it acts like a cheerleader.
“Great concept… strong potential… clear need…”
So how do you actually know if it’s a good idea?
I’ve stopped asking “is this a good idea?”
Now I ask: “Evaluate this idea. List all the pros and cons and justify every point with a source.”
Then I go read the sources myself.
That’s the process that led to Brainary → https://t.co/82Y9rOBti8
Free, no sign-up. Point it at your docs and it builds a local wiki with citations.
Would love any feedback if you try it.

[KP81 @KP81X]

If you’re tired of vibe-coded prototypes that fall apart when complexity hits — try the structured approach. The files are the force multiplier.
What are you using for the “rules + staged build plan” part? Drop your systems 👇

[KP81 @KP81X]

Most people think vibe coding is: talk to Claude → get one big prompt → dump it in Cursor → print money.
That’s how you get a weekend prototype. It’s also how you get a mess the moment the project needs real scale or testing.
Here’s what actually works 🧵

[KP81 @KP81X]

This is how I built Brainary — turns your documents into cited, verified wikis.
Not a weekend project. Even with heavy AI help: 8+ hrs/day, 7 days/week, months. Scale and rigor demand discipline.
https://t.co/smJnpYOClZ

[KP81 @KP81X]

Brainary now runs on Mac, Windows, and Linux. “Windows only?” — not anymore. Point it at your documents and it builds a cited, verified wiki. Run it fully local on your own models, or mix in the frontier ones. If you held off because it wasn’t on your OS — it’s there now: https://t.co/RPnyUQlyLF

[KP81 @KP81X]

@ShannonJean Is it urgent? Have a close connection or is that the final destination? If you can wait, wait. If not, when people are deplaning, there are pockets of wait time, make your way back in those pockets.

[KP81 @KP81X]

@OfficialLoganK Sent a DM with my application

[KP81 @KP81X]

@jjfleagle @GoogleCloudTech Try https://t.co/wJyzvIy28k you can build a wiki for all your docs (in any format and however large pile you have) and one click export to OKF

[KP81 @KP81X]

@__ShaikhAmmar__ @karpathy Try https://t.co/wJyzvIy28k you can add 1000s of documents and it builds the wiki for you. No coding, just drag and drop.

[KP81 @KP81X]

@akamoe98 @joelhooks Try https://t.co/wJyzvIy28k you can just drag and drop and is ready to go!

[KP81 @KP81X]

@_SteveBrown @plainionist What if you can take all your projects docs and can automatically build a wiki and with one click export to OKF and Obsidian. Would you use it? Checkout https://t.co/wJyzvIy28k

[KP81 @KP81X]

@cartmanx404 I built LLM wiki tool with even more features like chat, report writing and many others. Can export to Obsidian, or in OKF. Remains local and is only $8.99/month. Why pay $2k?

[KP81 @KP81X]

@Zgreene17 @samzliu I built https://t.co/wJyzvIy28k to build wiki for you with any documents and can handle 1000s (built for more but I tested with 7000 pages) and you can export to obsidian or in OKF

[KP81 @KP81X]

@amelapay @NickADobos Try https://t.co/wJyzvIy28k it builds the wiki for you from any and all of your docs, including handwritten notes and ebooks.