handoff-to-claude-code
Skill9 starsChanged 6 months agoMITView on GitHub
Developer handoff package
2 other projects use a version of this.
Adopted by
Most recently taken up by
- milanglacier/handoff-to-claude-code-skilltheir own version, first seen Oct 6, 2026
- stritar/skillstheir own version, first seen Sep 11, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- milanglacier/handoff-to-claude-code-skill★ 4same name
- stritar/skills★ 0same name
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 repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- canvas-syncSkill
- cuj-guardianSkill
- frontend-designSkill
- grill-meSkill
- pr-evidenceSkill
- semantic-commitSkill
- ship-taskSkill
- verify-with-playwrightSkill
- animated-videoSkill
- create-design-systemSkill
- design-aesthetic-presetsSkill
- design-critiqueSkill
- design-md-authorSkill
- exportSkill
- frontend-designSkill
- interactive-prototypeSkill
- make-tweakableSkill
- save-as-standalone-htmlSkill
- send-to-canvaSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
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
- Very specific: line 27
Call present_fs_item_for_download to give the user the bundle as a zip.
≈ “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.
Files
Handoff to Claude Code
⚠️ STUB — this is a working theory of the skill body. Replace as the implementation is refined.
What it does
Packages the current design + all its supporting files into a bundle a developer can drop into Claude Code (or any IDE/agent) to implement against.
Working theory of the body (to be replaced)
- Inventory: which HTML files, components, tokens, and assets are part of the deliverable.
- Generate a
HANDOFF.mdat the project root summarizing:- Scope of the design
- Tokens / variables in use
- Component file map
- Known TODOs and open questions
- Suggested implementation order
- Optionally produce a CLAUDE.md tuned for the consuming agent (Claude Code) with project-specific conventions.
- Call
present_fs_item_for_downloadto give the user the bundle as a zip.
TODO
- Replace with the real skill body once captured.
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.