YC Root Access

The End of the Designer–Engineer Divide

In less than a year, designer Ryo Lu helped transform Cursor from a feature-layer on top of VS Code into one of the world's leading AI code editors. He joins YC's Aaron Epstein on Design Review to talk about the path that brought him to Cursor, how rapid prototyping reshaped the core product and how he's breaking down the barriers that once separated designers and coders. Chapters: 00:00 — Designers Becoming Builders 04:11 — Learning by Building, Not Studying 08:39 — Inside Cursor’s Design Team 13:30 — Designing Systems, Not Features 17:40 — Rebuilding Cursor Around Agents 23:15 — Prototyping With “Baby Cursor” 30:52 — Design as Sculpting, Not Painting 36:10 — The Future of Designers and Engineers

RLRyo LuguestAEAaron Epsteinhost

Dec 12, 2025·42m·Watch on YouTube ↗

📖 CHAPTERS

1. 1

   Designers becoming builders: code as the shared language

   Ryo sets a clear goal at Cursor: push designers to code and blur the traditional designer/engineer boundary. He argues that AI agents reduce the fear and overhead of “learning everything first,” letting people start by building and iterating. The key shift is that code becomes the common medium for collaboration, not mockups or specs.

2. 2

   Learning by building (and how agents compress the learning curve)

   Ryo traces his path from making websites as a kid to becoming a professional designer, emphasizing self-teaching through shipping projects rather than coursework. He contrasts slow, curriculum-driven learning with agent-assisted learning-by-doing, where gaps are filled in real time. The result is faster feedback loops and less intimidation for non-engineers.

3. 3

   Onramp tools: from “vibe coding” to full-power building in Cursor

   For designers stuck in a narrow workflow, Ryo recommends starting with constrained tools (e.g., Figma Make, v0) that feel familiar. When those limits appear, Cursor becomes the step-up environment where the same interaction style scales to “anything” you want to build. Cursor’s value is flexibility: fewer constraints, broader scope, and deeper capability.

4. 4

   Inside Cursor’s design team: tiny team, everyone codes, engineers design too

   Ryo describes joining Cursor early (20 people) and scaling rapidly to ~250, while design remains a small four-person team. Because Cursor is a tool for developers, most employees are power users with strong opinions, which shapes product decisions. The design challenge becomes creating a simple core that still adapts to different working styles and preferences.

5. 5

   Designing systems, not features: primitives that scale (Notion as an example)

   Ryo contrasts feature-by-feature human-centered design with a systems-first approach. Feature accumulation tends to create button overload and fragmented concepts, while systems design decomposes problems into primitives that recombine flexibly. He uses Notion’s blocks/pages/databases as an example of stable primitives enabling emergent complexity.

6. 6

   Unifying Cursor’s AI surface: merging chat, composer, and agents into one model

   When Ryo joined, Cursor’s AI experience was fragmented: chat, composer, and agents overlapped, with confusing toggles and hidden capability. His first major change was to unify these into a single “Agent” experience with modes as settings, and to make agent the default. This reframing made the product easier to discover and helped adoption take off.

7. 7

   Rebuilding Cursor around agents: flipping the UI from files-first to agent-first

   As the world moved toward agents writing more of the code, Cursor’s interface needed to reflect that reality. Ryo explains Cursor 2.0’s “agent layout,” where you start with a prompt box, can run multiple agents, and only dive into code when you choose to review changes. The goal is approachability for new builders without losing the depth required by experts.

8. 8

   Website and brand evolution: from “futuristic gradients” to clear, interactive demos

   Ryo and Aaron critique early Cursor marketing as visually noisy and unclear, with code screenshots that lack relevance for many audiences. The newer site focuses on clarity, human-made art, refined typography, and—crucially—interactive, real-in-browser product examples. This helps users reach an “aha” moment immediately, without installation or setup.

9. 9

   Prototyping with “Baby Cursor”: a sandbox for fast, living interaction design

   Ryo introduces “Baby Cursor,” a lightweight, purpose-built prototype environment that mimics core Cursor interactions without production complexity. It lets designers explore new ideas like keyboard navigation, previews, internal browsing, and multi-agent workflows using real AI outputs and live states—things that are painful to fake in Figma. The point is to feel the product alive early and iterate quickly before upstreaming ideas to the main app.

10. 10

    Plan Mode in action: English → PRD → build → debug loop (no code required)

    Using his “real OS” playground, Ryo demonstrates Cursor’s Plan Mode: describe a goal, have the agent inspect the codebase, ask clarifying questions, then produce a PRD-like plan. After approval, the agent builds changes quickly, and the user iterates by giving feedback when something doesn’t work. This shows a new workflow where intent and evaluation matter more than manual implementation.

11. 11

    Design as sculpting, not painting: embracing imperfect first drafts

    Ryo frames modern AI-enabled design as sculpting: generate a rough but real artifact, then refine it through successive edits. Unlike traditional pixel-based workflows that produce non-functional canvases, agent-built prototypes are executable systems where interactions, motion, and states can be experienced. Designers’ advantage shifts to taste, craft, and the ability to push rough outputs into polished, coherent products.

12. 12

    The future: blurred roles, adaptive UIs, and system thinkers with deep craft

    Ryo predicts interfaces won’t disappear but will be decomposed into primitives that AI can recompose per user and context—without becoming random or unfamiliar. Designers should double down on craft and details (where AI lags) and become stronger systems thinkers who understand constraints across layers. The most important strategic advice: define the stable core concepts that won’t change over 10 years, then build everything as evolutions and recombinations of that core.