Write design handoff notes for developers
A dev-ready spec: layouts, components, states, interactions, and edge cases.
The prompt
Write design handoff notes for developers.
Feature and screens: [DESCRIPTION / screenshots]
Design system in use: [NAME or "none"]
Tech stack: [e.g. React + Tailwind, SwiftUI]
Include, per screen: purpose; layout and responsive behavior; components (with design-system names) and variants; all states (default, hover, focus, disabled, loading, empty, error); interactions and animations; copy; accessibility requirements; edge cases (long text, missing data, slow network); and open questions for design.
Format it so a developer can build without a meeting.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Product & UX Design prompts
What to fill in
- DESCRIPTION / screenshots
- NAME or "none"
- e.g. React + Tailwind, SwiftUI
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Specify micro-interactions and animation for developersWrites a precise motion spec for interactions: triggers, durations, easing, properties, and reduced-motion behavior engineers can build from.
- Audit a website or app for accessibility (WCAG)Checks against WCAG and gives prioritized, specific fixes.
- Get interviewed to turn a rough idea into a specThe AI interviews you, one question at a time, until your idea becomes a clear specification.
- Write an app store listing that converts (ASO)App name, subtitle, keywords, description, and screenshot captions for the App Store or Google Play.