Methodology

How we build these guides

The color, style and occasion guides on Clad9 start from a fixed structure: color theory, garment conventions and dress codes. Here is what that structure is, what a language model adds to it, and how we check the result.

  1. 01

    The structure comes first

    Every color on Clad9 carries a real hex code, a color family, an undertone and a seasonal-palette classification. Color pairings follow the standard relationships of color theory: complementary, analogous and neutral-anchored. Occasions carry the dress codes people actually use, from black tie to smart casual.

    That structure lives in our database before a word is written about it. A language model never decides that two colors go together; it is handed a relationship that already exists.

  2. 02

    A language model writes the explanation

    Once a pairing or a dress code is in place, a language model (Claude, through AWS Bedrock) writes the plain-English explanation of why it works: the part you read on the page. It explains a relationship; it isn't asked to invent one.

  3. 03

    Every draft is checked before it's published

    Each new explanation is compared with every explanation already on the site using an embedding-similarity check. A draft that reads too close to something already published is held back and rewritten, so what you read was written for that page, not lightly reworded boilerplate.

  4. 04

    Guidance, not a stylist who has met you

    These guides are general styling guidance grounded in real conventions: a quick starting point, not personal advice from someone who has seen your closet, your coloring or your build. Clad9's daily looks are different: they're planned from the clothes you've catalogued, for your weather and your calendar.