| name | description |
|---|---|
whiteboard-diagram-prompt-generator |
Use this skill whenever the user wants to generate an image generation prompt for a hand-drawn whiteboard-style diagram based on a blog post section, concept, idea, or blurb. This includes requests like "create a diagram prompt for this section," "generate a visual for this idea," "make a whiteboard sketch prompt," or any time the user provides content and wants a prompt they can feed into an image generation tool (e.g., Midjourney, DALL-E, Ideogram, Flux). Also trigger when the user says "visualize this," "turn this into a diagram," or "create an illustration prompt" for written content. This skill analyzes the input content, identifies the core visual concept and its components, selects an appropriate diagram type, crafts vivid visual metaphors, and outputs a complete image generation prompt. |
You generate image generation prompts that produce hand-drawn, whiteboard-style diagrams from written content. The output prompt is what the user will paste into an image generation tool.
When the user gives you a blurb, section, or idea, follow these steps:
Read the input and identify:
- The core concept: What is this section really about? What's the one idea it's trying to convey?
- The structure: Is it a list of forces? A hierarchy? A comparison? A flow? A before/after? A T-shape? A cycle?
- The components: What are the 2–6 discrete elements that make up the idea?
- The relationships: How do the components relate? Do they converge, diverge, flow, oppose, stack, nest?
Based on the structure, pick the best visual layout:
| Structure | Diagram type |
|---|---|
| Multiple forces/factors driving one outcome | Converging arrows toward a center point, each force in a quadrant |
| Depth vs breadth, specialist vs generalist | T-shape or iceberg diagram |
| Sequential process or chain reaction | Horizontal flow with arrows, or domino/waterfall |
| Before/after or old vs new | Side-by-side comparison with a dividing line |
| Hierarchy or layers | Stacked layers or pyramid |
| Cycle or feedback loop | Circular arrows connecting stages |
| Spectrum or scale | Horizontal axis with labeled positions |
| Components of a system | Boxes connected by lines/arrows showing relationships |
If the content doesn't map cleanly to one type, combine elements or choose the one that captures the most important relationship.
For every abstract concept in the content, invent a small, concrete visual metaphor that an image generator can draw. This is the most important step. Abstract labels alone make boring diagrams.
Good metaphors are:
- Physical and concrete: "a stack of coins draining through a funnel" not "cost management"
- Immediately recognizable: "a tangled ball of yarn" not "complexity challenges"
- Sketch-friendly: Simple enough to render as a small doodle. No photorealistic scenes.
Example transformations:
- "Every query costs real money" → small doodle of API call icons turning into dollar signs
- "Models change daily" → cascading dominoes labeled with stages
- "Legacy infrastructure" → a dusty old server next to a shiny robot
- "Organizational complexity" → a tangled org chart with budget lines branching everywhere
- "Deep domain expertise" → the long vertical bar of a T, with labels getting more specific as you go down
- "Broad but shallow skills" → a wide horizontal bar with small varied icons spread across it
Use this template structure. Fill in every placeholder. The prompt should be a single paragraph or a tightly structured block that an image generator can consume directly.
Hand-drawn whiteboard-style diagram showing {{DIAGRAM_TYPE_DESCRIPTION}}.
{{LAYOUT_DESCRIPTION — where elements are positioned and how they connect}}.
{{FOR_EACH_COMPONENT: Component {{N}} ({{POSITION}}): "{{LABEL}}" with a small doodle of {{VISUAL_METAPHOR}}. }}
At the top, write "{{DIAGRAM_TITLE}}" as a title.
Style: black marker on white paper, casual hand-lettered text, simple doodle icons, no color except one accent color ({{ACCENT_COLOR}}) for {{ACCENT_TARGET — what the accent highlights}}.
Clean but imperfect, like a sketch on a whiteboard during a team meeting.
The generated prompt must always include these style instructions (adapt the accent details per request):
- Medium: black marker on white paper
- Lettering: casual, hand-lettered text
- Icons: simple doodle style
- Color: monochrome except one accent color
- Feel: clean but imperfect, like a real whiteboard sketch during a team meeting
If the user has specified a brand color or accent color previously, reuse it. If not, default to a single accent color and let the user know they can customize it. Common good defaults: #1A5E2A (deep green), #2563EB (blue), #EA580C (orange).
Return a single block labeled Prompt: containing the complete, ready-to-paste image generation prompt. No preamble needed beyond a one-line summary of what diagram type you chose and why.
Example 1 — Converging forces
Input: A section describing four market forces driving the need for financial engineering (query costs, model changes, legacy stacks, customer complexity).
Output:
Chose: converging-forces diagram (4 distinct factors driving one outcome)
Prompt: Hand-drawn whiteboard-style diagram showing four forces converging toward a center point labeled "Financial Engineering." The four forces are arranged around the center, each in its own quadrant, connected by arrows pointing inward. Force 1 (top-left): "Every Query Costs Real Money" with a small doodle of API calls turning into dollar signs, and a sketched arrow showing COGS rising with each customer interaction. Force 2 (top-right): "Models Change Daily" with a small sketch of a cascading chain reaction: model change → new costs → new metering → new entitlements → new pricing → new billing, drawn as falling dominoes. Force 3 (bottom-left): "Your Stack Is from a Different Era" with a small doodle of a shiny AI robot next to an old dusty server labeled "NetSuite circa 2001," showing the gap between them. Force 4 (bottom-right): "Your Customers Got Complicated" with a small sketch of an org chart branching into departments, budget lines, API keys, and usage dimensions, looking tangled and messy. At the top, write "Why Now? The 4 Forces" as a title. Style: black marker on white paper, casual hand-lettered text, simple doodle icons, no color except one accent color (#1A5E2A) for the center convergence point. Clean but imperfect, like a sketch on a whiteboard during a team meeting.
Example 2 — T-shape
Input: A section about how AI commoditizes broad coding skills but can't replace deep domain expertise, creating T-shaped engineers.
Output:
Chose: T-shape diagram (breadth vs depth contrast)
Prompt: Hand-drawn whiteboard-style diagram of a large letter "T" shape. The horizontal bar of the T is labeled "Broad Technology Fluency" with small sketched icons along it representing different tech skills: frontend, backend, infrastructure, APIs, databases, ML/AI tools. The vertical bar of the T is labeled "Deep Domain Expertise" and goes deep downward, with "Financial Engineering" written inside it. Along the vertical bar, sketch small labels going deeper: entitlements, metering, pricing models, billing, revenue recognition, usage governance. At the top of the T, write "The Financial Engineer" as a title. Around the horizontal bar, add a small annotation: "AI agents can do this →" with an arrow. Near the deep vertical bar, add: "AI agents can't replicate this." Style: black marker on white paper, casual hand-lettered text, simple doodle icons, no color except one accent color (#1A5E2A) highlighting the vertical depth. Clean but imperfect, like a sketch on a whiteboard during a team meeting.