---
title: "Coral · Drew Minns"
description: "One format for a component, wherever it was made. Open a Figma design as HTML, edit it in code, send it back to Figma. AI has since changed the problem, so Coral is parked, but the idea of one shared source still drives my systems work."
url: https://designeng2026.vercel.app/work/coral/
---

Case 04 · Design to code

# Coral

One format for a component, wherever it was made. Open a Figma design as HTML, edit it in code, send it back to Figma. AI has since changed the problem, so Coral is parked, but the idea of one shared source still drives my systems work.

Role: Design and engineering

Year: 2025

Built with: TypeScript, Zod, a CLI, a Figma plugin

Link: coralui.com ↗

![The Coral UI plugin open in Figma, showing a component as a Coral file](https://designeng2026.vercel.app/work/coral/cover.jpg)

## 01\. The problem

Design and code drift apart.

When design and code are two separate sources of truth, every change becomes two tickets and two reviews, and a QA pass to catch where they disagree. When the tools or frameworks change, the system gets rebuilt.

Most teams accept that as normal. I think it's a structural problem.

1.  Two sources of truth: Every change is made twice.
2.  Tool lock-in: Change a tool or framework and the system is rebuilt.
3.  Translation: Specs get interpreted, and consistency lives in people's heads.

## 02\. Where it started

Superfun, a Figma plugin.

In 2021, before Figma had Dev Mode or Code Connect, I built [Superfun](https://www.superfun.design/). It read a selected frame through Figma's API and wrote it out as React, Vue, Svelte or HTML, with styles as CSS or Tailwind.

The part that mattered was the middle. Superfun turned a design into one neutral description first, and wrote every framework from that. Figma has since built most of this in, but the idea stayed with me: put a shared description between design and code, and the gap gets small enough to automate.

![Superfun generating React code in Figma](https://designeng2026.vercel.app/_astro/react.Bi4-zWHy_2uPv9T.webp)

Superfun generating React from a selected frame.

## 03\. The idea

A component, described as data.

Coral is that description, made into a standard. A component's structure, styles, variants, props, events and tokens live in one JSON file. Figma, React, HTML and Vue are just different ways to read and write it.

```json
{
  "name": "Button",
  "elementType": "button",
  "componentVariants": {
    "axes": [
      { "name": "intent",
        "values": ["primary", "secondary"] },
      { "name": "size",
        "values": ["sm", "md", "lg"] }
    ]
  },
  "props": {
    "label": { "type": "string", "required": true }
  },
  "textContent": { "$prop": "label" }
}
```

![The Coral UI plugin in Figma](https://designeng2026.vercel.app/_astro/figma.CbqKdvEm_Z3ohcy.webp)

The Coral plugin in Figma.

## 04\. Watch it work

From code to Figma and back.

In this walkthrough I import a component from code, look at the spec Coral makes from it, bring it into Figma, and sync a change back.

A four-minute walkthrough, with sound.

## 05\. Where it is

Open source, in beta.

Coral is a set of small open-source packages: the core spec and CLI, generators for React and HTML, a React parser, and converters between CSS and Tailwind. The [docs](https://docs.coralui.com/) and [code](https://github.com/reallygoodwork/coral) are public.

![The Coral UI playground](https://designeng2026.vercel.app/_astro/playground.D62Bzpu-_1YuOQh.webp)

The Coral playground.

-   [Next · Case 01 — Ramp Creative](https://designeng2026.vercel.app/work/ramp-creative/)
-   [Everything — All work](https://designeng2026.vercel.app/work/)
