C✳CODEZ.WIN
🌐 English

Localized reading guide

design-handoffPurpose, usage and source

Generate developer handoff specs from a design. Use when a design is ready for engineering and needs a spec sheet covering layout, design tokens, component props, interaction states, responsive breakpoints, edge cases, and animation details.

Source retrieved:

Source repository
anthropics/knowledge-work-plugins
SKILL.md
design/skills/design-handoff/SKILL.md
Repository stars
34,049
Repository updated
2026-10-30
Categories
Design
Last collected

License: Apache-2.0

Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.

The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.

What this Skill does

Generate developer handoff specs from a design. Use when a design is ready for engineering and needs a spec sheet covering layout, design tokens, component props, interaction states, responsive breakpoints, edge cases, and animation details.

How the upstream workflow works

Usage

Generate handoff specs for: @$1 If a Figma URL is provided, pull the design from Figma. Otherwise, work from the provided description or screenshot.

Upstream passage · L13 ↗

/design-handoff

> If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md. Generate comprehensive developer handoff documentation from a design.

Upstream passage · L7 ↗

Visual Specifications

Exact measurements (padding, margins, widths) Design token references (colors, typography, spacing)

Upstream passage · L25 ↗
Upstream passage · ↗
/design-handoff $ARGUMENTS

Requirements and setup

No short requirements passage was selected from this file. This does not mean the Skill has no dependencies. Check the repository setup instructions and referenced files.

Limits and quality checks

No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.

Start with a safe trial

  1. Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
  2. Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
  3. Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
  4. Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.

Skill format and directory specification ↗

Read further in the source

Translation and scope

This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.

This introduction refers to the pinned version below; current repository activity and collection time are shown separately.

Source retrieved
Source commit
2574e29377c7173d0cecffef29a6ecbd7f8ccb5d
Source SHA-256
38f1efc807928030654218443ad07f6a37ac82de6b4d627a03113a3568d787b7
Back to the full Skill catalog