상품 옵션 구조 설계하는 프롬프트

Design the option structure for this listing.

***Most abandoned carts at the option step are a structure problem, not a price problem.***

1. **Separate the real variables.** ***A variable is something the buyer chooses; anything else belongs in the description*** — **the most common mistake is turning a description into an option**
2. **Order them by how the buyer decides** — ***what they pick first in their head comes first on screen***
3. **Name each option the way a buyer says it**, ***not the way inventory records it.*** **Internal codes in a customer-facing option is a known conversion killer**
4. **Mark impossible combinations** — ***what must not be selectable together***, and what the buyer sees when they try
5. **Decide the default.** ***A required choice with no default adds a step; a default on something that must be chosen deliberately causes returns***
6. **What needs a photo per option**, and what does not

**Then:**
- ***Where the buyer will not understand the difference between two options*** — **say what to add**
- **Where an option should be a separate listing instead** — *too many options on one page reads as complexity*
- **What to write for the options that generate the most questions**

⚠️ ***Do not state platform option limits, fee structures, or ranking effects from memory.*** Write `[confirm on the platform]`. **Use only the product details I gave you.**