Recommended sentence order
Put the task first, then the permitted subject, scene, light, camera and preservation rules. Finish with output framing and negative constraints. This order gives each sentence one responsibility and keeps the highest-priority instruction near the beginning. It also makes the prompt scannable on mobile: users can remove one scene or camera sentence without accidentally deleting the identity rules.
Concrete language beats adjective stacks
Replace vague phrases such as ultra cinematic or professional quality with visible decisions. Name warm side light, readable shadow detail, a simple charcoal background, an eye-level head-and-shoulders crop or subtle film grain. Concrete language helps you compare the result with the request. Adjective stacks often repeat the same idea while leaving the tool to guess the composition and preservation boundaries.
Worked structure for a portrait
A useful portrait instruction can say: edit one consenting adult portrait; preserve face identity, age, hairstyle and proportions; keep the source outfit; use warm side light and a simple background; frame at eye level in 4:5; avoid changed identity, waxy skin, distorted eyes, text and logos. The exact visual values may change, but each part has a clear function and can be tested independently.
Keep personal details out of the prompt
Most editing tasks do not need a real name, address, account handle or other private information. Describe only the visible subject and the permitted transformation. The Builder keeps its text fields in the browser session and does not put subject details in the URL or analytics event properties. Apply the same discipline when you paste the prompt into any third-party tool, review that provider's own data terms, and remove metadata or context that is irrelevant to the visual task.