61–67 of 67 posts
This meant endless screenshots and descriptions back and forth to the LLM. Expensive in tokens and time.
I built Drawbridge to batch multiple context-rich (JSON Prompts) and screenshots for Claude or Cursor to process.
Hope this helps! https://github.com/breschio/drawbridge
Mainly using playwriter.dev to help debug CSS issues on the page. It's an extension you can enable in Chrome and let agents control the browser via CDP https://github.com/remorses/playwriter
Interesting, thanks To your opinion, what's the benefits compared to the native Chrome remote debugging feature + the chrome-devtools MCP?
Another benefit is context usage.
The cli can also do a lot more than other MCPs because it uses code snippets run in a stateful sandbox to control the browser, so it can do virtually anything instead of just a few exposed tools like `scroll`, `click`
Rounds will focus on a particular task like integration, ui, verification. Multiple rounds can be tasked one after the other Eg
2 integration rounds, 2 improvement round and 2 verification rounds.
This allows to pick up issues it would normally glaze over or not mention.
Styling is okay, but layout seems to be a sore point for llms.
Earlier quoted context omitted.
This is almost a meme reply on HN: absolving the LLM by comparing it to an inexperienced human.
I think the meme is trying to discredit LLMs by saying they don’t read your mind and produce exactly what you wanted from vague prompts. Everyone who uses LLMs knows that it’s an iterative process where you need to provide specific instructions. It’s only the LLM naysayers who think that pointing out that “Generate a modern UI for me” doesn’t create perfect results on the first pass is an indictment of LLMs.