design-handoff
Skill43 starsChanged 23 days agoMITView on GitHub
Turn a finished job into what an engineer needs: tokens, redline specs, component API docs and the asset list. Use after a job is signed off and someone else will build it in the product.
16 other projects use a version of this.
Adopted by
Most recently taken up by
- nisarth/claude-skills-storetheir own version, first seen Nov 8, 2026
- dmlguq456/heartingtheir own version, first seen Nov 8, 2026
- philipobenito/elelemtheir own version, first seen Oct 28, 2026
- toribryan/design-skillstheir own version, first seen Oct 25, 2026
- vindreshsingh/engineering-skillstheir own version, first seen Oct 20, 2026
- Geruyang/skillstheir own version, first seen Oct 15, 2026
Used with
Projects with it also use frontend-design.
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.
BlockSkillfrontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Also in 3 projects that use this
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- anthropics/knowledge-work-plugins★ 35ksame name
- dmlguq456/hearting★ 9same name
- shayan-m81/layerwright★ 8same name
- syntropic137/syntropic137★ 5same name
- philipobenito/elelem★ 3same name
- Geruyang/skills★ 2same name
- humbleteam/design-handoff★ 1same name
- Jaxton07/jax-skills★ 1same name
- nisarth/claude-skills-store★ 1same name
- toribryan/design-skills★ 1same name
6 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository25 other files it gives its agents.
- adapters/agents.mdAGENTS.md
- accessibility-auditSkill
- brand-kitSkill
- chart-designSkill
- dashboard-layoutSkill
- dashboardSkill
- design-critiqueSkill
- design-qaSkill
- design-reviewSkill
- designSkill
- design-systemSkill
- design-templateSkill
- studioSkill
- email-campaignSkill
- email-templateSkill
- helpSkill
- initSkill
- motion-designSkill
- presentation-designSkill
- social-campaignSkill
- social-contentSkill
- statusSkill
- tasteSkill
- variantsSkill
- videoSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 14 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 7
Write a handoff as the Design Manager.
- Very specific: line 34
Run: Read ${CLAUDE_PLUGIN_ROOT}/skills/desk/SKILL.md now and follow it from step 0 to step 7 as the Design Manager with the desks above.
“Common” is measured: kept by at least 6 in 10 of the 14 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.
Files
Write a handoff as the Design Manager.
Deliverable and standard. A handoff pack from a signed-off deliverable. Non-visual, so the copy standard applies to the documents, the brand-kit standard's front matter shape to the tokens, and the source deliverable's own standard to the specs. Nothing is redesigned here: the pack describes what was signed off.
Desks.
| Desk | Agent | Tier | Does |
| Design System Lead | desk:design-system-lead | senior | the tokens used by the file, named, diffed against .desk/DESIGN.md, new ones flagged |
| Design Engineer | desk:design-engineer | builder | the component breakdown, props and states, the specs with measurements, the framework notes |
| Content Designer | desk:content-designer | builder | the docs read as a developer would: plain, in order, nothing assumed |
| Copy Editor | desk:copy-editor | senior | one pass on every document |
| Creative Director | desk:creative-director | director | sign-off on the pack against the source renders: does it describe what was approved |
Inputs. A job id under .desk/jobs/ (the pack reads its state.json, brief and final.html), or a path to any signed-off final.html with its brand file. A job that is under the bar is refused with the reason: hand off finished work only.
Proof sizes. None new. The source job's renders are reused, and specs.html renders at desktop for a visual check.
Output under .desk/out/<id>/:
tokens.jsonandtokens.css: every token the file uses, by job, with values, and anewlist for anything not in.desk/DESIGN.md.specs.md: per component or region: size at each breakpoint, spacing, type, colour tokens, states, motion, with the measurements from the file, not estimated from the render.specs.html: the signed-off render with redlines drawn over it as SVG, toggled with[data-redlines].components.md: component list, props with types and defaults, states, slots, events, accessibility notes, in the--frameworkidiom (default fromproject.json, else plain HTML and CSS).assets/: every SVG and image from the file as separate files with their names and sizes inassets.md.README.md: how to use the pack, in ten lines.
Run. Read ${CLAUDE_PLUGIN_ROOT}/skills/desk/SKILL.md now and follow it from step 0 to step 7 as the Design Manager with the desks above. Command name for state and events: design-handoff. Changes to the loop for this command:
- Skip roughs and the pick. Phase order: intake (read the source job), extract (Design System Lead and Design Engineer in parallel), write (Content Designer), edit (Copy Editor), sign-off, handback.
- Sign-off is the non-visual kind: the Creative Director checks the pack against the source renders and scores copy, hierarchy and brand fit, with the other axes n/a. Notes go to the desk that owns the file.
- Proof runs only on
specs.htmlatdesktop, screenshots only.
The ask: $ARGUMENTS
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
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.