@javimosch · X

dpc94 · HN

Devthropology – Better Insights for GitHub Repos

musekit · Product Hunt

Free AI Tools Free browser tools for everyday tasks, no login

@milonspace · X

A specification nobody can find is functionally the same as no specification.

@IfeanyiArinze10 · X

What does What makes it unique?

@tools_loop · X

@zubidavies · X

@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

@ArnavGupta47851 · X

Vibe coding is fun. Sharing what you built is not. So I built unlocalhost. Tell your coding agent to deploy, say who is allowed in, and you get a real link with a login wall already in front of it.

@V1Gameboy · X

Do you want to make passive income from your GitHub code? Try a site that let's you put ads on in the README section of your repository to earn money.

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