Pinned publisher workflow: https://github.com/anthropics/knowledge-work-plugins/blob/33eeda1e8fd856455b05479d13a0f85b5f803744/design/skills/design-handoff/SKILL.md

Use the complete design-handoff source workflow for this specific task: prepare a design handoff for developers.

Context: [audience, actual country/jurisdiction where relevant, period, currency and authorised scope].
Available material: The accepted design, states, interaction rules and implementation constraints.
Available tools: [name only tools that are actually connected and authorised].

First check the full publisher instructions and supporting references. Identify missing prerequisites before proceeding. Use the source sections relevant to this scope:
1. What to Include
2. Visual Specifications
3. Interaction Specifications
4. Principles
5. Handoff Spec: [Feature/Screen Name]

Requested handover: A developer handoff describing components, behaviour, assets and unresolved decisions.
Task-specific review: Identify missing states and responsive behaviour before calling a handoff complete.

Use only the authorised evidence. Separate facts, assumptions and unresolved questions; do not invent results, references or access. Return the supported preparation or review in this conversation. Do not send, publish, lodge, pay, delete, change external records or save shared artifacts without separate approval of the exact action. If execution or access is unavailable, provide the bounded plan and state what has not been done.

Review: Confirm asset rights, accessibility, usage permissions and any paid generation costs. Review output quality before publishing.
Source: https://github.com/anthropics/knowledge-work-plugins/blob/33eeda1e8fd856455b05479d13a0f85b5f803744/design/skills/design-handoff/SKILL.md
Source inspected 2026-10-18. Not run-tested.