I thought about just sharing a Figma link since most of the people I get feedback from already have accounts, but the prototypes I build with Claude aren't Figma files, they're actual working HTML, so I'd have to redo the whole thing in Figma just to get comments on it. ProtoNote takes the thing I already built as-is and skips that step entirely, plus reviewers don't need to make an account, which matters when I'm sending it to people outside my usual circle.
ProtoNote
As a Product Owners moving from Figma to Claude Code and constantly looking for feedbacks from stakeholders and testing users, this is life saver for me!
ProtoNote
@dct_iz_dct Figma to Claude Code is one of the shifts that made me build this. If you’re already in Claude Code, you should try out the connector so you can publish and pull notes back without leaving the terminal. Would love to hear how it goes with your testers!
The scattered screenshots and vague "fine by me" replies have quietly worn me down for years, so feedback that lands right on the spot it's about feels so much saner. Nice work, @zach_friesen.
ProtoNote
@jean_noel_escande You and me both. Appreciate it Jean-Noël!
BetterClaw
The feedback loop between building and improving prototypes is usually the painful part. Making comments more contextual and connecting them directly with AI workflows feels like a smart way to speed things up.
ProtoNote
@better_shaya Yeah, the loop is the whole problem. Feedback that isn’t attached to a specific spot on the page turns into a translation job, where you’re reading “the button feels off” and guessing which button. Pinning it means the note arrives with its own context, and once Claude can read those notes directly there’s no re-typing step at all. That last part is the piece I’m most curious to see people use.