@Sparsh209 · X

Hi isha! Check it out here at: Would love to hear your feedbacks

@N0V4Dev · X

I found a tool called Next AI that links AI capabilities directly with diagrams. It lets you build and edit diagrams using natural language prompts instead of clicking around the canvas manually. It's a handy way to sketch out architecture when you don't want to drag every box yourself. The project is built on TypeScript with React 19 and Next.js. It supports multiple AI providers and even includes an MCP Server. This means you can use it with the Claude Code CLI to generate diagrams from your terminal. Deployment options are flexible too. You can run the tool locally with Docker or push it to Vercel and Cloudflare Workers. It supports multi provider setups so you can pick the backend that fits your workflow. #Nextjs #AI #Diagrams #TypeScript

@butmatthew17 · X

just check it out completely for free

ghosts_ · HN

I've been slowly adding some new free tools to Moxie Docs (partly for SEO, partly to illustrate some of our feature sets before any commitment) for some reason this mermaid editor one blew up on Google rankings so I figured I'd share in case people find it useful! We also have ADR, AGENTS.md, LLMs, and a few other free tools.

@kitbasedev · X

We just launched, check us out at

Flow AI Video — 在线 AI 视频生成工具，支持文字、图片和参考图生成视频，可选择画面比例、分辨率与视频时长

@soyalexdzul · X

Open-source platform for creating, organizing, and exporting diagrams using plain text markup. It combines the power of Mermaid, PlantUML, and D2 with a polished interface

@IfeanyiArinze10 · X

What does What makes it unique?

tahazsh · HN

Hi! I’m Taha. In many agentic products that support workflows (including one I worked on), I noticed they either don’t support node-based editors, or use React Flow and go through the difficult work of integrating it into their product to run it and work with their existing logic. So I thought about creating a tool that could help with this by closing the gap between the editor and the runtime. That’s why I created Wayflow. The basic architecture is simple: you just need to create a graph (which is a JSON object) that the runtime knows how to run. The runtime doesn’t care where that graph is coming from, it just needs the right schema. And with the help of the editor, you can create the graph, and then export it or directly save it on your backend in your database. And then when you want to execute it, you just hand it to the runtime. The runtime can either stream the execution (which is useful for the editor), or give you the final result. How you execute the graph is up to you: t

@WurkHaus · X

What happens when you got told no to a 3k quote for a data tool and spend a year building one instead.

@fugteapp · X

which empowers nontechnical users to be able to customize code generated by AI or developer, and be able to share and embed it to the website they are already using

drzivil · HN

Drag boxes around and watch a layout engine infer the Flexbox (no AI)