Ian Handdrawn PPT

Operating Rule

Resource Map

• references/intake.md

  : input types, missing-information checks, and concise clarification rules.

• references/narrative-planning.md

  : deck type selection and story structures.

• references/slide-archetypes.md

  : semantic mapping from content type to slide layout.

• references/visual-dna-v6.md

  : handdrawn Chinese technical PPT visual system and deck-level style lock.

• references/output-quality.md

  : output contracts and verification gates for final image pages.

• references/prompt-patterns.md

  : prompt templates for complete image-model slide pages.

assets/theme-tokens.json

assets/reference-handdrawn-article-illustration-style.png

references/prompt-patterns.md

Workflow

1. Ingest material
   • Read the provided content or attached file.
   • If the input is

     .pptx

     , extract the source content and visual intent only; do not edit or package the PPTX inside this skill.
   • If the input is

     .docx

     , use the Documents plugin or skill to extract content.
   • If the input is

     .pdf

     , use the PDF/document tooling appropriate to the task.
   • If the input is plain text, Markdown, notes, or an outline, parse it directly.
2. Run intake and gap diagnosis
   • Read

     references/intake.md

     when the content is broad, incomplete, or the output requirements are unclear.
   • Determine topic, audience, scenario, target length, and source sufficiency.
   • Ask at most 1-3 questions only when the missing information materially changes the deck.
   • If no critical information is missing, proceed with reasonable defaults.
3. Plan the deck narrative
   • Read

     references/narrative-planning.md

     .
   • Classify the deck as teaching, persuasive, report, product explanation, or knowledge-card style.
   • Create a slide-by-slide spine: each slide must have one main point.
4. Map each slide to an archetype
   • Read

     references/slide-archetypes.md

     .
   • Choose slide layouts from the content semantics, not from a fixed template order.
   • Vary archetypes so the deck has rhythm.
5. Apply visual DNA
   • Read

     references/visual-dna-v6.md

     .
   • Use small exact Chinese text, fine handdrawn lines, light pastel marks, few characters, low visual heaviness, large negative space, and one shared master layout language across the whole deck.
   • Lock cross-page constants before generating: page role, canvas ratio, near-white paper tone, no-border default, page number, title treatment, title optical size, line weight, pastel palette, corner grid marks, character policy, and spacing rhythm.
   • Keep the outer shell fixed across pages: page number location, title block, underline, paper tone, corner marks, and visual scale. Vary only the middle semantic diagram area according to the content.
   • Treat blog/article visuals as two role-specific outputs by default: a 21:9 cover image and 16:9 body illustrations. Do not let body pages look like cover pages.
6. Build output
   • For planning-only requests, deliver a structured blueprint with deck type, slide count, title, main point, archetype, content blocks, visual brief, and missing inputs.
   • For production requests, use the built-in image generation model to generate one complete page image per slide/visual. Use one image generation call per distinct page brief, not a generic repeated template.
   • When the user asks for a cover plus body illustrations, generate the cover as 21:9 and body illustrations as 16:9 unless the user specifies otherwise.
   • Before generating multiple pages, write one compact deck style lock and reuse it verbatim in every page prompt. Add page-specific layout instructions only for the central diagram/content area.
   • Keep all visible Chinese text short and exact in the prompt. Include a

     Required text only

     list for each page.
   • If exact Chinese text is mission-critical or repeated generations render text incorrectly, reduce the text budget first. If needed, generate the accepted visual with blank label spaces and add exact text as deterministic post-processing; the final deliverable is still a raster page image.
   • Save final selected images into the workspace, and make a contact sheet when generating multiple pages.
   • Check actual image dimensions. If the image model returns near-target native sizes, report the actual size; normalize body illustrations to 1920x1080 and cover images to 2520x1080 only when strict delivery dimensions are requested.
7. Verify
   • Read

     references/output-quality.md

     .
   • Check content accuracy, slide rhythm, Chinese text accuracy, visual consistency, style-anchor match, and commercial handoff readiness.
   • If verification fails, revise before final delivery.

Defaults

• Language: Simplified Chinese.
• Audience: Chinese learners with some technical curiosity but not necessarily expert depth.
• Deck length: 8-12 slides for an article, 15-30 slides for a course module, 5-8 slides for a short idea.
• Output: final PNG page images plus a contact sheet and short slide blueprint summary.
• Blog/article visual split: cover image is 21:9; body illustrations are 16:9.
• Style: refined near-white Chinese handdrawn technical article/PPT illustration V6.

Final Response

• The created image folder and contact sheet path.
• The page count and deck type.
• Any important assumptions.
• Verification performed and any remaining risks.