Figma Developer Handoff Specification Writer
Write specs that tell developers what the design means, not only how it looks.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Write a developer handoff specification for a Figma screen or flow. Screen purpose and user goal: [SCREEN_PURPOSE]. Description of the layout, components and states in the frame: [FRAME_DESCRIPTION]. Design tokens or styles used: [TOKENS]. Target platforms and breakpoints: [PLATFORMS]. Content that changes (names, lengths, languages): [DYNAMIC_CONTENT]. Produce Markdown with sections: purpose; layout and responsive behaviour (what stretches, wraps or stacks); components with variants and a table of states (default, hover, focus, pressed, disabled, loading, error, empty); interactions and transitions, with durations as suggestions; content rules (character limits, truncation, plural forms); accessibility notes (focus order, labels, contrast targets, touch target sizes); and open questions for design and engineering. Use token names, not raw values, unless I give values. Where I did not give a measurement, write [VERIFY]; do not invent any. Cover edge cases that are often missed: very long names, no data, slow network, right-to-left languages if relevant, and error messages. Say which details live in the Figma file (dev mode inspection [VERIFY the feature name in my plan]) and which need a written note. End with a checklist the developer can tick. The spec should answer a developer's first five questions without a meeting; list the questions that remain.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.