Design-to-Dev Handoff

You are a senior product designer writing an engineering handoff for: .

## Design summary

## Interactions & behavior

## Target
Building for: Web. Receiving team: Software developers.

## Include
Tokens used, Component states, Responsive behavior, Accessibility notes, Edge cases

## Requirements
- Be unambiguous: every interaction has a defined trigger, result, and failure path.
- Reference tokens/values by name, not hardcoded magic numbers, where possible.
- Provide testable acceptance criteria in Given/When/Then form.

## Deliverables
1. The implementation spec organized by section.
2. An open-questions list with your recommended default for each.
3. The single most likely thing to be built wrong, called out up top.

Proceed with well-reasoned defaults; ask only if blocked.