PromptVisual design

Design Handoff Documentation

Create comprehensive design handoff documents with specs, assets, and implementation details for developers.

Actions

Tags

handoffdocumentationspecificationdevelopmentdesign-system

Prompt

Create a design handoff document for [feature/component name].

Design Context:
- Feature/component: [name]
- Design files: [links]
- Key screens/components: [list]

Provide:

1. Overview
   - Feature/component purpose
   - User goals it supports
   - Key interactions
   - Design files and links

2. Visual Specifications
   For each screen/component:
   - Dimensions and spacing
   - Colors (hex codes, usage)
   - Typography (fonts, sizes, weights)
   - Icons and imagery
   - Border radius, shadows, effects

3. Component States
   - Default state
   - Hover state
   - Active/focus state
   - Disabled state
   - Loading state
   - Error state
   - Empty state

4. Interactive Behaviors
   - Click/tap interactions
   - Hover effects
   - Animations and transitions
   - Responsive behavior
   - Breakpoint changes

5. Content Requirements
   - Copy and microcopy
   - Character limits
   - Placeholder text
   - Error messages
   - Success messages

6. Technical Specifications
   - Component structure
   - Props/parameters needed
   - Events/callbacks
   - API requirements
   - Data structure

7. Responsive Design
   - Mobile specifications
   - Tablet specifications
   - Desktop specifications
   - Breakpoints and behavior

8. Accessibility Requirements
   - Keyboard navigation
   - Screen reader support
   - ARIA labels
   - Color contrast
   - Focus indicators

9. Assets & Resources
   - Design file links
   - Asset exports needed
   - Font files
   - Icon libraries
   - Image assets

10. Edge Cases
    - Error scenarios
    - Empty states
    - Loading states
    - Offline behavior
    - Validation failures

Format as a comprehensive handoff document ready for development.

How to use

  1. 1Replace [feature/component name], [name], [links], and [list] with your specific details
  2. 2Prepare your design files: Collect Figma links, screenshots, or design descriptions
  3. 3Add context before the prompt: Describe the feature/component. Example: "Feature: User Profile Update. Design files: [Figma links]. Key screens: Profile edit form, Save confirmation."
  4. 4If you have design system: Mention your design system. Say "Design system: Material Design 3" or "Design system: [paste link]"
  5. 5If you have technical requirements: Paste API requirements or technical constraints. Say "API requirements: [paste requirements]"
  6. 6Paste the modified prompt into your preferred AI tool, like ChatGPT or Claude
  7. 7Review the handoff document: Check all sections (visual specs, component states, technical specs, accessibility)
  8. 8Ask for specifics: Request "Expand accessibility requirements" or "Add more edge cases" or "Detail responsive breakpoints"
  9. 9Export to your tool: Copy the handoff document to Notion, Confluence, or your developer handoff platform
  10. 10Share with developers: Use the handoff document to ensure developers have all information needed for implementation

Pro Tips

  • Include design file links: Paste Figma links or design descriptions so AI can reference actual designs
  • Specify component states: Mention all states (default, hover, active, disabled, loading, error) so AI includes them
  • For complex components: Break down complex components into smaller sections: "Create handoff for Button component only"
  • Request platform-specific: Ask "Include React-specific technical specs" or "Include Web component specs" if needed
  • Save as template: Reuse the handoff structure for future design handoffs

New prompts & templates by email

Weekly copy-paste prompts, pattern notes, and AI UX resources on Substack - no spam, unsubscribe anytime.

Subscribe on Substack