Handoff SVG: a frozen frame for product and engineering—not slice manifests or animatable vector components
`design-handoff-psd-svg` reduces friction when partners cannot open PSDs: one MIME type drops into docs. Engineering will be disappointed if they try to mine nine-patch or slice boxes from it—that belongs in Zeplin-like tooling. Ship tokens, spacing tables, and the PSD alongside the SVG instead of pretending the wrapper replaces them.
사용방법
- Freeze naming and design tokens in Figma or PS, export the handoff SVG, and put “not a production icon” in the first paragraph of the email.
- Have one PM and one front-end engineer open the file in the real wiki or doc stack, watching for sanitizer stripping and unexpected outbound requests.
- Register the SVG hash on the delivery checklist and bind it to the same Storybook capture so nobody bookmarks a stale Confluence attachment.
PSD to SVG (handoff) FAQ
Teams assume SVG means editable vectors—what single sentence should lead the README or email?
Lead with: this file wraps a merged raster inside `<image>` for viewport semantics; there are no rebuildable paths or live text for CSS `fill` tweaks. Send typography and color edits back through PSD or a dedicated vector redraw. Without that banner, front-end wires it like a glyph and files false “converter broken” bugs.
Smart-object or linked art visible in Photoshop disappears in the handoff SVG—hidden layers, broken links, or the wrong comp?
Check whether the smart object was hidden before the merge action, whether the link is offline, and whether you targeted the correct layer comp. Rasterize or embed must-show links before handoff and note “baked” in the manifest so factory PSDs cannot disagree with the preview.
Brand swatches differ between the SVG preview and UI review laptops—who owns the numbers?
Tokens plus export reports in sRGB hex are authoritative; review laptops are relative layout checks only. Document acceptable ΔE or stick to contrast checks across devices. Phone photos are not a color-signing instrument—use a colorimeter baseline when fights escalate.
Engineering demands slice coordinates—can they measure this SVG or its embedded PNG instead of Zeplin?
Raster wrappers do not carry trustworthy slice rectangles or padding metadata; export coordinates from Photoshop generator presets or a manifest file. Measuring compressed embedded pixels invites half-pixel drift, and Android nine-patch cannot be inferred from a preview wrapper.
Security asks whether SVG equals executable script—how do we answer for our generator versus user uploads?
Split the narrative: pipeline output should be static `svg`/`image` only, yet you still virus-scan and hash releases. If customers upload arbitrary SVG, you must sanitize and allow-list tags—your tool being static does not shrink the whole attack surface.