How does it handle taking instruction about things like what stack to use?
E.g. if I'm building a new prototype, I personally would want to build with Tailwind, but lots of people think Tailwind is evil and prefer prototyping with <other_css_thing_they_like>
Also curious to hear what you think of the quality of the output code. My experiences with LLMs doing frontend code has been a pretty mixed bag personally
There's a dropdown where you can choose a stack for screenshots (Tailwind, React, Vue, etc.). I haven't updated the prompts for the video feature just yet. You can tweak the prompt yourself here: https://github.com/abi/screenshot-to-code/blob/6069c2a118592...
Comments
Looks awesome!
How does it handle taking instruction about things like what stack to use?
E.g. if I'm building a new prototype, I personally would want to build with Tailwind, but lots of people think Tailwind is evil and prefer prototyping with <other_css_thing_they_like>
Also curious to hear what you think of the quality of the output code. My experiences with LLMs doing frontend code has been a pretty mixed bag personally
Thanks!
There's a dropdown where you can choose a stack for screenshots (Tailwind, React, Vue, etc.). I haven't updated the prompts for the video feature just yet. You can tweak the prompt yourself here: https://github.com/abi/screenshot-to-code/blob/6069c2a118592...
The quality of the output code is solid, I think. You can see the code for the examples: https://codepen.io/abi/pen/ExJPdop and https://codepen.io/abi/pen/jORWeYB
I think the biggest thing LLM code is typically missing is better abstractions/componentization. You could probably prompt around some of that.