@helloukey · X

@mj_jimmi · X

@mr_wickedhacks · X

Write the doc once → get a notebook, slide deck, canvas, or resume from the same source. No rewriting for every format.

@EnzoV_sc · X

I’ve built a skill for agent orchestration so I don’t have to explain any session how to manage the next task. Pretty useful Through I can make my orchestrator spawn as many agents as it needs, from all harnesses (Claude Code, Codex, Grok Build etc..)

@iPranayJoshi · X

Would be honoured to come join! Built talk about vibe coding at

@AjayGB4 · X

@palak07rajput · X

@baptistedulac · X

time tracking for freelancers and agencies

@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

@AshiveCompany · X

@aviralgarg05 · X

Here's what you get on One toolkit. Every design task.

@almalimir · X

– a @YouTube extension for organizing videos