@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.

@iamdeepak89 · X

@neon_time · X

@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

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

@itz_sayan_03 · X

Ever wondered how cinematic scroll-driven websites are built? 👀 Meet SectionFlow—an open-source React library with 60+ ready-to-use section transitions, a one-command CLI, reusable sections, and optimized performance. 🚀

chenglong-hn · HN

Data visualizations are the bridge between user and data. But building AI agents that can generate visualizations reliably can be very tricky: - simple chart specs can be reliable, but generated charts are often of low quality due to reliance on system defaults; - complex chart specs with explicit details can produce good-looking charts, but they are verbose and agents can struggle with reliability We figured out it is a limitation on the language issue (not just AI capability thing) -- current visualization languages are a bit too low-level for AI agents, requiring them to explicitly make visual decisions that are supposed to be handled by a good compiler. Flint is a visualization intermediate language to address this issue, allow AI agents to solve this last-mile human-agent interaction problem. It provides a simple semantic-type based specification, and contains a layout optimization engine that can produce good-looking charts (filled with derived low-level details) from simple

@IfeanyiArinze10 · X

What does What makes it unique?

drzivil · HN

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