Prompt engineering

#What we render for you

You don't write prompts. You send structured fields — category, subtype, pose, background, views, tier — and we look up a versioned prompt template specific to that combination, fill in the slots, and dispatch to the routed provider.

This means "saree" doesn't generate a generic Indian-looking wrap. It generates a Nivi-style drape with 5–7 navel pleats and a left-shoulder pallu — because the saree.nivi.v1 template knows that's what Nivi means.

#Knobs you control

• garment.category + garment.subtype — chooses the prompt template.
• pose — free-form string. Defaults are sensible per category. Examples: "hand on waist", "walking towards camera", "namaste".
• background — studio_white, studio_grey, lifestyle_haveli, lifestyle_beach, transparent, or a free-form descriptor.
• views — adds camera-angle phrasing per child job.
• resolution — affects size hints. The router will downsample if the chosen provider can't hit the requested size.

#Saree subtypes

The drape style is everything. Match the subtype to the look.

#Nivi (Andhra / standard)

5–7 navel pleats, pallu over the left shoulder, falls behind to mid-thigh. The default for most modern saree wear.

#Bengali

Two-pleat shoulder drape, no front pleats, pallu draped over both shoulders.

#Gujarati (seedha pallu)

Pallu brought from back over the right shoulder, pleats fanned at front.

#Maharashtrian (kashta / 9-yard)

Dhoti-style between legs, no petticoat. Traditional, requires fuller-length fabric.

#Western garments

Western category templates are intentionally simpler — they describe garment fit and silhouette rather than draping rules. The primary lever is subtype (e.g. a-line / bodycon / maxi for dress).

#Custom prompts (advanced)

Power users can pass metadata.prompt_override — but beware: bypassing the registry sacrifices saree-aware drape instructions and may degrade output quality. We don't recommend it for production.

Companion: full taxonomy in Garment categories.