Images and code

Images

Describe subject, composition, lighting, and what to avoid. Treat the first generation as a sketch. Never publish likenesses or brand marks you do not have rights to use.

For anything that looks like a real person, assume consent is required. Synthetic beauty ideals travel fast; keep disclosure honest when you publish.

Code

• Ask for the smallest change that solves the problem.
• Require tests or a reproduction when the change touches security or money paths.
• Run the code. Reading confident code is not the same as executing it.
• Do not paste production secrets into prompts.

Spec before generate

Whether image or code, write the acceptance bar first:

• Good looks like: concrete, testable, owned
• Bad looks like: vague polish, invented APIs, unlicensed faces

Practice

Take one image or code task. Write a five-line spec. Generate once. Reject anything that fails the spec without renegotiating the bar mid-stream.

See also

• Challenge: When AI becomes the beauty standard
• Field Guide: Verify
• Field Guide: Build a workflow
• Next: Evaluate without theater