design-restore

스타8

포크0

업데이트2026년 5월 27일 12:05

Use when restoring/reconstructing a design image (concept art, screenshot, mockup, Figma export) into a clean, modular, HAND-EDITABLE HTML page. Produces Open-Design-editable HTML and verifies visual fidelity against the target image with the design-ruler CLI, iterating until the render matches.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

출처

Fzhiyu1

Fzhiyu1/design-ruler

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Design Restore — image → editable HTML

You turn a target design image into a single self-contained HTML file that (1) is a real responsive mobile page visually matching the image, (2) scrolls and adapts like a normal app screen, and (3) stays cleanly editable by a human afterward (in Open Design or any editor). You verify fidelity with the design-ruler CLI and iterate until the render matches the target.

design-ruler only measures runtime rendering — it does not generate or judge. You are the diff engine: you write the HTML, render it, compare against the target, decide the fix, and re-measure.

When to use

The user gives a design image (concept art / screenshot / mockup / Figma export) and wants editable HTML that reproduces it.

Output contract — the HTML you write MUST follow ALL of these

One standalone HTML file. All CSS in a single <style> block. No external deps, no build step. It must open directly via file://.
Real responsive mobile page, mobile-first — NOT a fixed canvas. Use <meta name="viewport" content="width=device-width, initial-scale=1">. Wrap the whole UI in a root container <div data-od-id="app-root" data-od-label="App root"> styled max-width: 430px; margin: 0 auto;, and lay it out fluidly inside (%, flex/grid, rem). The target image is a hi-res mockup (≈2–3× a real phone) — reproduce its proportions and layout, do NOT copy its pixel count as your CSS size, and do NOT lock the viewport to the image width (width=1024 etc. is wrong).
Natural vertical scroll. Do NOT put overflow: hidden on <body> or the root — the page must scroll like a normal mobile page. Avoid position: absolute for layout (use it only for genuinely-overlapping bits like a badge); build with normal flow + flex/grid so it adapts and a human can restyle it.
Expose modules. Every meaningful block carries:
- data-od-id="<stable-kebab-id>" — stable, unique (e.g. hero-banner, product-card-cat)
- data-od-label="<human name>" — shows in editors' layer lists (e.g. Hero banner, Product card · cat)
- These are protected — never strip them in later edits.
Token-driven styling. Define theme values as CSS variables on :root (colors, spacing, radius, font sizes) and reuse them. This makes global tweaks possible.
Editable text in leaf nodes. Put text in leaf elements (<span>, <p>), not buried in containers that also hold children — editing a container's text would collapse its children.
Real modular structure, NOT a flattened image. Do NOT <img src="target.png"> the whole thing. Reconstruct actual elements (status bar, search, categories, hero, grid cards, nav…). Editability is the whole point — a pixel-perfect flattened copy is a failure.

Workflow

Study the image. Look at it. Identify the modules, layout, colors, type scale, spacing.
Write the HTML following the output contract. Save it (e.g. restore.html) with an absolute path.
Render the phone column (non-interactive). Screenshot the app-root element — because it's max-width:430px centered, this captures the mobile layout at phone width regardless of the headless browser's viewport:
```
design-ruler screenshot --url "file:///ABS/PATH/restore.html" --selector "[data-od-id='app-root']" --output render.png
```
render.png is your current result, at phone width.
Compare to the target. Two ways, use both:
- Look at render.png next to the target image — you have vision; judge layout, color, hierarchy directly.
- Ghost overlay (target tinted magenta over your render, non-interactive). Overlay screenshots the app-root element and resizes the target to match it — so the hi-res mockup is scaled to your phone-width column automatically (you do NOT need matching pixel counts):
```
design-ruler overlay --design /ABS/PATH/target.png --url "file:///ABS/PATH/restore.html" --selector "[data-od-id='app-root']" --output ghost.png
```
  Open ghost.png: where magenta ghosts out of alignment → that block is off (proportions/spacing/order); where it blends → aligned. (Always pass --selector + --output so it runs headless and does not open a browser.)
Measure exact values when a block is off:
```
design-ruler measure --url "file:///ABS/PATH/restore.html" --selector "[data-od-id='hero-banner']"
```
Returns the rendered bbox {x,y,width,height} + computed CSS as JSON. Compare against what the image implies, then fix the CSS.
Iterate steps 3–5. Fix the worst misalignments first. Re-render, re-compare, until the ghost is clean and the render reads like the target.

Rules of thumb

It's an app screen, not a screenshot. Design at phone logical width (~390–430px), let it scroll, make it adapt. A fixed width=1024 non-scrolling canvas is the #1 failure mode — it looks fine in a 1:1 overlay but breaks in any real phone viewport.
Reconstruct structure even when it costs a few pixels of fidelity — editability > pixel-perfection.
The image's text may be decorative or garbled; write real, legible copy in your HTML.
Prefer flex/grid layout + the CSS variables over hard-coded absolute positions, so a human can restyle later.
Don't stop at "looks roughly right" — use measure to confirm key blocks are proportioned/ordered like the target.

이 저장소의 다른 Skills

같은 저장소

design-restore-overview

Fzhiyu1/design-ruler

