> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vinmake.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Style Creation

> The standalone style creation workflow used by command or as part of email intake

# Style Creation

⚪ **Planned (Phase 2)**

The style creation workflow can be triggered two ways: explicitly by a merchandiser
using a command, or implicitly as the next step in the [Email → Style](/brain/staging/workflows/email-to-style) flow.

## Triggers

### Manual command

A merchandiser sends:

> "Create a new style from this tech pack."

Or uses:

```text theme={null}
/create-style
```

With one or more attached documents.

### Automated from email intake

The [Email → Style](/brain/staging/workflows/email-to-style) workflow ends by calling
this workflow with the extracted style fields pre-populated. The merchandiser still
sees the draft and approves.

## What Brain extracts

Whether triggered manually or via email, Brain extracts the same fields:

| Field                   | Description                            |
| ----------------------- | -------------------------------------- |
| Client                  | Which client owns this request         |
| Client PIC              | Person on the client side              |
| VinMake PIC             | Internal merchandiser                  |
| Style reference         | Client's style number                  |
| Style name              | If available                           |
| Category                | Jacket, dress, pant, shirt, etc.       |
| Gender                  | Womenswear, menswear, kidswear, unisex |
| Season                  | If available                           |
| Product images          | From tech pack or email                |
| Attachments             | All files attached                     |
| RFQ date                | When the request came in               |
| Required quotation date | If specified                           |
| Target delivery date    | If specified                           |
| Notes                   | Special instructions from the client   |

Every field carries a confidence score and a link to its source.

## Duplicate detection

Before creating anything, Brain checks for duplicates against CutMake.

* **Exact match:** No new style created. Task updated with the matched style reference.
* **Near match:** Brain surfaces candidates for human disambiguation rather than
  guessing. Options: create as new, link to existing, mark duplicate, ask client to
  clarify.

Examples of near-match patterns:

* `J26WGW153` vs `J26WGW153A`
* `J26WGW153` vs `J26WGW155`
* Same image, different code
* Same name, different client
* Same code, different season

## Draft preview

| Field            | AI Draft                 | Confidence |
| ---------------- | ------------------------ | ---------: |
| Client           | Jaspal                   |       High |
| Style Ref        | J26WGW153                |       High |
| Category         | Women's jacket           |     Medium |
| Client PIC       | Kaimook                  |       High |
| Internal PIC     | Mai                      |     Medium |
| Attachments      | 3 files detected         |       High |
| Product Image    | Extracted from tech pack |     Medium |
| Duplicate Status | No exact match found     |       High |

## Approval actions

* Approve and create the style in CutMake
* Edit fields inline
* Reject
* Mark as duplicate
* Ask Brain to re-read attachments

## After approval

Brain writes the style record to CutMake and offers:

> "Style created. The next usual step is to create a true cost. Would you like me
> to draft the BOM from the tech pack now?"

## Related

* [Email → Style](/brain/staging/workflows/email-to-style) — the automated upstream
* [Tech Pack → BOM](/brain/staging/workflows/tech-pack-to-bom) — usual next step
* [Principles](/brain/staging/principles) — duplicate handling and approval rules