upvote
I personally rely on my claude setup and it's memory feature, and that's what plugs right into onlook. I don't end up repeating myself because those lessons learned across sessions persist. That and having a good base design reference to work from.

Also the agent in onlook is very visually aware and capable, it's constantly verifying work and sees exactly what you see, so I've rarely seen it diverge from the existing components or screens you have up. give it a try and see if it feels more aligned than you get in something like claude design.

reply
that's pretty frustrating and there are a lot of ways we keep designs aligned with your real product

When you work in Onlook you work on top of the real codebase, so whether you're starting a project to make a real edit on the running app, or you're just starting a project to make prototypes or sketches off of the foundational codebase, you are pointing the agent to the real code.

Think of Onlook more along the lines of working on top of code and apps rather than just flat HTML/CSS (like what Claude design does). It gives you more power because if you wanted to, you can actually reference a specific part of your repo and build with real React components.

If you set up your codebase to have a design system, you can start every ideation exercise as a new project in Onlook from that repo.

reply