@MahatiSingh · X

@Hamzadevio · X

just shipped. my goal is to help founders add taste to their vibe coded ugly looking apps. (especially the purple gradient, can't see it no more..)

@businessHunter_ · X

Business Hunter scans Reddit, HN and GitHub for real demand signals → tells you exactly what to build before you write a line of code.

@deepnlp_contact · X

We are launching Craftsman Agent Studio & Store today on PH, which turns creative ideas -> Agentic Designs -> Connect to skilled craftsman -> Physical products. you like to checkout our launch?

@versuchai · X

@milonspace · X

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

@baptistedulac · X

time tracking for freelancers and agencies

@James_Gibbons2 · X

Check out - the AI that builds your website for free!

@cecond_thoughts · X

Don't know about vercel but a website can have and only have its frontend vibe-coded, and backend not vibe coded but hosted on railway.

@12squaredAI · X

| @fieldcam_app

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

@foldtaskapp · X