3作者: flowscape_ui大约 1 个月前原帖
Hi HN,<p>I’ve been working on Flowscape, a 2D canvas engine focused on building interactive editors and visual tools. It provides low-level control over scenes, nodes, and interactions without enforcing a specific UI or workflow.<p>The goal is to give developers a flexible foundation for custom editors, diagrams, and canvas-based interfaces. I’d love feedback on the API design, architecture, and real-world use cases.<p>Demo: <a href="https:&#x2F;&#x2F;flowscape-ui.github.io&#x2F;core-sdk&#x2F;?path=&#x2F;story&#x2F;interactive-playground--interactive-playground" rel="nofollow">https:&#x2F;&#x2F;flowscape-ui.github.io&#x2F;core-sdk&#x2F;?path=&#x2F;story&#x2F;interac...</a> GitHub: <a href="https:&#x2F;&#x2F;github.com&#x2F;Flowscape-UI&#x2F;core-sdk" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;Flowscape-UI&#x2F;core-sdk</a>
1作者: covibes大约 1 个月前原帖
We&#x27;re releasing the next-gen Ralph Wiggum architecture - agent clusters with independent validator agents with clear rejection mandates. As long as the code is not feature-complete and production-grade, it will not be approved. The result is AI without any need for babysittng.
1作者: paulistaunb大约 1 个月前原帖
Hey,<p>Problem: Interface between front and back never match at first try !<p>Setup: 4 agents in parallel: front, back, infra and debug<p>Process: Vibespec the initial need and let&#x27;s the agents work on their domain. I asked to created the interface document before starting but even though I does not worked as expected.. I am spending around 30 minutes to make it match !<p>How you guys are solving this issue ?
1作者: Richardsonsimon大约 1 个月前原帖
As a non technial developer I don&#x27;t know how to test the functionalities of my platform. I always ask cursor to just check if everything works well or not. But Cursor is not God, it is not built for testing. So If i&#x27;m facing this issue then definitely others might also be facing this issue. So I&#x27;m currently working on Rihario with my co-founders to help others like me from UX bugs hell.<p>You paste your URL &gt; a virtual browser opens up along with execution logs &gt; A headless browser runs your site and tests almost everything when it comes UI&#x2F;UX &gt; Generates a report on what has passed the test (standard expections of a product) and what had failed &gt; Generates a prompt to help you resolve those exact errors