Handoff Spec

owl-listener/designer-skills/design-ops/skills/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 從公開儲存庫中收錄這些內容。

檢舉或申請下架