正在加载视频...

视频加载失败

for hack week, i made a GitHub visualizer desktop app! · see your github repo in a visual format · get alerts on branch health · see diffs written in plain english instead of code · view an actual visual diff between branch/main

60,050 次观看 • 4 个月前 •via X (Twitter)

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

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)

124,151 次观看 • 1 个月前

When I’m trying to improve the user experience of my applications, one of the most valuable things is being able to see an entire user flow as a storyboard. Not just one screen or screenshot at a time. This is something I love using the `/visual-plan` skill for. You can describe any flow you want, and the agent will look through your code and wireframe out a storyboard of what the flow looks like. Then you can visualize the steps in a simplified way and spot areas to improve. Recently, I found that in certain flows we were still asking for organizations, even though I thought I had gotten rid of that and made it automatic. A quick storyboard let me see all the different code paths in a simple, visual, intuitive way. Spot the areas of the flow I didn’t want. And have the agent fix it. Sign up, onboarding, and setup flows are usually some of the most important experiences in your app. And usually the least looked at. Especially because it can be hard to reproduce every flow, for every situation, for every user type, feature flag, or whatever else you have. The `/visual-plan` skill lets you visualize any part of your code. Either to understand the current state, plan out a new state, or recap updates that were made. I’m pretty addicted to this skill. I use it for a lot of other things too, so let me know if you want to see videos on those. And of course it’s all open source. You can grab it on my GitHub. I'll link to it in the thread. If you try it, let me know your feedback.

Steve (Builder.io)

147,324 次观看 • 29 天前