← ClaudeAtlas

image-to-codelisted

Turn a reference image, screenshot, or mockup into token-driven, accessible code — infer the design system from the reference (palette, type scale, spacing, radius, layout archetype), map it to the 3-tier tokens, rebuild it, then verify with the kit's gates. Use when the user provides a design/screenshot and wants matching UI code.
plugin87/ux-ui-agent-skills · ★ 214 · Web & Frontend · score 79
Install: claude install-skill plugin87/ux-ui-agent-skills
# Skill: Image to Code Reconstruct a design from a visual reference as a real design system, not a one-off copy. Match the *system* (color/type/spacing language), never lift copyrighted imagery or brand assets. ## Steps 1. **Read the reference like a designer.** Infer and write down: - **Palette** — 1 dominant surface family, text colors, 1 primary action + at most 1 accent (sample the hues; don't guess random hex). - **Type** — family feel (geometric/grotesk/serif), the scale jumps, display vs. body contrast, weights. - **Spacing & density** — base unit, section rhythm, card padding; airy vs. compact. - **Radius & depth** — radius language (sharp/soft/pill), shadow vs. hairline separation. - **Layout archetype + sequence** — full-bleed hero / asymmetric split / bento / editorial stack (`taste/design-taste.md` → Variance Mandate). 2. **Anchor to a known system** if it's close — browse `taste/aesthetic-systems.md` / `python3 scripts/design_systems.py search <term>` and adopt that recipe to stabilize decisions. 3. **Build the token theme** from the inferred values → 3-tier DTCG (`design-tokens` skill); generate a single `theme.css`. Verify every color pair with `scripts/contrast.py` / `scripts/validate_contrast.py` (light + dark) — a sampled brand color that fails AA gets adjusted; taste never overrides POUR. 4. **Rebuild layout + components** token-driven via `frameworks/adapter-protocol.md` + `components/*`: one shared primitive layer, all 8 states, a11y wire