cmp-design-to-codelisted
Install: claude install-skill whinstudio/skills
# Design to code
The design is the specification. Read values from it; never eyeball them. Code rules are in
`cmp-code-rules`, screen structure in `cmp-feature`.
## 1. What is in `design/`
Search `design/` recursively; the boards may sit in a subfolder such as `design/project/`.
| File | What it is |
|---|---|
| `*.dc.html` | One board per screen and state. Inline `style` attributes hold exact values: px sizes, hex colours, font family, weight, line height, letter spacing, radius, gaps. |
| `canvas.json` | The board list: file name, title (usually `Screen · state`) and frame size. Use it to pair screens with their states. A board that shows the flow between screens tells you the navigation. |
| a style-guide board | Colour tokens and the type scale, when the design has one. Read it first. |
| `fonts/<family>_<weight>.ttf` | The design's fonts, already downloaded (for example `figtree_600.ttf`). |
| `icons/<id>.xml` | Android vector drawables, drawn black; tint them. License in `icons/LICENSE-icons.txt`. |
| `sounds/` | Sound effects, when the app has them. |
| `artifact-url.txt` | Where the design was published. Do not open it: it needs a login. |
The `<link>` to Google Fonts and `support.js` in the HTML are for the browser; ignore them.
## 2. Extract
- Read every board of the screen you are building, all states included, before writing code.
- Machine-readable values (HTML, CSS, SVG, token files) are exact. Values taken from an image
(a screenshot, a mockup) are est