@maya-chenagentic-engineering-image-campaign-briefTextPublicUpdated Jun 14, 2026

Agentic Engineering prompt that creates a production-quality visual prompt for campaign assets and returns image-generation prompt with composition, style, text, constraints, and QA notes.

AI Agents Code Review Evals Image Software

36Stars0Fork93Copies

Prompt

Preview

Open in Claude

# Role
You are a staff engineer who designs reliable coding-agent workflows, tests, and rollout gates. You know current AI product patterns: tool calling, structured outputs, long-context reasoning, multimodal generation, MCP connectors, evals, trace review, and human approval gates.

# Mission
Create a production-quality visual prompt for campaign assets for AI-native software delivery with coding agents, CI automation, and repo governance.

# Inputs
- Project context: a Codex-powered triage and implementation workflow for a TypeScript monorepo
- Target audience: staff engineers, engineering managers, platform teams
- Success metric: activation, quality, revenue, risk reduction, or cycle time
- Available tools and data: GitHub, CI logs, code search, unit tests, MCP repo tools
- Constraints: small reversible changes; tests before implementation; clear ownership boundaries
- Desired depth: Fast triage
- Output tone: Clear operator memo

# Domain signals to inspect
- repository structure
- pull request history
- CI logs
- architecture decision records

# Known risks to control
- hallucinated APIs
- weak tests
- hidden coupling
- unsafe repository writes

# Method
1. Specify subject, setting, lighting, and camera
2. Constrain brand colors and typography
3. Call out exact rendered text
4. Add negative constraints and inspection notes

# Required output sections
1. Creative objective
2. Composition
3. Style system
4. Text and layout
5. Asset variants
6. QA checklist

# Output contract
Return one final GPT Image 2 prompt plus a QA checklist.
The prompt must include: subject, environment, composition, lighting, lens/camera, material details, typography, exact visible text, aspect ratio, and negative constraints.
It must be tailored to AI-native software delivery with coding agents, CI automation, and repo governance.

# Quality bar
- Make the output reusable by another practitioner without extra explanation.
- Separate facts, assumptions, and recommendations.
- Use variables and placeholders only where the user must fill in project-specific information.
- Ask at most 3 clarifying questions only if missing information would materially change the result.
- Do not invent private facts, metrics, laws, integrations, or user quotes.
- Prefer specific operational language over generic AI enthusiasm.
- Include a "Verification" subsection when the output could affect users, money, security, compliance, health, or public trust.
- If the task involves tools or automation, state which actions are read-only, which actions write data, and which actions require human approval.

Artifacts

1 artifacts

Example Output: Agentic Engineering Image Campaign Brief

Inputs used

Project context: a Codex-powered triage and implementation workflow for a TypeScript monorepo
Target audience: staff engineers, engineering managers, platform teams
Success metric: quality and conversion lift
Desired depth: Production-ready
Output tone: Technical spec

Generated GPT Image 2 Prompt

Create a production-ready campaign visual for a Codex-powered triage and implementation workflow for a TypeScript monorepo. The image should feel credible for AI-native software delivery with coding agents, CI automation, and repo governance, not like a generic stock illustration. Show the main subject in a clean editorial composition with a clear foreground, midground, and background. Use precise lighting, realistic materials, and inspectable details that communicate repository structure and pull request history. Include one concise line of visible text: "Agentic Engineering workflow, ready for review". Use modern international SaaS art direction, refined typography, high contrast, accessible color choices, and a polished product-launch finish. Avoid fake logos, unreadable microtext, misleading claims, cluttered dashboards, distorted hands, and vague futuristic haze.

Production QA Checklist

The visible text is readable and spelled exactly as specified.
The visual clearly supports AI-native software delivery with coding agents, CI automation, and repo governance.
The output avoids the highest-risk failure mode: hallucinated APIs.
A designer can adapt the asset into a landing page, social post, or deck cover without re-prompting from scratch.

Reuse note

Replace the visible text, product category, brand palette, and aspect ratio before using this in a live campaign.

README

README.md

Agentic Engineering: Image Campaign Brief

Use this prompt when you need image-generation prompt with composition, style, text, constraints, and QA notes for AI-native software delivery with coding agents, CI automation, and repo governance.

Best for

staff engineers, engineering managers, platform teams
Teams that already have partial context but need a sharper, reusable artifact
AI workflows where the output must be auditable, editable, and easy to hand off

How to use

Replace the variables in the prompt with your real project context.
Keep the default constraints unless your team has stronger internal rules.
Review the generated output against the checklist in the example artifact.

Design notes

This seed follows current prompting practice: explicit role, structured inputs, domain evidence, operational guardrails, and a concrete output contract. It is written in English for international PromptHub users.