Cursor prototypes a Rotis homepage from Figma
Phil Sayer used Cursor and Figma MCP to prototype a homepage for an online archive of the Rotis typeface. The result captured the design’s layout, colors and hover states, while missing the intended font and font weights.
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Implement the selected Figma frame in HTML and CSS. Inspect its design properties, preserve hover behavior, and report unavailable fonts and remaining visual differences.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source author
- Phil Sayer
- Original account
- Read the source ↗
- Published
- 5 Aug 2025
- Source link checked
- 15 Oct 2026
- Reported result
- Phil Sayer used Cursor and Figma MCP to prototype a homepage for an online archive of the Rotis typeface. The result captured the design’s layout, colors and hover states, while missing the intended font and font weights.
- Human involvement
- Sayer prepared the repository and Figma selection, inspected the result and identified incorrect fonts and weights; further tweaking remained.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Open the archive’s Git repository in Cursor and connect Figma MCP.
- Copy the selected Figma Dev Mode URL into an HTML/CSS implementation request.
- Inspect the generated layout and hover states, noting incorrect font and weights.
Phil Sayer used Cursor and Figma MCP to prototype a homepage for an online archive of the Rotis typeface. The result captured the design’s layout, colors and hover states, while missing the intended font and font weights.
The experiment followed a disappointing attempt to build the page from static mockups in another tool. Sayer instead connected Figma’s structured design information to Cursor. He created a local Git repository, synchronized it with GitHub and opened it in the editor.
In Figma Dev Mode, he selected the content to build, copied its URL and included it in a request for HTML and CSS. The MCP connection gave the agent more information about how the design was constructed than a screenshot alone. Cursor generated highlighted code changes that the author could inspect before keeping or regenerating them.
Sayer reports a promising first result after one prompt, with more tweaking still needed. He suggests the missing typography may have reflected the unavailable Rotis web font; that explanation is not independently established. The account does not claim a complete production site, accessibility audit or pixel-by-pixel match. It documents an inspected design-to-code prototype with a clear remaining limitation and a comparison to the author’s earlier approach.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: designphilosophy.substack.com · Phil Sayer
Frequently asked questions
What did the agent do?
It generated HTML and CSS from Figma design context, reproducing layout, colors and hover states but missing typography.
What remained the human’s responsibility?
Sayer prepared the repository and Figma selection, inspected the result and identified incorrect fonts and weights; further tweaking remained.
Did the prototype match the typography?
No. The author identified incorrect fonts and weights, while describing the layout, colors and hover states as promising.
More details
About this account
Cursor retrieved Figma design context through MCP and generated HTML/CSS matching layout, colors and hover states with incorrect typography.
Firsthand account opened and read. Outcome is source-reported, not independently reproduced. Suggested prompt written by Agents In Use. Typography remained incorrect and further manual tweaking was needed.
Credit: Phil Sayer
Source published 5 Aug 2025
Source checked 15 Oct 2026
Tools and topics
Figma MCP · HTML · CSS · GitHub
Figma MCP · HTML · CSS
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.