ui-from-reference
/ui-from-reference
Build or reshape a page or section in code from a reference (Figma frame, screenshot, annotated wireframe) with exact structure, clean alignment and a mandatory screenshot check with Playwright. Use when the user attaches a reference or says "fă-l ca aici", "make it look like this", "aliniază", "curăță layout-ul", "din Figma în cod", or changes a section visually.
- Author
- UncleBenisimo ↗
- Repository
- claude-kit-designeri ↗
- Licence
- MIT
- Last repository change
- 04.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 04.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Build or reshape a page or section in code from a reference (Figma frame, screenshot, annotated wireframe) with exact structure, clean alignment and a mandatory screenshot check with Playwright. Use when the user attaches a reference or says "fă-l ca aici", "make it look like this", "aliniază", "curăță layout-ul", "din Figma în cod", or changes a section visually.
Triggers from the description
Original author description
Build or reshape a page or section in code from a reference (Figma frame, screenshot, annotated wireframe) with exact structure, clean alignment and a mandatory screenshot check with Playwright. Use when the user attaches a reference or says "fă-l ca aici", "make it look like this", "aliniază", "curăță layout-ul", "din Figma în cod", or changes a section visually.
How it works
- 1. Read the reference before touching code
- 2. Map to existing components
- 3. Layout system
- 4. Visual verification with Playwright (mandatory)
- 5. Final checklist
- 6. Report (in the user's language, simple)
SKILL.md preview
---
name: ui-from-reference
description: Build or reshape a page or section in code from a reference (Figma frame, screenshot, annotated wireframe) with exact structure, clean alignment and a mandatory screenshot check with Playwright. Use when the user attaches a reference or says "fă-l ca aici", "make it look like this", "aliniază", "curăță layout-ul", "din Figma în cod", or changes a section visually.
---
# UI from reference
A visual task is not done until it has been seen. This skill turns a reference into code and proves the result with screenshots.
Project rules in CLAUDE.md always win over anything here.
## 1. Read the reference before touching code
Write a short inventory for the user, in their language, and keep it in the plan:
1. Sections top to bottom, each with: layout (columns + approximate ratio), background, elements in order.
2. **Crossed out / X-marked = removed.** List every removed element so nothing slips back in.
3. Ambiguities (two plausible readings) → ask one precise question instead of guessing.
4. Anything that needs new content fields or a new dependency → ask before adding it.
Estimate proportions from the image ("text ≈ 45%, image ≈ 55%") and map them to the grid, not to pixel values.
For a Figma link: read the design once with the Figma MCP (structure + variables), take one screenshot, and do not re-read per element.
## 2. Map to existing components
- Search the project's components first. Reuse, then extend with a prop, and only then create a new component.
- One pattern = one component. If two sections look the same in the reference, they render through the same component.
- Only design tokens (CSS variables) for colour, spacing, radius and type. No magic numbers: a value needed twice is a token.
## 3. Layout system
- **One container, one grid.** Every section shares the same max-width and inline padding; left and right edges line up across the page.
- Vertical rhythm: the same spacing token between sections; spacing between sections belongs to the section wrapper only, components have no outer margin.
- Image + text pairs are vertically centred. Buttons in a row have the same height and a fixed gap.
- One `h1` per page, section titles `h2`; paragraphs around 60–70 characters wide.
- Mobile-first: one column at small widths, no horizontal scroll at 320 px, body text at least 16 px, touch targets at least 44 px.
- Reserve image space with `aspect-ratio` so the layout does not jump while images load.
- Flat selectors, no `!important`.
## 4. Visual verification with Playwright (mandatory)
1. Start the dev server once (and stop it at the end).
2. With the Playwright MCP, open the page and take full-page screenshots at **1440, 1024 and 390 px**. Also check for horizontal overflow at each width.
3. Compare section by section with the reference. Write a diff list: order, missing or extra elements, edge alignment, column ratios, vertical centring, spacing rhythm, button alignment.
4. Fix, screenshot again. **Max 3 rounds**, then report what still differs and why.
5. Do not commit screenshots.
If screenshots are not possible (no browser, blocked download), say so plainly, keep the code change, and give the user a short checklist to verify by eye at the three widths. Never claim a visual task is finished without screenshots or the user's confirmation.
## 5. Final checklist
- [ ] Every removed element from the inventory is gone.
- [ ] Left/right edges identical in every section.
- [ ] Repeated patterns render through one component each.
- [ ] Only tokens; no hardcoded colours or spacing.
- [ ] Focus visible on every link and button.
- [ ] No horizontal scroll at 390 and 320 px.
## 6. Report (in the user's language, simple)
1. What changed, per section (one line each).
2. What differs from the reference on purpose, and why.
3. Open questions (max 3).
4. Screenshot paths, or the manual checklist.
Versions
The database has no other skills named ui-from-reference.
Database snapshot: 13.11.2026 · package version 2317ed813328 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100flutter-ui-from-design
Use when implementing responsive Flutter UI from a screenshot, mockup, Figma frame, or visual reference. Triggers on "build this UI", "implement this design", "match this screenshot", or "responsive Flutter UI". - 86build-from-reference
Use when a screenshot, mockup or design image is the source for a page or component, or when asked to match or copy a look. - 100ui-check
Execute ui-check: steps in test specs — compare the live page currently open in the browser under test against a declared design baseline: a Figma frame (identifier only; file + token configured once per project) or a screenshot image, in exact mode (every visible detail) or… - 100page-build
Build a page end to end as HTML, push it to Figma as one frame per section, and publish an HTML preview. Use when the user asks to build or start a page or a section, "push to Figma", or "build the preview". - 100figma-design-extract
Extract exact design values from a Figma node into a build-ready spec table, instead of eyeballing a screenshot. Use when the user shares a figma.com node URL, or says "implement this Figma design", "build this component from Figma", "extract the Figma values", or "match the… - 100figma-generate-design
Use this skill alongside figma-use when the task involves translating an application page, view, or multi-section layout into Figma. Triggers: 'write to Figma', 'create in Figma from code', 'push page to Figma', 'take this app/page and build it in Figma', 'create a screen',…