<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: flo_r</title><link>https://news.ycombinator.com/user?id=flo_r</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Mon, 15 Jun 2026 04:46:12 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=flo_r" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[Show HN: Velyr – an AI agent that finds and fixes conversion leaks on your site]]></title><description><![CDATA[
<p>Article URL: <a href="https://velyr.io/">https://velyr.io/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=48525761">https://news.ycombinator.com/item?id=48525761</a></p>
<p>Points: 7</p>
<p># Comments: 1</p>
]]></description><pubDate>Sun, 14 Jun 2026 10:00:55 +0000</pubDate><link>https://velyr.io/</link><dc:creator>flo_r</dc:creator><comments>https://news.ycombinator.com/item?id=48525761</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48525761</guid></item><item><title><![CDATA[New comment by flo_r in "Show HN: Paca – Lightweight Jira alternative for human-AI collaboration"]]></title><description><![CDATA[
<p>Gh issues works surprisingly well as an agent board. Labels for state, one issue per feature. The part i haven't figured out yet is how to know when the output is actually done vs just "looks done" to the agent.</p>
]]></description><pubDate>Sat, 13 Jun 2026 17:12:02 +0000</pubDate><link>https://news.ycombinator.com/item?id=48519244</link><dc:creator>flo_r</dc:creator><comments>https://news.ycombinator.com/item?id=48519244</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48519244</guid></item><item><title><![CDATA[New comment by flo_r in "Slightly reducing the sloppiness of AI generated front end"]]></title><description><![CDATA[
<p>Tried macOS HIG for the same reason and got similar results, less slop, more structure. I think what's happening is that the model has a very specific grammar to pull from instead of averaging over everything web-related it's ever seen.
The SaaS one is interesting as a control, it's essentially asking for the average of all modern web UI, so you get exactly that.</p>
]]></description><pubDate>Fri, 12 Jun 2026 20:39:15 +0000</pubDate><link>https://news.ycombinator.com/item?id=48509179</link><dc:creator>flo_r</dc:creator><comments>https://news.ycombinator.com/item?id=48509179</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48509179</guid></item></channel></rss>