Launching today
Paper design: MCP and Desktop
The design canvas your agents can edit
3 followers
The design canvas your agents can edit
3 followers
Design tools and codebases live in parallel universes. You design in Figma, export, translate, and watch it drift from production within a week. Paper is a design canvas built on HTML/CSS, so Cursor, Claude Code, and Codex can read and write to it natively. Push from your codebase. Pull real data. No translation layer, no format lock-in. Your agents handle the boilerplate. You focus on the call only you can make.
Design tools have always had one dirty secret: the design file and the production code are never actually the same thing.
You design in Figma. You hand it off. A developer interprets it. It drifts. You redesign. The cycle repeats.
Every tool in the stack is speaking a slightly different language, and you spend enormous energy in translation.
Paper bets that this whole translation layer shouldn't exist.
The core insight is deceptively simple: HTML and CSS are already a design language. Every browser renders them. Every agent already speaks them.
So instead of inventing a proprietary format and building an export pipeline on top of it, Paper just builds the canvas on web standards directly.
What that unlocks in practice:
Agents can read and write the canvas natively. Point Cursor, Claude Code, or Codex at Paper and they know exactly what they're working with. No glue code, no prompt gymnastics to explain your format.
Push/pull from your codebase. Design tokens, components, styles stay in sync instead of becoming a static mockup that drifts from production within days.
Real data on the canvas. Pull from your CMS, database, or any API. No more designing with lorem ipsum and being surprised when real content breaks the layout.
Agents handle the boilerplate. Responsive variants, consistency checks, style repetitions. You focus on the decisions that actually require taste.
This is for the team that's already deep in an agent-assisted workflow.
If you're using Cursor or Claude Code daily, you've probably felt the friction of jumping between your IDE and a separate design tool with no real connection between them.
Paper closes that loop.
The timing matters too. AI coding agents are moving from "generate a component" to "manage a full design system."
The tools they work with need to be built for that reality, not retrofitted to it. Paper is native to that world.
I'm genuinely curious how teams are thinking about the design-to-code handoff as agents get more capable.
Are you still maintaining a Figma file alongside your codebase?