Cloud Architecture Diagram Visual Prompt Verification Checklist

Role: Principal Solutions Architect and Technical Documentation Visual Lead

Context

• Target cloud ecosystem: {{cloud_platform}}
• Architectural pattern: {{architecture_pattern}}
• Security isolation boundary: {{security_classification}}
• Primary consumer audience: {{technical_audience}}
• Notation and style standard: {{diagram_standard}}
• Critical infrastructure nodes: {{infrastructure_components}}

Task

Generate an architectural prompt verification checklist that ensures image generation prompts produce clean, accurate, and professional systems architecture graphics representing {{architecture_pattern}} on {{cloud_platform}}.

Method

1. Translate the core compute, storage, and networking layers of {{infrastructure_components}} into discrete visual prompt blocks.
2. Map the data flow directionality and boundary encapsulations required for {{security_classification}} into composition layout rules.
3. Define graphic aesthetic parameters matching {{diagram_standard}} (e.g., flat vector, isometric blueprint, modular node-graph).
4. Establish prompt rules that enforce vendor-accurate iconography and color-coding for {{cloud_platform}}.
5. Build negative prompt parameters to eliminate visual spaghetti wiring, floating unlabeled nodes, and pseudo-alphabetic gibberish.
6. Align cognitive density and hierarchy specifically for the technical depth of {{technical_audience}}.
7. Formulate a final pre-execution sanity check covering spatial orientation, node clustering, and legible relational arrows.

Constraints

• The output MUST format every verification item as an interactive markdown checklist box [ ].
• You MUST NOT use generic artistic styling terms like "photorealistic" or "cinematic lighting" in technical diagram prompts.
• Technical flow directions must be specified using explicit compositional weights (e.g., left-to-right flow, concentric security zones).
• Include explicit negative keywords against photorealism, illegible text, and perspective distortion.

Output format

Provide the output in 4 sequential categories: 1. Topology & Flow Orientation, 2. Vendor Iconography & Component Syntax, 3. Security Boundary & Layering Controls, and 4. Style Hygiene & Text Suppression. Conclude with a Ready-to-Execute Prompt Template block containing positive and negative prompt slots. Total word count: 450-650 words.

Self-review

• Did I reflect the technical requirements of {{architecture_pattern}} and {{cloud_platform}}?
• Are diagram flows constrained strictly against common AI visual hallucinations?
• Does the output provide clear negative constraints to block fake labels and corrupted text?