Skip to content
Back to skills

Implement Design From Export

ASecurity

Use when the user hands off a design export, HTML/CSS, or screenshot from an AI design tool and asks to build or match it in the project.

  • 6 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 27, 2026
ai-agentsapi

Works with

  • api

Security analysis

A100/100

Scanned September 27, 2026

npx -y skills add xrhstosmour/macsify --skill implement-design-from-export --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Implement Design From Export?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Implement Design From Export
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/xrhstosmour-implement-design-from-export/badge)](https://www.skillsdirectory.com/skills/xrhstosmour-implement-design-from-export)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: implement-design-from-export
description: Use when the user hands off a design export, HTML/CSS, or screenshot from an AI design tool and asks to build or match it in the project.
---

# Implement Design from Export

## When to use

- User pastes/attaches a design export, HTML/CSS or screenshot, and asks to build matching UI.
- User saved a design export to a file and asks you to build from it.
- Not for writing a new design prompt before design, see the `craft-design-prompt` skill for that.

The user designs in an AI design tool themselves, then hands the result to the agent one of these ways:

- Pastes the exported HTML/CSS directly into the chat.
- Saves the exported HTML to a file in the repo and tells the agent which path to read.
- Attaches/pastes a screenshot of the design and asks the agent to build UI to match it visually.

Do not ask the user to authenticate, generate an API key, or set up any credential for this, there's nothing to configure.

Design exports are static layouts. Hover states, animations, validation, and state management are not part of the export and need to be implemented separately.

When implementing those missing states, apply the `web-app-design` skill's motion framework, frequency gate, easing, duration budgets, origin-aware popovers, rather than inventing ad hoc timings.

Exports often hand-roll dropdowns, modals, toasts, or tooltips as plain styled `div`s. Before wiring these up, check whether the project already has a primitive for it, see `web-app-design`'s native → primitive → hand-roll ladder, and use that instead of keeping the exported markup as the real implementation.

Before calling the implementation done, exercise every interactive element the export implies, hover, focus, open/close, since a static export can't show whether those states were considered.

Design tool exports often use `Tailwind` utility classes by default. If the project doesn't already use `Tailwind`, translate the export to the project's actual styling approach, don't introduce `Tailwind` as a new dependency just because the pasted HTML happens to use it.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.