agentsclimarketplace

Design handoff

Skill Dragoon0x/everything-design-taste/skills/design-handoff

A taste system for AI agents. 288 skills, 80 agents, 12 rules, and 8 hooks that turn generic AI output into work with genuine design quality. Anti-slop detection, typography craft, color systems, brand voice, product strategy, and 50+ specialized reviewers across UI, industry, platform, and content domains.

Install
npx -y skills add Dragoon0x/everything-design-taste --skill design-handoff

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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

SKILL.md

1.4 KB, 273 tokens by cl100k_base, as published. Nobody here has run it

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.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.