Update to Whiteboard by Lumin

{
  "description": "Turn an explanation, process, comparison, or idea into a visual story on Whiteboard by Lumin. Use when deciding what to show and how readers should follow it, rather than for file operations or a small label edit.",
  "included_files": [],
  "name": "whiteboard-storytelling",
  "skill_md_contents": "---\nname: whiteboard-storytelling\ndescription: Turn an explanation, process, comparison, or idea into a visual story on Whiteboard by Lumin. Use when deciding what to show and how readers should follow it, rather than for file operations or a small label edit.\n---\n\n# Visual storytelling\n\nFor file creation or edits, follow [Whiteboard operations](../whiteboard/SKILL.md). Plan within the user's requested board and scope; a visual explanation does not require a separate board.\n\n## Choose the structure\n\nIdentify the question the viewer should be able to answer after looking at the board. Use the user's audience and facts when supplied. For a simple request, make a reasonable choice and draw; do not turn it into a planning interview.\n\nChoose a structure that carries the meaning:\n\n| Reader's question | Useful structure |\n| --- | --- |\n| What happens next? | Process with one main direction and labeled decision branches |\n| What changes? | Before and after, using matching positions and scale |\n| How do these options differ? | Side-by-side columns with the same comparison criteria |\n| How does this work? | Components grouped by responsibility, with labeled relationships |\n| Why does this happen? | Cause and effect, distinguishing evidence from a hypothesis |\n| How does it unfold? | A short sequence of panels with a clear progression |\n\nFor a requested illustration, focus on its subject and supporting details instead of forcing a flowchart. Preserve playful or expressive intent.\n\n## Make the message visible\n\nGive the board a short title that states its subject or supported takeaway. Establish one obvious starting point. Let shape size, position, and grouping carry structure; use concise text to explain what shapes cannot. Prefer specific nouns for entities and verbs for actions. Label arrows when their relationship is not self-evident.\n\nSeparate the main path from exceptions and supporting detail. Use a secondary row, callout, or section when that improves comprehension. Avoid squeezing an essay into boxes or duplicating every sentence as a shape. Preserve distinctions the user cares about, even if the board needs more space.\n\nDo not invent numbers, evidence, causality, or missing steps. Identify assumptions and unknowns on the board when material. A bigger shape must not imply a larger quantity unless that relationship is intentional and supported.\n\nUse [Layout](../whiteboard-layout/SKILL.md) to arrange the chosen structure and [Style](../whiteboard-style/SKILL.md) for its visual treatment. Check the result: can a viewer identify the topic, follow the sequence, and understand the conclusion without reading the chat? For an existing board, preserve the user's organization unless restructuring is requested or necessary for the requested change.\n"
}