What this prompt does
This prompt generates DALL-E prompts for clean technical diagrams and architecture illustrations. You describe the [diagram_topic], the [purpose], the [audience], and a [style_preference], and it produces prompts for several diagram types — system architecture, data flow, concept explainer, before/after comparison, and process/sequence — plus a style guide and a post-processing workflow.
The structure works around DALL-E's biggest weakness: text. Every prompt is engineered to produce the illustration without labels, because DALL-E garbles words, and you add text later in a design tool. The architecture prompts use isometric perspective and a consistent [color_scheme], with component sizing and arrow thickness carrying meaning. Because you set the [audience] and [purpose], the concept-explainer prompt can lean toward a visual metaphor for non-technical stakeholders while the architecture prompt stays precise for engineers. The [design_tool] slot tailors the post-processing steps to whatever you use to add labels.
When to use it
- When a blog post or doc needs an architecture or data-flow diagram and you don't have a designer.
- To draft a visual explainer of a system you've built for a technical or mixed audience.
- When you need a before/after or comparison diagram for a migration or refactor.
- To produce presentation-ready illustrations in light and dark background versions.
- When you want a clean illustrative base to label yourself rather than a finished diagram.
Example output
You get DALL-E prompts for each diagram type — system architecture (isometric, labeled-component layout with no text), data flow, a concept-explainer metaphor, a before/after split view, and a numbered process diagram — each using your [color_scheme] and [style_preference]. Then a style guide of do's and don'ts (consistent icon style, color-coding by layer, generous whitespace, max five colors), a post-processing workflow for importing into your design tool and adding labels, export specs per medium, and DALL-E-specific prompt-engineering tips.
Pro tips
- Always keep the "no text, no labels" instruction — DALL-E can't render readable text, so generate the clean illustration and add labels in
[design_tool]afterward. - Set
[color_scheme]to a small, named palette (three to five colors) and let it color-code by layer; more than five colors makes diagrams confusing. - Tailor
[style_preference]to context — isometric with soft shadows reads as polished for a blog, flatter line art reads cleaner in docs. - Use
[audience]deliberately: a developer audience wants accuracy in the architecture prompt, while stakeholders benefit from the concept-explainer metaphor. - Specify the background explicitly (white or dark) in the prompt; I generate both light and dark versions when the diagram will appear in slides.
- Treat DALL-E output as a base layer — trace it to vector or rebuild key shapes in
[design_tool]if the diagram needs to scale crisply.
