How to write project prompts: ready patterns for images, websites and code

Use the uploaded photo as a strict identity reference. Preserve facial features, face proportions, natural age and skin texture. Create a photorealistic chest-up portrait, vertical 4:5. Dark neutral studio, large softbox 45° camera-left, subtle rim light, natural contrast. Simple black clothing without a logo. Portrait focal length equivalent to 70-85 mm, shallow depth of field. Do not smooth the face, do not change the hairstyle and do not add accessories. Leave a safe margin above the head and on both sides.

For social media, establish the aspect ratio first. 4:5 uses vertical feed space well; set the exact pixel dimensions during export.

Source of truth: the uploaded product photo. Do not change the geometry, number of elements, holes, handles, logo, text or product colour. Change only the environment. Place the product in a realistic, bright interior appropriate to its use. Camera at product height, natural perspective, soft daylight from a large window, contact shadow consistent with the surface. Format 4:5. The product must remain the dominant element in the frame. After generation, verify 1:1: edges, mountings, text, proportions and number of parts.

For technical products, the source of truth remains the photograph, 3D render or CAD. The environment may be generated; the product specification may not.

Design a single tool icon for [feature name]. Style: simple modern 3D / soft-clay icon, one main symbol, no text and no logo. 3/4 view, readable silhouette at 64 px, soft studio lighting, subtle shadow. Transparent background. Central composition, no elements touching the edges. Prepare a square 1:1 variant. First describe the icon metaphor in one sentence, then generate it.

A good icon should work at a small size. Avoid multiple objects and microtext.

Goal: design a 1440 px-wide hero for a B2B service page. Audience: a business owner looking for a specific contractor. Keep the copy and prices from the brief unchanged. Layout: content on the left, visual composition on the right, one primary CTA and one secondary CTA. Style: bright, minimalist, plenty of breathing room, clear hierarchy. Also prepare mobile rules for 390 px. Do not add fictitious testimonials, client logos or statistics. At the end, provide: H1, lead, CTA, grid, spacing, mobile behaviour and an accessibility checklist.

In interface prompts, specify the result, breakpoints, source copy and acceptance criteria. “Premium” alone does not define a layout.

First audit the existing repository and identify the files responsible for the problem. Do not change the architecture unless necessary. Task: [describe the exact bug]. Preserve working APIs, routing and styles outside the scope. Make the smallest safe change. Add or update a regression test. Run lint and the full existing test suite. At the end, report: changed files, root cause, test results and anything that could not be verified. Do not mark the release as ready if the tests are red.

A code prompt should resemble a good technical ticket: current state, expected result, constraints and an acceptance test.