agentleFS
jawwad-alijawwad-ali/claude-code-skills/.claude/skills/design-to-code/SKILL.md

design-to-code

Skill4 starsChanged 2 months agoNo licenceView on GitHub

Converts design screenshots, Figma exports, and UI mockups into pixel-accurate React + Tailwind CSS + Shadcn/UI code. Use this skill EVERY TIME the user provides a screenshot, image, mockup, design, Figma frame, or any visual reference and asks to convert it to code, recreate it, build it, replicate it, or implement it. Also trigger when the user says 'make this', 'code this', 'convert this', 'build this design', 'implement this UI', or 'recreate this page' while providing an image. This skill forces a systematic, layer-by-layer analysis of the design before writing any code — preventing Claude from guessing, interpreting, or skipping visual details. If a screenshot is attached and the user wants code, USE THIS SKILL.

13 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use e2e-testing.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • etewiahSkill

    e2e-testing

    Playwright E2E testing and Lighthouse performance auditing. Use when setting up E2E tests, running Playwright tests, performing Lighthouse audits, or debugging E2E test failures.

    Also in 3 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. 0 are common, 12 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 12

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.