The layered system that shapes every generation run

MerchantDrafts doesn't use a single prompt. It builds a layered context from multiple sources — store-level settings, per-category notes, per-manufacturer descriptions, structural style rules, and per-run controls — and combines them at generation time. Each layer adds a different dimension of context so the output is shaped by the store's actual intent rather than a generic instruction.

01

Store-level layers are set in Settings

Business Context, Writing Pattern, Category Context, and Manufacturer Description are written once in MerchantDrafts Settings and applied automatically to every future generation run.

02

Per-run controls narrow the output

Tone, Description Length, and What to Emphasize are set per generation run from the left-side generation controls — they narrow the output within the context already established by the Settings layers.

03

All layers combine at generation time

MerchantDrafts assembles the full context from all active layers before generation runs — the operator doesn't need to combine or repeat them manually each time.

Six layers that build the generation context before output is produced

Each layer adds a distinct dimension to the generation context. Store-level layers are set once in Settings. Per-run controls are adjusted each time. Together they give the AI enough context to produce output that reflects the store's actual intent — without the operator manually constructing that context in a prompt each time.

MerchantDrafts Settings — prompt layer configuration.

Store-wide · dominant

Business Context

Brand voice, positioning, and audience. Set once in Settings. The dominant baseline for every generation run across the entire catalogue.

Store-wide · structural

Writing Pattern

Sentence rhythm, vocabulary register, and formatting style. Set once in Settings. Shapes how the AI writes — not what it says about the brand.

Per-category · automatic

Category Context

What each WooCommerce category is about. Written per category in Settings. Resolved automatically for each product at generation time.

Manufacturer Description

Per-manufacturer brand and product range notes. Written in Settings per brand. Pulled into the prompt automatically when generation runs for a product in that manufacturer range.

Tone and Description Length

Per-run controls set from the left-side generation controls. Narrow the tone and output volume for each specific generation run within the context already set by Settings layers.

What to Emphasize

Per-run product focus control. Set from the generation controls for each run. Tells the AI what aspects of the product to foreground in the generated output.

All layers combine automatically

MerchantDrafts assembles all active layers into the generation context. The operator doesn't construct the prompt — they set the layers and run generation.

Before

Constructing context manually in every prompt

  • Write the brand description, category notes, manufacturer details, and style rules into each AI prompt manually.
  • Context drifts between products and operators because there's no single shared source for any of these dimensions.
  • Changing the brand description means finding and updating every prompt where it was written in by hand.
  • Batch runs produce inconsistent output because the per-product context isn't resolved automatically from structured sources.

After

Prompt layers configured in MerchantDrafts Settings

  • Write each layer once in Settings — Business Context, Writing Pattern, Category Context, and Manufacturer Description are stored and reused automatically.
  • Per-run controls like Tone and What to Emphasize are set from the generation interface for the current job, narrowing within the stored context.
  • Every generation run — single product or full batch — draws from the same layer stack without the operator reconstructing it.
  • Updating one layer in Settings propagates to all future runs without touching anything else.

The layers narrow the context — they don't replace each other.

Business Context is the widest layer. Each subsequent layer adds specificity within it. Output reflects all active layers together, not just the most recently set one.

Context configured once, applied consistently across the catalogue

The prompt layer system removes the overhead of constructing store context on every generation run. Write each layer once, and every future run draws from the same consistent foundation without the operator repeating the work.

MerchantDrafts Settings — prompt layers configuration.

01

Set once, applied everywhere

Store-level layers — Business Context, Writing Pattern, Category Context, Manufacturer Description — are written once in Settings and applied to every future generation run.

Output shaped by all active prompt layers.

02

Consistent output across the catalogue

Every generation run draws from the same layer stack, so output reads consistently across different products, operators, and batch sizes.

Products Workspace batch generation with all layers applied.

03

Batch runs use the full stack automatically

When generating a filtered batch in Products Workspace, each product draws its Category Context and Manufacturer Description automatically — the stack works without per-product manual setup.

Product ready to generate with all layers configured.

04

No prompt construction per run

The operator sets per-run controls like Tone and What to Emphasize from the interface. MerchantDrafts assembles the full context — the operator doesn't write the prompt manually.

Review drawer with layer-consistent output.

05

Review focuses on content, not drift

When context is configured in advance and applied consistently, review time is spent checking content accuracy rather than correcting brand drift, structural inconsistency, or missing context.

Update one layer, propagate to all future runs.

06

Update one layer, propagate everywhere

When the store changes — a new brand direction, a different style register, an updated manufacturer range — update the relevant layer in Settings and all future runs reflect it immediately.

Expanded screenshot