Yellow Sketchnote Deck

Explain how a small team can turn a question into a concrete test and a useful decision. Yellow Sketchnote Deck pairs oversized black/yellow headings with asymmetric copy islands and fine ink figures, giving experiment planning, feedback and comparison their own visual roles. The example is a guide structure, not evidence that an experiment has succeeded.

What you get

  • A custom-count sequence drawn from twelve optional roles: opening, question, first step, signals, tools, team, feedback, reflection, decision, experiment, comparison and close. Adapt or extend those roles without treating the twelve-page example as a default or limit.
  • A white/near-black/sunshine-yellow system with licensed heavy grotesk headings, small Arial copy, alternating illustration positions and sparse eight-arm asterisks. Opening/closing use giant centered two-tone titles; inner pages keep deliberate asymmetric text islands rather than generic equal cards.
  • Twelve local illustrated catalog assets and twelve example slots, with fine black outlines, unpainted skin areas, black hair/clothes and restrained yellow objects. Rockets, bulbs, gears, boards and expressive figures illustrate concepts; they do not represent actual staff, measured experiments or proven results.
  • Editable text, counts, tables, geometric marks and experiment comparisons around the placed illustrations. The selected plan determines artwork needs, with one independent image per page and an art ledger for subject, aspect, placement, palette, prompt and saved result. No fixed generation quota applies.
  • A standalone 16:9 HTML presentation with viewing, editing, thumbnails, notes, presentation mode and print styling, plus recipes/runtime, Python build/check and Node image tools. Requested PPTX preserves text/notes and separate pictures while ink/background/diagram art renders into layers; PDF gives one page per slide.

Before you choose

Read the experiment and comparison pages before the closing statement. A useful guide identifies what was tested, which differences matter and what decision follows. If those are still unknown, keep them open rather than let a confident headline or celebratory drawing imply success.

Good fit

  • A small team needs an experiment guide linking the initial question, test, useful signals, feedback and next decision.
  • A facilitator wants a consistent visual language across planning, shared learning, reflection and comparison pages.
  • A creator can supply approved content, a clear audience and decision goal and wants the sequence adapted to an exact count.

Not for

  • Reproducing protected illustrations, source identities, logos or recognizable reference figures.
  • Automatic research or verification of experiment results, causal claims or team performance.
  • A PowerPoint where every ink figure, asterisk, chart and decorative primitive remains a native editable shape.
  • Gray-shadowed 3D character art, full-page raster slides or a repetitive card grid replacing the authored asymmetric typography.

How to use

You say/yellow-sketchnote-deck Create a twelve-page small-team experiment guide with bold yellow-and-black headlines and original ink figures.
  1. Provide topic, audience, approved messages/source material, language and exact count, adding the decision the guide should support. Supply actual questions, test conditions, observations and measures where making real claims. Agree a missing count from content and duration before generation; include cover/close unless specified otherwise.

  2. Plan useful page jobs from question to first step, signals, feedback, test and decision. Choose/reorder/adapt the twelve recipes rather than copy their exact sequence. Preserve the single authored white/black/yellow system and alternating asymmetric art placement; the themes reference is not a list of interchangeable palette presets.

  3. Keep the licensed heavy grotesk display face, tight large two-tone titles and compact Arial supporting text. Asterisks remain editable SVG. Maintain clean silhouettes, fine pen detail and restrained yellow objects; do not add gray shading, 3D figures or rasterize the complete slide.

  4. Create an art ledger for actual slots. Choose suitable reuse of the twelve local illustrations, reuse with generated gaps or all-new art, giving approved supplied material priority. Use each pictorial source once, including closing artwork; crops/recolors/rotations do not become independent scenes. Match the kit’s square inner scenes, 4:3 experiment, 16:9 comparison and 3:2 close.

  5. Embed catalog IDs with the checksum-verifying Node helper. Authorized fresh illustrations may use a built-in tool or optional paid FAL route with FAL_KEY, recording returned task IDs for status/fetch without automatic failure retries. Account/provider costs may apply. Keep labeled gaps when no suitable image is available, and decide image count from content rather than a quota.

  6. Replace example questions, test statements, comparison labels and notes with approved material. Distinguish a proposed signal or success threshold from an observed result. Keep words/tables/diagram labels outside artwork. Compose/build/check with Python 3 and the expected count/style kit; Node is for media helpers. Preserve notices, embed final assets and stay below 20 MB.

  7. Open over local HTTP and inspect each 1280×720 page for title fit, small-copy readability, art/text balance, silhouette crops, contrast and bounds. Confirm actual count, thumbnails and notes, then test Edit/E, text/images/order/notes/object changes, undo/redo, Save and reopening the HTML.

  8. Export requested PPTX/PDF, run the PPTX checker and inspect editable text/notes, rendered ink layers and actual fonts in the target application. The shared editor has individual color editing, not a preset theme picker. Report real visual findings and remaining evidence gaps instead of equating a successful build with a validated experiment.

Requirements and costs

You bring
Presentation topic and audience · Key messages or source material · Desired slide count and language
Dependencies
A browser for presentation and verified print export · Node.js for local validation · A host image generation tool for fresh artwork · Chrome, Chromium or Edge plus Node.js 20 or newer — required only for PowerPoint export
Outside costs
Generating new artwork may incur a separate provider charge. The included original example can be viewed without image generation.
Publisher testing
v1.0.5 — Claude Code / Claude Desktop / Cowork / Codex / ChatGPT

FAQ

User reviews

—0 reviews

Select a star to share your experience.

No reviews yet. Ratings appear once readers share real experiences.

Similar Skills

View all skills