Skip to main content 홈 크리에이터 comeonoliver skillshub baoyu-comic
baoyu-comic Knowledge comic creator supporting multiple styles (Logicomix/Ligne Claire, Ohmsha manga guide). Creates original educational comics with detailed panel layouts and sequential image generation. Use when user asks to create "知识漫画", "教育漫画", "biography comic", "tutorial comic", or "Logicomix-style comic".
설치로 이동 Skills Marketplace 커뮤니티가 만든 AI 스킬을 발견하고 탐색하세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/ComeOnOliver/skillshub --skill baoyu-comic명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Zip 다운로드 다운로드 중... name baoyu-comic description Knowledge comic creator supporting multiple styles (Logicomix/Ligne Claire, Ohmsha manga guide). Creates original educational comics with detailed panel layouts and sequential image generation. Use when user asks to create "知识漫画", "教育漫画", "biography comic", "tutorial comic", or "Logicomix-style comic".
Knowledge Comic Creator
Create original knowledge comics with multiple visual styles.
Usage
/baoyu-comic posts/turing-story/source.md
/baoyu-comic
Options
Option Values --styleclassic (default), dramatic, warm, tech, sepia, vibrant, ohmsha, realistic, or custom description --layoutstandard (default), cinematic, dense, splash, mixed, webtoon --aspect3:4 (default, portrait), 4:3 (landscape), 16:9 (widescreen) --langauto (default), zh, en, ja, etc.
Style × Layout × Aspect can be freely combined. Custom styles can be described in natural language.
Aspect ratio is consistent across all pages in a comic.
Auto Selection
Content Signals Style Layout Tutorial, how-to, beginner ohmsha webtoon Computing, AI, programming tech dense Pre-1950, classical, ancient sepia cinematic
Personal story, mentor warm standard
Conflict, breakthrough dramatic splash
Wine, food, business, lifestyle, professional realistic cinematic
Biography, balanced classic mixed
Script Directory Important : All scripts are located in the scripts/ subdirectory of this skill.
Agent Execution Instructions :
Determine this SKILL.md file's directory path as SKILL_DIR
Script path = ${SKILL_DIR}/scripts/<script-name>.ts
Replace all ${SKILL_DIR} in this document with the actual path
Script Purpose scripts/merge-to-pdf.tsMerge comic pages into PDF
File Structure [target]/
├── source.md # Source content (if pasted, not file)
├── analysis.md # Deep analysis results (YAML+MD)
├── storyboard-chronological.md # Variant A (preserved)
├── storyboard-thematic.md # Variant B (preserved)
├── storyboard-character.md # Variant C (preserved)
├── characters-chronological/ # Variant A chars (preserved)
│ ├── characters.md
│ └── characters.png
├── characters-thematic/ # Variant B chars (preserved)
│ ├── characters.md
│ └── characters.png
├── characters-character/ # Variant C chars (preserved)
│ ├── characters.md
│ └── characters.png
├── storyboard.md # Final selected
├── characters/ # Final selected
│ ├── characters.md
│ └── characters.png
├── prompts/
│ ├── 00-cover-[slug].md
│ └── NN-page-[slug].md
├── 00-cover-[slug].png
├── NN-page-[slug].png
└── {topic-slug}.pdf
With source path: [source-dir]/[source-name-no-ext]/comic/
Example: /posts/turing-story.md → /posts/turing-story/comic/
Without source: ./comic/[topic-slug]/
If target directory exists, rename existing to <dirname>-backup-YYYYMMDD-HHMMSS
Workflow
Step 1: Analyze Content → analysis.md Read source content, save it if needed, and perform deep analysis.
Save source content (if not already a file):
If user provides a file path: use as-is
If user pastes content: save to source.md in target directory
Read source content
Deep analysis following references/analysis-framework.md:
Target audience identification
Value proposition for readers
Core themes and narrative potential
Key figures and their story arcs
Detect source language
Determine recommended page count:
Short story: 5-8 pages
Medium complexity: 9-15 pages
Full biography: 16-25 pages
Analyze content signals for style/layout recommendations
Save to analysis.md ---
title: "Alan Turing: Father of Computing"
topic: Biography
time_span: 1912 -1954
source_language: en
user_language: zh
aspect_ratio: "3:4"
recommended_page_count: 12
---
- **Primary**: Tech enthusiasts curious about computing history
- **Secondary**: Students learning about scientific breakthroughs
- **Tertiary**: General readers interested in biographical stories
What readers will gain:
1 . Understanding of how modern computing was born
2 . Emotional connection to a brilliant but tragic figure
3 . Appreciation for the human cost of innovation
| Theme | Narrative Potential | Visual Opportunity |
|-------|--------------------|--------------------|
| Genius vs. Society | High conflict, dramatic arcs | Contrast scenes |
| Code-breaking | Mystery, tension | Technical diagrams as art |
| Personal tragedy | Emotional depth | Intimate, somber panels |
- **Arc**: Misunderstood genius → War hero → Tragic end
- **Visual identity**: Disheveled academic, intense eyes
- **Key moments**: Enigma breakthrough, arrest, final days
- **Role**: Early friend whose death shaped Turing
- **Visual identity**: Youthful, bright
- **Key moments**: School friendship, sudden death
- "biography" → classic + mixed
- "computing history" → tech + dense
- "personal tragedy" → dramatic + splash
1 . **Chronological** - follow life timeline (recommended for biography)
2 . **Thematic** - organize by contributions (good for educational focus)
3 . **Character-focused** - relationships drive narrative (good for emotional impact)
Step 2: Generate 3 Storyboard Variants Create three distinct variants, each combining a narrative approach with a recommended style.
Variant Narrative Approach Recommended Style Layout A Chronological sepia cinematic B Thematic tech dense C Character-focused warm standard
Generate storyboard (storyboard-{approach}.md):
YAML front matter with narrative_approach, recommended_style, recommended_layout, aspect_ratio
Cover design
Each page: layout, panel breakdown, visual prompts
Written in user's preferred language Reference: references/storyboard-template.md
Generate matching characters (characters-{approach}/):
characters.md - visual specs matching the recommended style (in user's preferred language)characters.png - character reference sheetReference: references/character-template.md
All variants are preserved after selection for reference.
Step 3: User Confirms All Options IMPORTANT : Present ALL options in a single confirmation step using AskUserQuestion. Do NOT interrupt workflow with multiple separate confirmations.
Determine which questions to ask :
Question When to Ask Storyboard variant Always (required) Visual style Always (required) Language Only if source_language ≠ user_language Aspect ratio Only if user might prefer non-default (e.g., landscape content)
If source language = user language: Just inform user (e.g., "Comic will be in Chinese")
If different: Ask which language to use
All storyboards and prompts are generated in the user's selected/preferred language.
Default: 3:4 (portrait) - standard comic format
Offer 4:3 (landscape) if content suits it (e.g., panoramic scenes, technical diagrams)
Offer 16:9 (widescreen) for cinematic content
AskUserQuestion format (example with all questions):
Question 1 (Storyboard): Which storyboard variant?
- A: Chronological + sepia (Recommended)
- B: Thematic + tech
- C: Character-focused + warm
- Custom
Question 2 (Style): Which visual style?
- sepia (Recommended from variant)
- classic / dramatic / warm / tech / vibrant / ohmsha / realistic
- Custom description
Question 3 (Language) - only if mismatch:
- Chinese (source material language)
- English (your preference)
Question 4 (Aspect) - only if relevant:
- 3:4 Portrait (Recommended)
- 4:3 Landscape
- 16:9 Widescreen
Copy selected storyboard → storyboard.md
Copy selected characters → characters/
Update YAML front matter with confirmed style, language, aspect_ratio
If style differs from variant's recommended: regenerate characters/characters.png
User may edit files directly for fine-tuning
Step 4: Generate Images With confirmed storyboard + style + aspect ratio:
For each page (cover + pages) :
Save prompt to prompts/NN-{cover|page}-[slug].md (in user's preferred language)
Generate image using confirmed style and aspect ratio
Report progress after each generation
Image Generation Skill Selection :
Check available image generation skills
If multiple skills available, ask user preference
Character Reference Handling :
If skill supports reference image: pass characters/characters.png
If skill does NOT support reference image: include characters/characters.md content in prompt
Session Management :
If image generation skill supports --sessionId:
Generate unique session ID: comic-{topic-slug}-{timestamp}
Use same session ID for all pages
Ensures visual consistency across generated images
Step 5: Merge to PDF After all images generated:
npx -y bun ${SKILL_DIR} /scripts/merge-to-pdf.ts <comic-dir>
Creates {topic-slug}.pdf with all pages as full-page images.
Step 6: Completion Report Comic Complete!
Title: [title] | Style: [style] | Pages: [count] | Aspect: [ratio] | Language: [lang]
Location: [path]
✓ analysis.md
✓ characters.png
✓ 00-cover-[slug].png ... NN-page-[slug].png
✓ {topic-slug}.pdf
Page Modification Support for modifying individual pages after initial generation.
Edit Single Page Regenerate a specific page with modified prompt:
Identify page to edit (e.g., 03-page-enigma-machine.png)
Update prompt in prompts/03-page-enigma-machine.md if needed
If content changes significantly, update slug in filename
Regenerate image using same session ID and aspect ratio
Regenerate PDF
Add New Page Insert a new page at specified position:
Specify insertion position (e.g., after page 3)
Create new prompt with appropriate slug (e.g., 04-page-bletchley-park.md)
Generate new page image (same aspect ratio)
Renumber files : All subsequent pages increment NN by 1
04-page-tragedy.png → 05-page-tragedy.pngSlugs remain unchanged
Update storyboard.md with new page entry
Regenerate PDF
Delete Page Remove a page and renumber:
Identify page to delete (e.g., 03-page-enigma-machine.png)
Remove image file and prompt file
Renumber files : All subsequent pages decrement NN by 1
04-page-tragedy.png → 03-page-tragedy.pngSlugs remain unchanged
Update storyboard.md to remove page entry
Regenerate PDF
File Naming Convention Files use meaningful slugs for better readability:
NN-cover-[slug].png / NN-page-[slug].png
NN-cover-[slug].md / NN-page-[slug].md (in prompts/)
00-cover-turing-story.png01-page-early-life.png02-page-cambridge-years.png03-page-enigma-machine.png
Derived from page title/content (kebab-case)
Must be unique within the comic
When page content changes significantly, update slug accordingly
After add/delete, update NN prefix for affected pages
Slug remains unchanged unless content changes
Maintain sequential numbering with no gaps
Style-Specific Guidelines
Ohmsha Style (--style ohmsha) Additional requirements for educational manga:
Default: Use Doraemon characters directly - No need to create new characters
大雄 (Nobita): Student role, curious learner
哆啦A梦 (Doraemon): Mentor role, explains concepts with gadgets
胖虎 (Gian): Antagonist/challenge role, represents obstacles or misconceptions
静香 (Shizuka): Supporting role, asks clarifying questions
Custom characters only if explicitly requested: --characters "Student:小明,Mentor:教授"
Must use visual metaphors (gadgets, action scenes) - NO talking heads
Page titles: narrative style, not "Page X: Topic"
Reference : references/ohmsha-guide.md for detailed guidelines.
References Detailed templates and guidelines in references/ directory:
analysis-framework.md - Deep content analysis for comic adaptationcharacter-template.md - Character definition format and examplesstoryboard-template.md - Storyboard structure and panel breakdownohmsha-guide.md - Ohmsha manga style specificsstyles/ - Detailed style definitionslayouts/ - Detailed layout definitions 이 저장소의 다른 Skills Review product and feature risk before an AI coding agent starts implementation.
Use Xquik for X data and confirmation-gated X actions: tweet search, user lookup, follower export, media download, monitors, webhooks, MCP, and SDK workflows.
Canton Network open-source ecosystem guide covering DAML SDK, Canton runtime, and Splice applications. Use when working with Canton Network, DAML smart contracts, or building decentralized applications.
