HN 提问：小型团队开发者们——在人工智能时代，你们如何与 UI/UX 设计师协作？
2 分•作者: cameronnimmo•大约 2 个月前
我们是一家两人产品公司，我和我的联合创始人（他是一名产品设计师）在人工智能改变我们交付产品的方式时，一直在努力优化设计/开发流程。
存在几个相互关联的问题：
1. 随着我们加快速度，前端代码中由 AI 生成的比例越来越高，这意味着会出现更多细微的 UI 错误和不一致。这些通常是可以通过代理（agent）轻松解决的问题，但据我所知，针对现有中等规模代码库的代理编码工具往往以开发者为中心，设计师难以设置/使用。
2. 最初所有设计都在 Figma 中完成，但逐像素调整每个屏幕的感觉越来越冗余。所以理想情况下，我们只想依赖在 Figma 中构建的核心组件，然后通过代码实现它们。但当然，当我们想更改现有组件时，我倾向于直接在代码中实现更改，获得设计批准后就上线：Figma 从未更新，因此它几乎被弃用，而生产环境中实际的组件系统变得笨拙且不一致。
想知道是否有人遇到过这些问题，以及你们是如何解决的？以及更广泛地说，早期团队目前的设计/开发流程是什么样的？
查看原文
Running a 2 person product company, my cofounder (product designer by trade) and I are struggling to get the design/dev process right as AI transforms the way we ship.<p>There are a couple of interrelated problems:<p>1. As we move faster and a higher proportion of our frontend code is AI generated it means more minor UI bugs and inconsistencies.
These are generally things that could be zero-shotted by an agent but from what I've found the agentic coding tools for existing mid-sized codebases tend to be developer-focused and not easy for a designer to setup/use.<p>2. Everything was originally designed in Figma but pixel pushing every screen is feeling increasingly redundant. So ideally we'd just rely on some core components built in Figma and then vibe code their implementation. But of course when we want to change an existing component, I tend to just implement that change in code, get design-approval, and ship it: figma never gets updated, so its been pretty much discarded and the actual component system in production has become unwieldy and inconsistent.<p>Wondering if anyone can relate to these issues and what you're are doing to solve them? And more generally what the design/dev process is looking like these days in early stage teams.