Design to Code in 45 Min with Cursor's Head of Design

Lu and Yang ask Cursor to add a calculator to the retro OS. Plan Mode researches the project, drafts an implementation plan, and lets Lu edit the spec before building. He says the agent can handle much of the work in one pass, with local review and fixes along the way.

Lu says the OS began as a soundboard with default Tailwind and shadcn styles, then grew into a collection of retro-inspired apps. He uses shadcn components and a theming layer, and researches old computers to understand their visual patterns and constraints. The project also serves as a playground for testing Cursor features and models.

Lu describes Cursor’s workflow as a mix of local editing and background agents for defined tasks, with designers, engineers, and PMs working across traditional role boundaries. He says Plan Mode grew from user workflows and internal experiments, and uses a Markdown plan to make product decisions reviewable before implementation. Cursor gathers feedback from ambassadors and nightly users while adapting its direction as models and workflows change.

Lu advises designers to start a small project in Cursor and learn concepts such as components, props, and how software fits together. He says prototypes in code reveal live states and behavior that static mockups can obscure. Designers can use agents to make visual changes and ask for explanations, reducing some of the repeated handoff between design and engineering.

Lu favors simple core concepts that can combine into more capable experiences, rather than minimal products with narrow limits. He points to code, agents, models, and tools as Cursor’s foundational pieces, and says product teams must balance flexibility, complexity, and ease of use.