@AmeerHaio · X

your content everywhere!

@SidathRashen · X

@helloukey · X

@baptistedulac · X

time tracking for freelancers and agencies

@lynkxapp · X

u/_xtr0_ · Reddit

I built a hype almanac — a countdown calendar for everything you're waiting for Twenty-ish years ago I built a little tool just for myself to track release dates of video games I was hyped about with a funny js hype graph. I love to be able to look fw to things in my calendar. So I rebuilt it properly this time (vibe-coded the whole thing) and figured I'd share it: hypanac.com (hype + almanac -- back to the future) What it does: One calendar for everything you're looking forward to — ga

@pedromusculini · X

@FinnFreema69220 · X

Nylo - Learning plans shaped to your fixed Schedule

@vchamariaX · X

@AriaInbox · X

Aria is an AI chief of staff that reads your inbox, drafts replies in your voice, and books meetings while you sleep.

@CodewithDivine · X

check this out

@harryjwang · X

I've used many of the major conference systems. Plenty still have docs as an unsearchable static site — or worse, as PDFs that stopped tracking the product three versions ago. Somehow, still true in 2026. We took an AI-first path with instead. Our docs are generated from the codebase itself. A custom Claude Code skill writes each page and retakes the screenshots whenever a feature changes — so the docs don't drift from the product. Every page still gets reviewed by a human before it ships. Now you can talk to them, too. We just shipped "Ask AI" over our docs: This feature also turned out to be a nice teaching case for agentic RAG vs. classic RAG: • Classic RAG: chunk → embed → vector DB → retrieve once, by fixed rules • Agentic RAG: hand the model a search tool and let it drive — write a query, read the results, rewrite, retry At more than 100 pages, still no vector database needed. And every answer cites the exact page it came from. #Age