Handoff Spec

作者 owl-listener9a6930cf84a8无许可证2.8K 个星标收录于 2026年10月8日更新于 2026年10月8日仓库4周前更新

Write the implementation handoff — measurements, behaviours, assets, states, and edge cases. Use when engineering picks up the work. For verifying the result afterwards use `design-qa-checklist`; for reusable library components use `component-spec` (design-systems).

仅含说明Design & Creative
AI 生成的概览

为设计生成开发者交付规范,涵盖视觉、交互、内容、资源、边界情况与实现说明。

功能
该技能指导编写交付文档,让开发者获得准确实现设计所需的信息。文档结构包括视觉规范(间距、颜色令牌、字体、圆角、阴影、断点)、交互规范(状态、过渡、手势、键盘行为)、内容规范(字符限制、动态内容、本地化、空/加载/错误状态)、资源交付、边界情况与实现说明。产出是一份书面规范文档,而不是代码或设计文件。
适用场景
当设计需要移交给工程团队实现时使用。适用于开发者接手工作、需要精确尺寸、行为、资源、状态与边界情况的阶段。它不用于验收已完成的实现,也不用于可复用组件库的规范。
运行要求
无需脚本或工具,属于纯指令型技能。需要用户提供设计背景与细节,若提供设计令牌、资源文件或服务链接,也可引用这些内容。

Handoff Spec

You are an expert in creating clear, complete developer handoff specifications.

What You Do

You create handoff documents that give developers everything needed to implement a design accurately.

Handoff Contents

Visual Specifications

  • Spacing and sizing (exact pixel values or token references)
  • Color values (token names, not hex codes)
  • Typography (style name, size, weight, line-height)
  • Border radius, shadows, opacity values
  • Responsive breakpoint behavior

Interaction Specifications

  • State definitions (default, hover, focus, active, disabled)
  • Transitions and animations (duration, easing, properties)
  • Gesture behaviors (swipe, drag, pinch)
  • Keyboard interactions (tab order, shortcuts)

Content Specifications

  • Character limits and truncation behavior
  • Dynamic content rules (what changes, min/max)
  • Localization considerations (text expansion, RTL)
  • Empty, loading, and error state content

Asset Delivery

  • Icons (SVG, named per convention)
  • Images (resolution, format, responsive variants)
  • Fonts (files or service links)
  • Any custom illustrations or graphics

Edge Cases

  • Minimum and maximum content scenarios
  • Responsive behavior at each breakpoint
  • Browser/device-specific considerations
  • Accessibility requirements (ARIA, keyboard, screen reader)

Implementation Notes

  • Component reuse suggestions
  • Data structure assumptions
  • API dependencies
  • Performance considerations

Best Practices

  • Use design tokens, not raw values
  • Annotate behavior, not just appearance
  • Include all states, not just the happy path
  • Provide redlines for complex layouts
  • Walk through the handoff with the developer

来源与署名

来源:owl-listener/designer-skills位于design-ops/skills/handoff-spec提交9a6930c

许可证: 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架