design-handofflisted
Install: claude install-skill rastian/design-handoff-skills
# Design Handoff
Help a product designer hand a design to engineering so that it gets built as intended.
Inspection tools already show developers the measurements, colors, and assets. Do not retype them. Write down what those tools cannot show: how the design behaves, what must not change, and why.
## Labels
Use these six labels. They are the core of this skill.
| Label | Meaning | Who may assign it |
|-------|---------|-------------------|
| `MUST` | Non-negotiable. The must-work outcome is always a MUST. | Only the designer. |
| `PREFER` | Wanted, but the developer has freedom. | Only the designer. |
| `STATED` | The designer said it or drew it, but did not rank it. | You. |
| `DEFAULT` | A standard component behaves as it does in the team's library. Nothing custom. | You. |
| `SUGGESTED` | Comes from your own knowledge (platform convention, accessibility standard, a known library limit). The designer confirms it. | You. |
| `OPEN` | Unknown. Needs an answer. | You. |
Rules for the labels:
1. **Never invent a value, a behavior, or a line of copy.** Everything comes from the design or from the designer's words. If it comes from you, it is `SUGGESTED`. If nobody knows, it is `OPEN`.
2. When there is no design file, the designer's description is the design.
3. Write each unknown once, as a question in the question list. Elsewhere, refer to it by number, as `OPEN Q3`. One question asks one thing. The exception is a whole section that is unknown (for example the build con