1  # Image Generation Prompt Template - Kubernetes AI Blog
 2  
 3  ## Core Style Definition
 4  
 5  Create an image in a **serious-comic technocratical style** that balances technical accuracy with approachable, slightly humorous visual elements. The aesthetic should feel professional yet not overly corporate - think technical documentation meets modern tech illustration.
 6  
 7  ## Color Palette (from goern.name)
 8  
 9  **Light Theme Colors:**
10  - Background: `#F5EEDD` (warm cream/beige)
11  - Primary Text: `#06202B` (deep teal/dark blue)
12  - Links: `#077A7D` (teal/cyan)
13  - Link Hover: `#7AE2CF` (bright cyan)
14  - Accent Marks: `#698b69` (muted green)
15  - Secondary Accent: `#ef3982` (bright pink/magenta)
16  - Code Highlight: `#E74C3C` (red-orange)
17  
18  **Dark Theme Colors (optional):**
19  - Background: `#292a2d` (charcoal)
20  - Primary Text: `#a9a9b3` (light gray)
21  - Links: `#55bde2` (bright blue-cyan)
22  - Link Hover: `#bdebfc` (light cyan)
23  
24  **Primary Palette for Images:**
25  Use `#F5EEDD` (warm beige), `#077A7D` (teal), `#698b69` (muted green), and `#ef3982` (bright pink) as your core colors. These create a warm, technical aesthetic that balances professionalism with approachability. Accent with `#7AE2CF` (bright cyan) for "magic" or AI elements.
26  
27  ## Visual Style Characteristics
28  
29  - **Line work:** Clean, geometric vector-style illustrations with occasional hand-drawn elements for warmth
30  - **Complexity:** Technical but not overwhelming - simplified architectural diagrams that remain accurate
31  - **Tone:** Slightly playful without being childish; think XKCD meets AWS architecture diagrams
32  - **Composition:** Balanced, with clear focal points and intentional negative space
33  - **Icons/Symbols:** Recognizable Kubernetes symbols (hexagons, pods, nodes) mixed with AI motifs (neural networks, chat bubbles, automation arrows)
34  
35  ## Technical Elements to Include
36  
37  - Kubernetes pods and containers (as simplified geometric shapes)
38  - Network connections (as flowing lines or arrows)
39  - AI/ML indicators (brain icons, neural network patterns, sparkles for "magic")
40  - DevOps symbols (infinity loops, CI/CD pipelines)
41  - Abstract representation of declarative code (YAML-like structures, but artistic)
42  
43  ## Mood and Atmosphere
44  
45  - **Professional confidence** with a hint of "knowing wink"
46  - **Technical competence** without intimidation
47  - **Forward-looking optimism** about AI-assisted infrastructure
48  - **Subtle humor** - small Easter eggs or clever visual metaphors
49  
50  ## Composition Guidelines
51  
52  - Use isometric or flat 2.5D perspectives for technical diagrams
53  - Incorporate data visualization elements (graphs, metrics) as decorative elements
54  - Balance complexity with clarity - every element should serve a purpose
55  - Consider abstract geometric backgrounds that echo Kubernetes architecture patterns
56  
57  ## Example Prompt Structure
58  
59  ```
60  [Style description], featuring [main subject] in [composition style]. Color palette: [your colors]. 
61  Technical elements include [specific K8s/AI symbols]. Mood is [serious-comic technocratical], 
62  balancing professional accuracy with approachable visual design. [Additional specific requirements].
63  ```
64  
65  ## Anti-patterns to Avoid
66  
67  - ❌ Overly cartoonish or clipart-style graphics
68  - ❌ Stock photo realism
69  - ❌ Pure abstract art without recognizable tech elements
70  - ❌ Meme-heavy humor that undermines technical credibility
71  - ❌ Overcomplicated diagrams that sacrifice clarity
72  
73  ## Format Specifications
74  
75  - **Aspect Ratio:** 16:9 for blog headers, 1:1 for social media
76  - **Resolution:** Minimum 1920x1080 for headers
77  - **Style consistency:** Maintain visual language across all images for the article
78  - **Text overlay space:** Leave clear areas for potential title overlays