Design a research poster
Designs a conference poster with a headline finding, layout grid, condensed sections, figures to include and a 60-second walkthrough script. For researchers presenting at conferences.
People spend seconds deciding whether to stop at a poster. Posters that work state the main finding in plain words as the largest text on the page, show one or two clear figures that carry the evidence, and cut everything else to short blocks that can be read from about two metres. Posters that fail are shrunken papers: a title that names the topic but not the result, dense paragraphs, and every figure from the manuscript. Evidence-informed layouts (such as the "billboard" style with a central take-home message and a side column of supporting detail) and conventional column layouts both work if the reading order is obvious. The presenter's spoken walkthrough matters as much as the poster.
Design a poster from this materialOnly if [AUDIENCE] is given: for .
- Headline: write three candidate main messages: one plain-language sentence each, stating the finding (not the topic), true to the data. Recommend one. Then write a short formal title for the programme listing if the conference requires one.
- Layout: choose a layout (billboard with a central message, or two to four columns) suited to the size and orientation, and describe a grid with each block's position, its approximate share of the area, and the reading order. Include where the QR code, logos and author details go.
- Poster text: write each block in condensed form: background (two or three sentences on the gap), question or aim, methods (bullets or a small flow diagram), results (short captions that state what each figure shows), conclusion and implications (two or three bullets), and limitations in one line. Give a word count per block and a total; aim for roughly 300–800 words depending on size.
- Figures: choose the one or two figures that carry the main message and say how to adapt them for a poster: larger labels, fewer panels, direct labels instead of legends, colour-blind-safe palettes, and a one-line take-home caption above each. Describe any new figure needed, for example a simple bar or dot plot of the main effect.
- Walkthrough script: a 60-second spoken version (about 150 words) that opens with the question and finding, points at the figures in order, and ends with an invitation to discuss, plus a 10-second version for passers-by.
- Final checks: text size guidance for the format (for a printed poster, title roughly 85 pt or larger and body text at least 24 pt, readable from two metres), contrast, alignment, the conference's rules, a QR code to the paper or slides, and having a few printed handouts or a link.
- Use only the findings and numbers given. Do not round or restate numbers in a way that changes their meaning, and keep caveats (pilot study, small sample, preliminary) visible.
- The headline must be supported by the results; if the results are mixed or null, write a headline that says so honestly.
- Do not invent figures or data for them; propose figures only from the data provided.
- If the material is too thin to design from (for example only a title), ask for the abstract and key results.
- Use plain words in the headline and conclusions; keep technical terms in the methods.
Use the contract's section headings. Layout as a table: block | position | share of area | contents. Poster text as headed blocks with word counts. Figures as numbered items. Walkthrough script as quoted text. Final checks as a checklist.
1 required value still a placeholder; the assistant will ask for it.
details
- kind
- Prompt: a task you run by name to get one finished thing back
- domain
- Research and science
- category
- Scientific writing
- level
- Beginner
- made for
- Researcher / scientist, Student
- risk
- read-only
- version
- v1.0.0 · incubating
- reviewed
- 2026-10-02
- works in
- Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai
use in
npx @hermes-hq/hodios install design-research-poster --target claude-codenpx skills add hermes-hq/hodios-dist --skill design-research-poster -a claude-codeclaude plugin marketplace add hermes-hq/hodios-distclaude plugin install hodios-research-science@hodiosThe plugin brings every entry in this domain at once.
pairs well with
All of Scientific writingWrite a paper abstract
Writes a structured or unstructured abstract within a word limit from a manuscript, keeping every number faithful to the source and showing where each appears. Use before submission.
write-abstractExplain research to the public
Turns a research paper into an accurate plain-language summary, press release, blog post or social thread without hype, keeping caveats, study type and effect sizes. Use for science communication.
explain-research-to-publicScience communicator
Acts as a science communicator who makes research vivid and accurate, uses analogies carefully, keeps uncertainty visible and never overstates findings. For researchers, journalists and educators.
science-communicatorRespond to peer reviewers
Drafts a point-by-point response to peer-review comments, giving the change made or a polite, evidenced rebuttal for each, never claiming unmade changes. Use for revise-and-resubmit.
respond-to-reviewersWrite a research proposal
Writes a research or grant proposal section (aims, significance, approach, timeline) mapped to the funder's criteria, with placeholders instead of invented data. Use for grant or thesis proposals.
write-research-proposalAcademic writing rules
Standing rules for academic writing that hedge claims to the evidence, define terms, forbid invented citations, keep tense and terminology consistent, and report numbers precisely.
academic-writing-rules