... mostly stick with the built in screenshot tool too. It's hard to beat when I just need a quick capture and want to paste it straight into Slack or ChatGPT. Comment from Alexander Bickov(@bickov): Tool name: SlimSnap Link: https://slimsnap.ai [ ] Free [ ] Paid [ ] Built-in OS: [ ] Mac [ ] Windows [ ] Linux Shortcut you actually press: Shift+Cmd+S for a region, Shift+Cmd+L for a full scrolling page What happens after the capture (annotate, drop in Slack, paste into ...

... shape, 11x smaller, about 99% of the pixels gone. Text that was 28px tall arrives under 3px. That's the whole reason long screenshots get useless answers. The model isn't being lazy, it's reading a gray smear. SlimSnap handles it in two parts. The capture gets cut into frames small enough to survive the resize, and the text goes over separately as JSON with coordinates, which has no height limit at all. A 28,000px page arrives intact ... ... damaged signal it received. Comment from Roopesh Donde(@roopesh_donde): Ugh that's strange, especially since it takes more tokens to process an image. I've moved on to pasting only text and logs, even for a full site. SlimSnap

... pattern before the tool existed. that order matters Comment from Alexander Bickov(@bickov): @ozandag  Team of 5 to attempt it before. That number is the whole shift Comment from Alexander Bickov(@bickov): @virko_kask   Name the human vs describe a market is the cleanest test in here. AI can only ever hand you a market, it's never sat across from the angry person. That's why its ideas feel plausible and empty at the same time. Comment ... ... solve creative velocity for small brands" would have been "you can't affordably." Now the answer is "AI generation of variations that are actually shippable, not slop." Same problem, different physics. So the split I'd draw is idea vs

... bandage" as a test for any problem statement. Quick one: do you find the bleed has to come first, or can the bandage lead if it's vivid enough? Comment from Alexander Bickov(@bickov): Problem first, always. For @SlimSnap it's this: you paste a screenshot into a coding agent and it edits the wrong element on a busy screen, so you redo the work. The fix is marking the exact element so the agent acts on that instead ... ... more than any UI polish did. So yeah, I d say naming the problem is the actual unlock. The demo just has to not get in the way of it. Comment from Viraj Parab(@viraj_parab): StartupHQ to organize competitor

... brain needs rest Comment from Mustafa Najoom(@mustafa_najoom): @busmark_w_nika  Request sent Comment from Alexander Bickov(@bickov): Love this, thanks for keeping the accountability going Nika. My Q3: Work goals: Keep the commit streak alive, ship @SlimSnap improvements weekly instead of in bursts Take marketing as seriously as building. It was my weak side, so more distribution and less hiding in the editor Build in public on X properly, share the real experience (the wins, the boring ... ... middle, the competitor

... guess which element on a busy screen I actually meant, and it edits the wrong one. Then I'm re-prompting, which is its own iteration tax. Curious how much of your rework is this specific thing versus raw model quality. And what's your fix, crop hard, or describe the element in text? Comment from Mustafa Arian(@thenameisarian): @bickov   rough box-and-label works about 70 percent of the time. label has to be specific. not 'header ... ... single element), which also happen to be the most frequent. The relational and counterfactual cases want pixels or motion. You've basically written the doc for when to use which. Mind if I borrow "useful seam" and the box-vs

... These came from people who tried the SlimSnap screenshot-to-JSON workflow during launch and asked for something specific. Listing in the order they came in. Screenshot capture for scrollable content and open dropdowns. Right now the capture clips to the visible window, so if a dropdown or long list is open, parts get cut. Balpreet S flagged this on LinkedIn. Native Mac app screenshot support (scope verification). Several people asked whether SlimSnap

... breaking, and so on. - Vaizle - I work with Vaizle, but it has very easily emerged as my fav platform. Not even lying. I can keep track of ad performance, check what competitors are posting on social. And best part is that I can feed it my own website + competitors

... flow too, so I made it: capture, annotate if you need to, and the agent reads the latest one on its own. Path and metadata handled. Screenshot as part of the conversation, not a file chore. It's called SlimSnap. Which part would you want most, the auto-send or the annotate step? Comment from Rahul Bhavsar(@rahulbhavsar): The current workflow is still too fragile. Saving the image, naming it, copying the path, and then hoping the agent reads ...

... versioning angle is the part most people skip. An annotated PNG is a dead end, you can't diff it or reuse the reference. A small structured file you can, which is basically why I ended up building SlimSnap, the arrows became fields. Were you versioning those against design history or the actual code change? Comment from Alexander Bickov(@bickov): @kalvinio  Ha, same instinct, I built one too (SlimSnap

... SlimSnap ships a Claude Code skill that auto-loads your latest screenshot so the agent reads the structured JSON without you pasting anything. That's the "magic" version of the workflow. For everything else (Cursor, Lovable, bolt.new , Replit AI, claude.ai ), the screenshot spec works but you paste the JSON into chat manually. It works, just not as smooth as the Claude Code flow. Where do you actually paste screenshots into AI tools today? Vote in the comments, ideally with ... ... break it. Comment from Hossein Yazdi(@hosseinyazdi): @bickov  I usually want bolt to edit the existing component. Comment from Alexander Bickov(@bickov): @peter_nick  Right, capture volume is upstream of paste destination. The take-vs