visual-intent

Topics in the source

• Visual Intent
• Purpose
• When to invoke
• Inputs
• Required intermediate representation
• Procedure
• Intent → chart family (SEM-01, S04)
• Medium profiles

Fix what the visual must accomplish and for whom before deciding how it looks. Most serious visualization failures originate upstream of the encoding — solving the wrong problem or mis-abstracting the data — and no amount of styling repairs them (S01). This skill produces the intent contract every other skill consumes. At the start of any request to make a chart, figure, map, diagram, or data slide. When a draft "looks fine" but you cannot state its one-sentence takeaway. When someone asks which chart type to use. Do not skip it because the request seems simple; an unexamined default is where the wrong-problem failure hides. The data (or a description: fields, types, size, provenance). The audience and the delivery medium. What decision or understanding the visual should enable. Produce an intent record before proposing any chart: 1. Characterize the domain problem, users, data, and task abstraction (INTENT-01, INTENT-02). Name the reader task explicitly. 2. Name the audience and its literacy; tailor complexity and framing (INTENT-03). 3. Write the takeaway sentence — for a captioned figure, draft the caption first (INTENT-04). 4. Map the reader task to an analytic relationship, th

This is an excerpt. Refer to the complete source and its current requirements.