Productivity1 month ago
Prodigent
Document product decisions and reasoning in one shared layer for team collaboration.
@TimEngng · X
Stop losing the "why" behind product decisions -
The full gallery
Tech stack
5 projects
Document product decisions and reasoning in one shared layer for team collaboration.
@TimEngng · X
Stop losing the "why" behind product decisions -
Audit citations and verify authorship to prove the authenticity of your academic work.
@clawncore · X
Chat-first workspace for teams to consolidate conversations, files, and feedback from scattered tools.
@AmaaN_AshiF · X
I Built this for 2 weeks with Claude code It’s now a working beta Product A chat first workspace for teams whose work gets scattered across chats, files, feedback and project tools. Free to try right now.
A minimalist task management tool designed for team simplicity and focus.
@trackowork · X
Manage academic conferences: submit and review papers, handle scheduling and registration.
@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