skills/linkedin-infographic-studio/references/visual-archetypes.md

# Visual archetype selector

Choose structure from the story shape before styling. Do not default to cards because they are easy to code.

All examples assume a 1080x1350 LinkedIn artboard.

## Comparison split

Use when two ideas, states, sources, approaches, or outcomes must be compared directly.

Structure:
- one shared headline
- two strongly differentiated visual fields
- one central relationship marker or axis
- one evidence or consequence row
- one takeaway spanning both sides

Avoid putting each side inside multiple nested cards. The visual contrast should carry the comparison.

## Flow map + verdict

Use when several inputs converge on one answer, decision, synthesis, or output.

Structure:
- setup or question
- 3-5 input nodes
- visible connectors
- central synthesis point
- verdict or takeaway panel

Motion can travel through connectors or activate inputs in sequence.

## Pipeline stages

Use for a real linear process with 4-6 stages.

Structure:
- headline and promise
- stages with meaningful progression
- visible directional relationship
- real output or consequence row
- takeaway

Do not create a stage card for content that is not actually sequential.

## Orbit or cycle

Use when no stage is truly first and the relationship is cyclical.

Structure:
- central anchor
- 4-6 nodes on a clear path
- concise node copy
- one visible cycle or feedback relationship

Use motion to indicate progression or active state, not constant rotation.

## Node tree

Use for hierarchy, dependencies, branching decisions, or capability relationships.

Structure:
- root node
- first-level branches
- limited second-level leaves
- connectors that explain dependency
- optional summary strip

Do not use when the story has no genuine hierarchy.

## Annotated blueprint

Use when one object, interface, diagram, or artifact is the hero and supporting facts explain parts of it.

Structure:
- dominant central object
- 3-6 annotations around it
- precise leader lines
- minimal supporting text
- takeaway below or beside the object

This is often stronger than turning each annotation into a separate card.

## Editorial signal sheet

Use for a thought-leadership idea with one strong claim and several pieces of evidence or implications.

Structure:
- oversized hook
- one dominant editorial visual or typographic relationship
- 2-4 supporting proof or implication blocks
- decisive takeaway

Allow open space, rules, typography, and scale to create structure instead of rounded boxes.

## Specimen grid

Use when comparing a family of examples where repeated visual treatment is meaningful.

Structure:
- clear category header
- consistent specimens
- one meaningful variable per specimen
- shared legend or takeaway

Repeated cells are valid here because repetition is the story. Keep cell count within feed-readable limits.

## Terminal or command surface

Use only when terminal/command interaction is genuinely part of the story.

Structure:
- coherent terminal frame
- one command or interaction sequence
- result/output
- concise explanation

Do not use terminal styling as generic tech decoration.

## Structural choice check

Before committing, answer:

1. What story relationship makes this archetype appropriate?
2. What would become harder to understand if this were replaced by generic cards?
3. What is the single dominant visual anchor?
4. What is the expected vertical occupancy?
5. Where does the composition visually terminate before the footer?

If the answers are weak, choose another archetype.