
Alex Tran
11 posts




you can instantly 10x your vibecoded frontends by just learning what different ui components are called ofc opus is creating generic slop, the only words you know are menu and button.

we just launched the first AI for design system components designers create components in figma. engineers install generic libraries. shipping a design system that's truly yours is the real work. that's why we built an AI agent for design systems. prompt, screenshot, paste a Figma frame, or import code → get custom React components with variants, props, and slots you can edit visually. then, sync it to your codebase with Cursor or Claude Code. it reads your existing components. it reviews its own work. it builds with your system, not a generic one. start building your design system with @SubframeApp .



You should consider your existing code, tests, and docs as a part of your "prompt" for autonomous agents. If those are miserable your results will be miserable as well. Clean those up and your agents (and the humans working with them) will be much more effective.

Tired: code or canvas Wired: code AND canvas Introducing Claude Code to Figma


Today we’re launching Design Canvas for AI agents. AI can build a feature, but every "design tweak" turns into another prompt. We built a drag & drop editor for Claude Code, Cursor, Codex to explore and iterate on your UI, so you get the best design by default. No endless prompting. Ship better designs in code with Subframe.

imagine figma but everything is code imagine v0 but you can drag-and-drop imagine prompting by commenting on designs

