Documentation

Prompt Structure

Scenario

Without a shared schema, prompt quality varies by operator and output reliability drops.

Steps

  1. Start with the primary request in one sentence.
  2. Add scene/background context.
  3. Define subject invariants that must remain unchanged.
  4. Specify style, framing, and lighting.
  5. Add constraints and avoid-list.

Parameter Guidance

Use this template:

Primary request: <what to generate>
Scene/background: <where it appears>
Subject: <what must stay unchanged>
Style/medium: <look and treatment>
Composition/framing: <camera/crop intent>
Lighting/mood: <light direction and tone>
Constraints: <must keep>
Avoid: <must not appear>

Failure Troubleshooting

Symptom: Outputs are inconsistent between runs

Fix:

  • Keep stable style and lighting descriptors.
  • Avoid mixing conflicting aesthetics in one prompt.

Symptom: Requested object is changed accidentally

Fix:

  • Strengthen subject lock language.
  • Move optional ideas into separate test iterations.

Compliance Boundary

  • Avoid prompts for illegal, harmful, or deceptive categories.
  • Do not request edits that violate third-party rights.

FAQ

Should we optimize for creativity or control?

For production assets, optimize for control first and add creative variation in a second pass.

How often should templates be updated?

Review monthly or after major workflow changes.

Prompt Structure | Documentation | Pixelto