Daisychain / Workflows / figma-make-to-github
Workflow · from drop 007

How to move a Figma Make prototype into a GitHub repo you own

Prototype in Figma Make, push it to GitHub, give it a proper home in your own repo, harden it with a Cursor agent, and ship preview deploys on Vercel. The trick is keeping Make's one-way push from overwriting your work.

The steps, in outline

  1. Get the prototype to a stopping point (Figma Make, 10 min)
  2. Push to GitHub (Figma Make, 5 min)
  3. Create your real repo (GitHub + terminal, 10 min)
  4. Harden it with an agent (Cursor, 40 min)
  5. Connect Vercel (Vercel, 10 min)
  6. Pull later design changes in on purpose (10 min, whenever)

Exact prompts, settings, prices and gotchas are in the full write-up: Drop 007: From a Figma Make prototype to a repo you actually own.

Tools in this chain

FAQ

What does this workflow do?

Prototype in Figma Make, push it to GitHub, give it a proper home in your own repo, harden it with a Cursor agent, and ship preview deploys on Vercel. The trick is keeping Make's one-way push from overwriting your work.

Which tools do I need?

Figma Make, GitHub, Cursor, Vercel. The full drop lists the plan each one needs and its current price.

How much does it cost?

From $20/mo (Figma Professional Full seat, monthly) with GitHub, Cursor and Vercel on free plans. Prices are as listed by each vendor when the drop was last checked.

How long does it take to set up?

About 90 minutes (estimate), longer if the prototype is large.

Who is it for?

Designers who code a little, PMs with a prototype that got popular, and founders who built the demo in Make and now need it to be real.

Has this workflow been tested?

Last verified: Oct 2026 (desk-checked, not run end-to-end). It was checked against each vendor's current documentation and pricing; Daisychain labels drops that have not yet been run end to end, so treat the steps as a careful plan and check them in your own accounts.

Get the next workflow.

One a week, free.