Can I add a recommendation badge on the better approach?

Yes — add "Place a small \"Recommended\" badge in the top-right of the [side] column."

ComparisonText → ImageLow creditEN

Method Comparison Mind Map (Pros vs Cons)

Clean side-by-side comparison of two approaches with color-coded pros and cons branches.

When to use this prompt

For related-work tables, blog posts comparing technical approaches, and survey papers.

The prompt

A horizontal mind-map comparing two approaches for vulnerability discovery in source code.

Left side: "End-to-End LLM"
Right side: "Architectural Decomposition"

Each side has two color-coded branches:
- Pros (dark green)
- Cons (dark red)

End-to-End LLM
Pros: simple integration; fast prototyping; broad language coverage.
Cons: hallucinated findings; no provenance; vulnerable to "semantic bypass".

Architectural Decomposition
Pros: traceable evidence chain; deterministic queries; ontology-grounded.
Cons: heavier engineering; schema maintenance overhead.

Layout: central vertical divider; method title at top of each side in a colored header bar; pros branches above, cons below. Use clean rounded labels, generous whitespace, sans-serif typography. Optimize for poster readability. White background.

Variations

Three-way comparison

A three-column comparison of three approaches (Approach A, B, C). Each column lists Pros (green checkmarks) and Cons (red crosses) plus a one-line summary at the top. Equal column widths, white background, poster-readable.

Decision tree variant

Same content but laid out as a decision tree with binary "yes/no" branches starting from the question "Do you have schema constraints?" leading to either "End-to-End LLM" or "Architectural Decomposition" leaf nodes.

Tips

Use exactly 3–4 bullets per branch. More than 5 makes the figure cramped.
Use color names, not hex codes — generators handle "dark green / dark red" reliably.
Keep each bullet under 6 words for poster legibility.