正在打开每日关注
正在打开每日关注
用 /visual-plan 将代码中的完整用户流程转成故事板,发现并修正注册与入职路径问题。
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.
是什么
这条推文把 /visual-plan 定义为一种“从代码反推用户流程”的可视化工具:Agent 阅读项目,识别注册、入职、设置等路径及分支,再生成可浏览的故事板。画面中的浏览器画布显示多个界面帧、连接箭头、缩放和评论入口;终端画面则展示 Claude Code 执行修复并回传 recap。
核心设计
核心不是把单个页面画得更精细,而是把跨页面、跨状态的体验放到同一张地图上。流程图让组织选择、自动创建、应用专属入职等路径并列呈现,帮助团队发现“以为已移除、实际仍存在”的旧分支。评论、发送给 Agent、再次生成计划,形成从观察、定位到修改的闭环;画面还记录了帧重叠修复和画布间距规则,说明可视化产物本身也需要可维护。
关键洞察
注册和 onboarding 往往最影响激活,却最难覆盖所有用户类型、特性开关和异常路径。故事板把复现成本压低,适合在实现前做方案评审,也适合在改动后做快速回顾。
边界与风险
故事板是代码与运行体验之间的近似层,不能替代真实浏览器测试、响应式检查、权限验证和埋点数据。推文仅说明其用途,未提供 GitHub README 或元数据,因此不应据此判断仓库的具体架构、安装方式或完整能力。