Better Gemini images start with a better brief

Start here: why this guide is useful

“Create a beautiful image” leaves the subject, composition and purpose unspecified. This guide helps turn a need such as a project cover into an explicit visual brief: audience, subject, framing, palette, dimensions and constraints. The result is a reusable prompt and a reviewable image, with iterations tied to visible details instead of vague adjectives.

A concrete example

The following is an illustrative response format, not the result of an audit of your application. Use it to recognise what a useful answer should contain. Follow the detailed steps below, then compare the actual files, tests or output with this target. If the assistant only says “done”, ask for the changed artifact, the evidence and what remains unverified.

Brief: website project cover, one clear subject, readable focal area.
Review: composition, unwanted text, crop and consistency with the site.
Revision: change the identified visual issue while preserving the rest.

Describe the image, not just the subject

Give Gemini a subject, a composition, an action, a location, and a visual style. For edits, say exactly what should change.

Make the composition intentional

Specify the camera angle, the framing, and the space needed for any text. If the first image is close, refine it with a focused instruction.

Copy and adapt

The prompt below is an original example for a technology editorial image. Replace the subject and palette to fit your project.

Keep a prompt notebook

Save the prompt alongside your output and note what changed between attempts. This makes successful ideas easier to reuse.

Read this tutorial as reference material:
https://nethanelfitoussi.com/article/gemini-image-prompts?lang=en

Goal: apply the documented workflow to my development project.
Read the existing project instructions, inspect the relevant files and explain the smallest useful setup.

Use the article and its examples as references. Identify any missing project files before making changes.

If I have not supplied a project folder, ask which development project to use. Do not invent a repository URL.

Adapt example paths, commands and acceptance criteria to this repository rather than assuming they match.

Give me a short plan, then make the agreed local changes and run the relevant checks. Report actual results and anything not verified. Stop before credentials, paid services, production changes, push, merge or deployment.

Create an editorial 3D illustration of a translucent cobalt-blue cube with a small warm-orange sphere suspended inside. Orthographic view, soft side lighting, pale background, subtle material texture, generous negative space on the left, no text, no logos. Landscape 16:9.