@helloukey · X

@itzKashan2912 · X

@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

@AadyaAI · X

Aadya AI turns a client conversation into a branded, ready-to-send proposal or invoice PDF in 60 seconds — no templates, no formatting, no chasing.

ShamarWebster · HN

Store Front For Vibe coded apps

@discorev · X

I've been working on - Using gpt-5.6-sol and Fable in Claude Code via CLIProxyAPI. I've found using these two together with Claude Code Workflows is a killer combination

@ReleasePilotHQ · X

Just shipped ReleasePilot. Connect GitHub → push code → release notes write themselves. No Actions. No config. Just push. Free for 1 repo & free trial → #buildinpublic #indiehacker #saas #github

@uwais_jawed · X

Rank higher on Google Maps O_O

@zarektech · X

- AI Launching Tool