正在加载视频...

视频加载失败

I made a guide for prompting impressive UI code After creating 120 components in a week while working on Aura, listed all the techniques I used: frameworks, styles, framing, html-to-code, image-to-code, etc. AI is getting so good at creating user interfaces.

117,197 次观看 • 1 年前 •via X (Twitter)

11 条评论

Meng To 的头像
Meng To1 年前

Here's the url: This is going to evolve. I think, for the first time, esp with Claude 3.7, I'm confident that AI can generate amazing user interfaces. The industry is going to change so much as a result. Because of this, I had to build a huge browse section with a ton of navigation. We're at 200 components, but we'll grow to 1000 within the next couple of weeks.

Coral AI News 的头像
Coral AI News2 年前

Coral AI is the most powerful AI for documents. See the difference yourself:

Mohammad Bagher 🦋 的头像
Mohammad Bagher 🦋1 年前

amazing stuff! just wanted to share this

Meng To 的头像
Meng To1 年前

It's the content loading, not sure why it does that. Can you try reloading?

Eli Schiff 的头像
Eli Schiff1 年前

Would be cool if there were an embedded prompt-building workflow

Meng To 的头像
Meng To1 年前

Working on something visual for that!

akhil 的头像
akhil1 年前

i'm working on a project that requires generating code outputs with a nice UI are you going to open this up to access via API at any point?

Meng To 的头像
Meng To1 年前

do you mean the ui component code via api?

Dylan White 的头像
Dylan White1 年前

120 components in a week? That’s some serious wizardry!

Meng To 的头像
Meng To1 年前

As with AI, there's a lot of reimagining, adapting, including html files/figma urls, hence the high count.

Matthew Payne 的头像
Matthew Payne1 年前

Ayyy this is incredible!

相关视频

Introducing /visual-plan - a skill to generate rich, visual plans for Claude Code and Codex. Plan mode in Claude Code is incredible. But I always find my eyes glazing over when it gives me this huge markdown essay in my terminal. I found I can make much better visual plans with reusable components. So I made a skill called `/visual-plan`. It generates plans as MDX with visual, interactive components. Diagrams, interactive API specs, schema design changes, annotated code, and even pan and zoomable wireframes. So for any UI work, you can look at a wireframe first, comment on it, iterate, and then have the agent work. I’ve found this to be a much more intuitive interface for reasoning about what the agent is doing. It’s somewhat inspired by that popular post about how HTML is better than Markdown. But HTML can be slow and verbose to write. And it doesn’t look good checked into a repo. This has really made me feel like humans and engineering are entering a new abstraction phase, where we reason about things at the plan level. As long as the plan is good, agents are getting more and more reliable at executing on it. Almost to the degree that we trust the C compiler to compile to assembly reliably. Plans are the new intermediate representation. I also made a skill for the reverse of this, called `/visual-recap`. After the agent works, it gives you a recap of everything it did. Same idea: wireframes, interactive API specs and diffs, schemas, annotated code, etc. So now when you’re reviewing what the agent did for you, or looking at a pull request of somebody else’s code, you can see a visual recap instead of just reading a wall of text. It’s all free and open source. You can find it on my GitHub. Will link to it in the reply because we all know how dumb these algorithms are with links.

Steve (Builder.io)

125,708 次观看 • 2 个月前