dragoon0x/everything-design-taste

design-handoff

Design-to-development handoff workflows, spec tooling, and developer-designer collaboration.

First seen Jul 18, 2026

Installation

$ npx skills add dragoon0x/everything-design-taste --skill design-handoff

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from dragoon0x/everything-design-taste · top by installs.

npx skills add dragoon0x/everything-design-taste

Browse all from dragoon0x/everything-design-taste

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 11
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,415 B
  • docs SUMMARY.md 114 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

Design Handoff

Handoff Checklist

What Developers Need

  • All states designed (default, hover, focus, disabled, loading, error, empty)
  • Responsive behavior specified (mobile, tablet, desktop)
  • Spacing values (use tokens, not arbitrary pixel values)
  • Typography specs (font, size, weight, line-height, color)
  • Color values (token names preferred over hex)
  • Animation specs (duration, easing, properties)
  • Edge cases (long text, no data, many items, error recovery)
  • Accessibility notes (focus order, ARIA labels, keyboard behavior)

What Developers Don't Need

  • Pixel-perfect mockups of every possible state combination.
  • Detailed redlines (modern tools provide inspection).
  • A 50-page spec document nobody will read.

Collaboration Model

  1. Include developers early. Feasibility check during design, not after.
  2. Pair on complex interactions. Sometimes building together is faster than specifying.
  3. Design review in browser. Final QA in the actual implementation, not in Figma.
  4. Shared language. Use design system token names in conversation.
  5. Fast feedback loops. Small PRs, quick design reviews, iterate.