fashion-designlisted

# Fashion Design — Systems, Capsules & Specs The craft layer for apparel brand-building: wardrobe architecture, capsule economics, garment spec language, and fashion-specific evidence discipline. Brand-agnostic — bring your own brandDNA. ## 1. Wardrobe System Architecture Structure the offer as **2–5 systems named for wearer states, not garment categories or demographics** (reference pattern: FORM/MOVE/FLOW/TRANSIT/REST — studio to recovery, one daily arc). Rules: - Every SKU belongs to exactly one system; system tag appears on site, labels, and internal docs — this is the primary navigation axis - **Fit logic is a separate axis from garment type.** Define 2–3 fit logics (reference pattern: R = one shared pattern / T = same design, blocks A+B where anatomy changes the pattern / C = body-specific essentials). The naming is an ethical position, not a sizing chart — whichever demographics-split convention exists in the category (men/women racks, "for her/him"), the brand's own tests must forbid it - Hero product logic: choose the *least crowded, most describable* garment as entry wedge ("one trouser anyone can wear and describe to a friend"), versioned like software rather than seasonally replaced ## 2. Capsule & SKU Math - Capsule = designs × colors × size-count; shared patterns multiply cheapest (one pattern serves all bodies; per-block patterns multiply by block count) - Publish the arithmetic in the entity doc: `(shared designs × colors × sizes) + (