← ClaudeAtlas

handwritten-infographiclisted

Turn a technical topic into a hand-drawn notebook-style explainer infographic that shows BOTH how the thing works and what it costs you. Produces a validated content spec and a copy-paste image-generation prompt (for Designer, ChatGPT, Gemini, Midjourney or any image model), plus a proofread checklist for catching dropped text and broken numbering. Use whenever the user wants a handwritten or hand-drawn infographic, a notebook-style explainer, a 'how X works' poster with trade-offs, a LinkedIn carousel panel, or says 'infographic', 'hand-drawn diagram', 'handwritten notes style', 'explainer image', 'sketch-note', 'visual explainer'. Also use when they name a topic and ask to 'explain it visually' or 'make a poster about it'.
sheoraninfosec/Handwritten-Infographic-Claude-Skill · ★ 0 · AI & Automation · score 58
Install: claude install-skill sheoraninfosec/Handwritten-Infographic-Claude-Skill
# Handwritten Infographic — the Explainer layout Turn one topic into a hand-drawn, notebook-style explainer image. The format's whole argument is that **an honest explainer has two halves**. Most infographics only sell the thing. This one always pairs `HOW IT WORKS` with `WHAT IT COSTS YOU`, numbered continuously 1 to 8, so the reader gets the trade-offs in the same glance as the pitch. You do not render the image. You produce: 1. `spec.json` — the validated content 2. `prompt.txt` — a copy-paste prompt for any image model 3. `checklist.md` — what to proofread in the returned image All three go in the output folder. **A run is not finished until all three exist.** Create a todo per step so the checklist is not skipped — it is the part that catches the image model's mistakes. ## The one rule that matters **Never ship four upsides and four upsides.** Cards 1–4 explain the design. Cards 5–8 are what it costs the reader: limits, risks, work they inherit, things that break. If a topic seems to have no costs, you have not thought about it hard enough — every design decision trades something away. Write the costs first if it helps. ## Workflow ### Step 1: Settle the topic and the angle Ask the user for the topic if they have not given one. Then decide, without asking unless it is genuinely ambiguous: - **The accent colour.** The technology's own brand colour, as a hex. Look it up rather than guessing. Generic topics with no brand → `#0B7A80` (teal). Never use red as t