@lynkxapp · X

@Puneet626 · X

hi, let's connect, i'm building

@abhishekbariyaa · X

@HossainArif85 · X

Building — a platform for paid events where organizers manage registrations, approve payment proofs, send QR tickets, and check attendees with any phone browser. Happy to connect with fellow builders!

@AbhinavtejR · X

@sardamit · X

2-3 years ago, i built the waitlist app for a very popular date place in Mumbai i rebuilt it today using vibe coding

@Jatinthadani1 · X

@pgardunoc · X

I vibe coded this for the World Cup, and other projects

@vaultmeet · 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

@zeuscode21 · X

Save time when building with

@twfaria · X