Use when you have a design image (an AI-generated concept render, a screenshot, or a mockup) and want to reproduce it as clean, hand-editable code with real assets, and you need the overall plan before picking a tool. The entry point that orients the whole image-to-code restore mode and routes you to the right sub-skill for each stage. Triggers include "还原设计图", "把设计图变成代码", restore a design image to HTML, image2 concept to editable webpage, design-to-code with real icons and photos.

2026-06-048

extract-assets

Fzhiyu1/design-ruler

Use after design-restore has produced editable HTML for a design image, when you need to fill its placeholder image slots with real assets — fetch icons as ready-made SVGs from Iconify (by recognizing what each icon is) and crop real photos/backgrounds out of the design image. Does NOT redraw or trace anything.

2026-05-288

name	design-restore
description	Use when restoring/reconstructing a design image (concept art, screenshot, mockup, Figma export) into a clean, modular, HAND-EDITABLE HTML page. Produces Open-Design-editable HTML and verifies visual fidelity against the target image with the design-ruler CLI, iterating until the render matches.

Design Restore — image → editable HTML

When to use

The user gives a design image (concept art / screenshot / mockup / Figma export) and wants editable HTML that reproduces it.

Output contract — the HTML you write MUST follow ALL of these

One standalone HTML file. All CSS in a single <style> block. No external deps, no build step. It must open directly via file://.
Real responsive mobile page, mobile-first — NOT a fixed canvas. Use <meta name="viewport" content="width=device-width, initial-scale=1">. Wrap the whole UI in a root container <div data-od-id="app-root" data-od-label="App root"> styled max-width: 430px; margin: 0 auto;, and lay it out fluidly inside (%, flex/grid, rem). The target image is a hi-res mockup (≈2–3× a real phone) — reproduce its proportions and layout, do NOT copy its pixel count as your CSS size, and do NOT lock the viewport to the image width (width=1024 etc. is wrong).
Natural vertical scroll. Do NOT put overflow: hidden on <body> or the root — the page must scroll like a normal mobile page. Avoid position: absolute for layout (use it only for genuinely-overlapping bits like a badge); build with normal flow + flex/grid so it adapts and a human can restyle it.
Expose modules. Every meaningful block carries:
- data-od-id="<stable-kebab-id>" — stable, unique (e.g. hero-banner, product-card-cat)
- data-od-label="<human name>" — shows in editors' layer lists (e.g. Hero banner, Product card · cat)
- These are protected — never strip them in later edits.
Token-driven styling. Define theme values as CSS variables on :root (colors, spacing, radius, font sizes) and reuse them. This makes global tweaks possible.
Editable text in leaf nodes. Put text in leaf elements (<span>, <p>), not buried in containers that also hold children — editing a container's text would collapse its children.
Real modular structure, NOT a flattened image. Do NOT <img src="target.png"> the whole thing. Reconstruct actual elements (status bar, search, categories, hero, grid cards, nav…). Editability is the whole point — a pixel-perfect flattened copy is a failure.

Workflow

Study the image. Look at it. Identify the modules, layout, colors, type scale, spacing.
Write the HTML following the output contract. Save it (e.g. restore.html) with an absolute path.
Render the phone column (non-interactive). Screenshot the app-root element — because it's max-width:430px centered, this captures the mobile layout at phone width regardless of the headless browser's viewport:
```
design-ruler screenshot --url "file:///ABS/PATH/restore.html" --selector "[data-od-id='app-root']" --output render.png
```
render.png is your current result, at phone width.
Compare to the target. Two ways, use both:
- Look at render.png next to the target image — you have vision; judge layout, color, hierarchy directly.
- Ghost overlay (target tinted magenta over your render, non-interactive). Overlay screenshots the app-root element and resizes the target to match it — so the hi-res mockup is scaled to your phone-width column automatically (you do NOT need matching pixel counts):
```
design-ruler overlay --design /ABS/PATH/target.png --url "file:///ABS/PATH/restore.html" --selector "[data-od-id='app-root']" --output ghost.png
```
  Open ghost.png: where magenta ghosts out of alignment → that block is off (proportions/spacing/order); where it blends → aligned. (Always pass --selector + --output so it runs headless and does not open a browser.)
Measure exact values when a block is off:
```
design-ruler measure --url "file:///ABS/PATH/restore.html" --selector "[data-od-id='hero-banner']"
```
Returns the rendered bbox {x,y,width,height} + computed CSS as JSON. Compare against what the image implies, then fix the CSS.
Iterate steps 3–5. Fix the worst misalignments first. Re-render, re-compare, until the ghost is clean and the render reads like the target.

Rules of thumb

It's an app screen, not a screenshot. Design at phone logical width (~390–430px), let it scroll, make it adapt. A fixed width=1024 non-scrolling canvas is the #1 failure mode — it looks fine in a 1:1 overlay but breaks in any real phone viewport.
Reconstruct structure even when it costs a few pixels of fidelity — editability > pixel-perfection.
The image's text may be decorative or garbled; write real, legible copy in your HTML.
Prefer flex/grid layout + the CSS variables over hard-coded absolute positions, so a human can restyle later.
Don't stop at "looks roughly right" — use measure to confirm key blocks are proportioned/ordered like the target.