agentleFS
Sign inStart free
rpraharajrpraharaj/ai-sdlc/skills/map-design-handoff/SKILL.md

map-design-handoff

Skill0 starsChanged 17 days agoMITView on GitHub

Map design frames to existing UI components and list gaps only. Use when the user asks for a design handoff, component map, Figma-to-code map, or /map-design-handoff. Do not invent components. Do not implement.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not invent a design-system component that is not in the repo.

    line 18
  2. Distinctive:

    If you cannot see the frames and the user did not describe them, stop.

    line 33
  3. Distinctive:

    Read AGENTS.md if present.

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Map design handoff

Show what already exists and the gaps. This is not a UI spec (write-ui-spec) and not implementation.

Do not invent a design-system component that is not in the repo.

Is this the right skill?

SignalDo this instead
States and a11y of a screenwrite-ui-spec
Build the screenimplement-change
Visual QA of a built flowverify-ui

Required inputs

  • Named frames (paths, links, or filenames the user provides)
  • The UI tree in this repo (search existing components)

If you cannot see the frames and the user did not describe them, stop.

Human decisions (do not invent)

  • Whether a gap is “build new” vs “change the design to match existing”

Procedure

  1. Read AGENTS.md if present. Search the repo for existing components/patterns before listing a gap.
  2. List each frame → existing component path, or gap.
  3. Find the home: docs/ui/<slug>-handoff.md.
  4. Open references/handoff-template.md. Copy every heading. Write n/a when unused.
  5. Gaps only get a one-line need. Do not design a new system in this file.

Output

  • Path: docs/ui/<slug>-handoff.md
  • Template: references/handoff-template.md

Quality bar

  • Every frame maps to a path or gap
  • Gaps were checked against the repo (say how)
  • No new component invented as if it exists
  • Unused headings are n/a

Done

  1. Path
  2. Mapped count / gap count
  3. Next skill: write-ui-spec for gaps that need states; implement-change for reuse

Download now (ZIP)

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.

Check your setup, free