@hazemnassr · X

Loerei · HN

I found that describing where a broken UI is and taking screenshots for AI agents really sucks. I’m too lazy to explain an indescribable visual bug or capture a millisecond-long flash. I also don’t want to remember which file defines an element, whether it's right in the .tsx or a problem with the Parent Styles in .css. And even if you can point out the exact file, your agent still has to dig through thousands of lines of code to know what on earth you're yapping about. In a 7700-file monorepo like Cal.com, simply giving the right file in the prompt for your agent saves about 68.9% of execution time and 94.2% of the tokens your agent needs to digest. HoverSource gives all the needed information and further pushes it to -88.5% time and -94.5% tokens, basically skipping the entire digging session and jumping straight to reasoning and executing. The save is linear to how big your codebase is. I want to save tokens, but don’t want to spend my time and energy digging manually, and a junio

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

@fgiuliani87 · X

What if every blind or visually impaired child could create—and touch—their own story? ✨ Type an idea. We turn it into real Braille and raised illustrations, ready to 3D-print at home. Built with @lovable to make imagination accessible to everyone. 💜