comic

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Knowledge Comic Creator

知识漫画创作工具

Create original knowledge comics with multiple visual styles.
可创作具有多种视觉风格的原创知识漫画。

Usage

使用方法

bash
/comic posts/turing-story/source.md
/comic  # then paste content
bash
/comic posts/turing-story/source.md
/comic  # 然后粘贴内容

Options

选项

OptionValues
--style
classic (default), dramatic, warm, sepia, vibrant, ohmsha, realistic, wuxia, shoujo, or custom description
--layout
standard (default), cinematic, dense, splash, mixed, webtoon
--aspect
3:4 (default, portrait), 4:3 (landscape), 16:9 (widescreen)
--lang
auto (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.
选项取值
--style
classic(默认)、dramatic、warm、sepia、vibrant、ohmsha、realistic、wuxia、shoujo,或自定义描述
--layout
standard(默认)、cinematic、dense、splash、mixed、webtoon
--aspect
3:4(默认,竖版)、4:3(横版)、16:9(宽屏)
--lang
auto(默认)、zh、en、ja等
风格×布局×宽高比可自由组合。自定义风格可使用自然语言描述。
漫画中所有页面的宽高比保持一致。

Auto Selection

自动选择

Content SignalsStyleLayout
Tutorial, how-to, beginnerohmshawebtoon
Computing, AI, programmingohmshadense
Pre-1950, classical, ancientsepiacinematic
Personal story, mentorwarmstandard
Conflict, breakthroughdramaticsplash
Wine, food, business, lifestyle, professionalrealisticcinematic
Martial arts, wuxia, xianxia, Chinese historicalwuxiasplash
Romance, love, school life, friendship, emotionalshoujostandard
Biography, balancedclassicmixed
内容特征风格布局
教程、操作指南、入门内容ohmshawebtoon
计算机、AI、编程ohmshadense
1950年前、古典、古代内容sepiacinematic
个人故事、导师主题warmstandard
冲突、突破主题dramaticsplash
酒、美食、商业、生活方式、专业内容realisticcinematic
武侠、仙侠、中国历史内容wuxiasplash
爱情、校园生活、友情、情感类内容shoujostandard
传记、平衡类内容classicmixed

Script Directory

脚本目录

Important: All scripts are located in
scripts/
subdirectory of this skill.
Agent Execution Instructions:
  1. Determine this SKILL.md file's directory path as
    SKILL_DIR
  2. Script path =
    ${SKILL_DIR}/scripts/<script-name>.ts
  3. Replace all
    ${SKILL_DIR}
    in this document with actual path
Script Reference:
ScriptPurpose
scripts/merge-to-pdf.ts
Merge comic pages into PDF
重要提示:所有脚本都位于本skill的
scripts/
子目录中。
Agent执行说明:
  1. 确定本SKILL.md文件的目录路径为
    SKILL_DIR
  2. 脚本路径 =
    ${SKILL_DIR}/scripts/<script-name>.ts
  3. 将本文档中所有
    ${SKILL_DIR}
    替换为实际路径
脚本参考:
脚本用途
scripts/merge-to-pdf.ts
将漫画页面合并为PDF

File Structure

文件结构

Each session creates an independent directory named by content slug:
comic/{topic-slug}/
├── source-{slug}.{ext}            # Source files (text, images, etc.)
├── 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
Slug Generation:
  1. Extract main topic from content (2-4 words, kebab-case)
  2. Example: "Alan Turing Biography" →
    alan-turing-bio
Conflict Resolution: If
comic/{topic-slug}/
already exists:
  • Append timestamp:
    {topic-slug}-YYYYMMDD-HHMMSS
  • Example:
    turing-story
    exists →
    turing-story-20260118-143052
Source Files: Copy all sources with naming
source-{slug}.{ext}
:
  • source-biography.md
    ,
    source-portrait.jpg
    ,
    source-timeline.png
    , etc.
  • Multiple sources supported: text, images, files from conversation
每个会话会创建一个独立目录,目录名由内容别名(slug)生成:
comic/{topic-slug}/
├── source-{slug}.{ext}            # 源文件(文本、图片等)
├── analysis.md                    # 深度分析结果(YAML+MD格式)
├── storyboard-chronological.md    # 变体A(保留)
├── storyboard-thematic.md         # 变体B(保留)
├── storyboard-character.md        # 变体C(保留)
├── characters-chronological/      # 变体A角色设定(保留)
│   ├── characters.md
│   └── characters.png
├── characters-thematic/           # 变体B角色设定(保留)
│   ├── characters.md
│   └── characters.png
├── characters-character/          # 变体C角色设定(保留)
│   ├── characters.md
│   └── characters.png
├── storyboard.md                  # 最终选中的分镜
├── characters/                    # 最终选中的角色设定
│   ├── characters.md
│   └── characters.png
├── prompts/
│   ├── 00-cover-[slug].md
│   └── NN-page-[slug].md
├── 00-cover-[slug].png
├── NN-page-[slug].png
└── {topic-slug}.pdf
别名(Slug)生成规则:
  1. 从内容中提取主题(2-4个单词,短横线分隔格式)
  2. 示例:"Alan Turing Biography" →
    alan-turing-bio
冲突解决: 如果
comic/{topic-slug}/
目录已存在:
  • 追加时间戳:
    {topic-slug}-YYYYMMDD-HHMMSS
  • 示例:
    turing-story
    已存在 →
    turing-story-20260118-143052
源文件: 将所有源文件复制为
source-{slug}.{ext}
命名格式:
  • source-biography.md
    source-portrait.jpg
    source-timeline.png
  • 支持多个源文件:文本、图片、对话中的文件

Workflow

工作流程

Step 1: Analyze Content →
analysis.md

步骤1:分析内容 →
analysis.md

Read source content, save it if needed, and perform deep analysis.
Actions:
  1. 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
  2. Read source content
  3. 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
  4. Detect source language
  5. Determine recommended page count:
    • Short story: 5-8 pages
    • Medium complexity: 9-15 pages
    • Full biography: 16-25 pages
  6. Analyze content signals for style/layout recommendations
  7. Save to
    analysis.md
analysis.md Format:
yaml
---
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
---
读取源内容(如需保存则保存),并执行深度分析。
操作步骤:
  1. 保存源内容(如果尚未是文件):
    • 如果用户提供文件路径:直接使用
    • 如果用户粘贴内容:保存到目标目录的
      source.md
      文件中
  2. 读取源内容
  3. 按照
    references/analysis-framework.md
    执行深度分析
    :
    • 目标受众识别
    • 读者价值主张
    • 核心主题与叙事潜力
    • 关键人物及其故事弧光
  4. 检测源语言
  5. 确定推荐页数:
    • 短篇故事:5-8页
    • 中等复杂度:9-15页
    • 完整传记:16-25页
  6. 分析内容特征以推荐风格和布局
  7. 保存到
    analysis.md
analysis.md格式:
yaml
---
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
---

Target Audience

目标受众

  • Primary: Tech enthusiasts curious about computing history
  • Secondary: Students learning about scientific breakthroughs
  • Tertiary: General readers interested in biographical stories
  • 主要受众:对计算机历史感兴趣的科技爱好者
  • 次要受众:学习科学突破的学生
  • 三级受众:对传记故事感兴趣的普通读者

Value Proposition

读者价值主张

What readers will gain:
  1. Understanding of how modern computing was born
  2. Emotional connection to a brilliant but tragic figure
  3. Appreciation for human cost of innovation
读者将获得:
  1. 了解现代计算机的诞生过程
  2. 与这位才华横溢却命运悲惨的人物建立情感联结
  3. 体会创新背后的人文代价

Core Themes

核心主题

ThemeNarrative PotentialVisual Opportunity
Genius vs. SocietyHigh conflict, dramatic arcsContrast scenes
Code-breakingMystery, tensionTechnical diagrams as art
Personal tragedyEmotional depthIntimate, somber panels
主题叙事潜力视觉呈现机会
天才与社会的冲突高冲突、戏剧性弧光场景对比呈现
密码破译悬疑、紧张感将技术图表艺术化
个人悲剧情感深度私密、阴郁的分镜

Key Figures & Story Arcs

关键人物与故事弧光

Alan Turing (Protagonist)

艾伦·图灵(主角)

  • Arc: Misunderstood genius → War hero → Tragic end
  • Visual identity: Disheveled academic, intense eyes
  • Key moments: Enigma breakthrough, arrest, final days
  • 故事弧光:不被理解的天才 → 战争英雄 → 悲惨结局
  • 视觉特征:凌乱的学者形象、锐利的眼神
  • 关键场景:恩尼格玛密码机突破、被捕、最后时光

Christopher Morcom (Catalyst)

克里斯托弗·莫科姆(催化剂)

  • Role: Early friend whose death shaped Turing
  • Visual identity: Youthful, bright
  • Key moments: School friendship, sudden death
  • 角色定位:早期好友,其离世影响了图灵的人生
  • 视觉特征:年轻、阳光
  • 关键场景:校园友谊、突然离世

Content Signals

内容特征

  • "biography" → classic + mixed
  • "computing history" → ohmsha + dense
  • "personal tragedy" → dramatic + splash
  • "传记" → classic + mixed
  • "计算机历史" → ohmsha + dense
  • "个人悲剧" → dramatic + splash

Recommended Approaches

推荐叙事方式

  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)
undefined
  1. ** chronological(按时间顺序)** - 遵循时间线(传记推荐使用)
  2. ** thematic(按主题分类)** - 按贡献内容组织(适合教育类内容)
  3. ** character-focused(人物聚焦)** - 以人物关系推动叙事(适合情感类内容)
undefined

Step 2: Generate 3 Storyboard Variants

步骤2:生成3种分镜变体

Create three distinct variants, each combining a narrative approach with a recommended style.
VariantNarrative ApproachRecommended StyleLayout
AChronologicalsepiacinematic
BThematicohmshadense
CCharacter-focusedwarmstandard
For each variant:
  1. 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
  2. Generate matching characters (
    characters-{approach}/
    ):
    • characters.md
      - visual specs matching recommended style (in user's preferred language)
    • characters.png
      - character reference sheet
    • Reference:
      references/character-template.md
All variants are preserved after selection for reference.
创建三种不同的变体,每种变体结合一种叙事方式和推荐风格。
变体叙事方式推荐风格布局
A按时间顺序sepiacinematic
B按主题分类ohmshadense
C人物聚焦warmstandard
针对每个变体:
  1. 生成分镜
    storyboard-{approach}.md
    ):
    • YAML前置元数据,包含narrative_approach、recommended_style、recommended_layout、aspect_ratio
    • 封面设计
    • 每一页:布局、分镜拆解、视觉提示
    • 使用用户偏好的语言编写
    • 参考:
      references/storyboard-template.md
  2. 生成匹配的角色设定
    characters-{approach}/
    ):
    • characters.md
      - 符合推荐风格的视觉规格(使用用户偏好的语言)
    • characters.png
      - 角色参考图
    • 参考:
      references/character-template.md
所有变体在选中后仍会保留,以供参考。

Step 3: User Confirms All Options

步骤3:用户确认所有选项

IMPORTANT: Present ALL options in a single confirmation step using AskUserQuestion. Do NOT interrupt workflow with multiple separate confirmations.
Determine which questions to ask:
QuestionWhen to Ask
Storyboard variantAlways (required)
Visual styleAlways (required)
LanguageOnly if
source_language ≠ user_language
Aspect ratioOnly if user might prefer non-default (e.g., landscape content)
Language handling:
  • 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 user's selected/preferred language.
Aspect ratio handling:
  • 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 + ohmsha
- C: Character-focused + warm
- Custom

Question 2 (Style): Which visual style?
- sepia (Recommended from variant)
- classic / dramatic / warm / sepia / vibrant / ohmsha / realistic / wuxia
- 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
After confirmation:
  1. Copy selected storyboard →
    storyboard.md
  2. Copy selected characters →
    characters/
  3. Update YAML front matter with confirmed style, language, aspect_ratio
  4. If style differs from variant's recommended: regenerate
    characters/characters.png
  5. User may edit files directly for fine-tuning
重要提示:使用AskUserQuestion在单个确认步骤中展示所有选项。请勿通过多个单独的确认步骤中断工作流程。
确定需要询问的问题:
问题询问时机
分镜变体始终询问(必填)
视觉风格始终询问(必填)
语言仅当
source_language ≠ user_language
时询问
宽高比仅当用户可能偏好非默认值时询问(例如横版内容)
语言处理:
  • 如果源语言=用户语言:仅告知用户(例如:"漫画将使用中文创作")
  • 如果不同:询问使用哪种语言
所有分镜和提示都将以用户选择/偏好的语言生成。
宽高比处理:
  • 默认:3:4(竖版)- 标准漫画格式
  • 如果内容适合,提供4:3(横版)选项(例如全景场景、技术图表)
  • 为电影类内容提供16:9(宽屏)选项
AskUserQuestion格式(包含所有问题的示例):
问题1(分镜):选择哪种分镜变体?
- A: 按时间顺序 + sepia(推荐)
- B: 按主题分类 + ohmsha
- C: 人物聚焦 + warm
- 自定义

问题2(风格):选择哪种视觉风格?
- sepia(变体推荐)
- classic / dramatic / warm / sepia / vibrant / ohmsha / realistic / wuxia
- 自定义描述

问题3(语言)- 仅当语言不匹配时询问:
- 中文(源材料语言)
- 英文(你的偏好)

问题4(宽高比)- 仅当相关时询问:
- 3:4 竖版(推荐)
- 4:3 横版
- 16:9 宽屏
确认后:
  1. 将选中的分镜复制为
    storyboard.md
  2. 将选中的角色设定复制为
    characters/
  3. 更新YAML前置元数据,包含确认后的风格、语言、宽高比
  4. 如果风格与变体推荐的不同:重新生成
    characters/characters.png
  5. 用户可直接编辑文件进行微调

Step 4: Generate Images

步骤4:生成图像

With confirmed storyboard + style + aspect ratio:
For each page (cover + pages):
  1. Save prompt to
    prompts/NN-{cover|page}-[slug].md
    (in user's preferred language)
  2. Generate image using confirmed style and aspect ratio
  3. 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
:
  1. Generate unique session ID:
    comic-{topic-slug}-{timestamp}
  2. Use same session ID for all pages
  3. Ensures visual consistency across generated images
使用确认后的分镜+风格+宽高比:
针对每一页(封面+内页):
  1. 将提示保存到
    prompts/NN-{cover|page}-[slug].md
    (使用用户偏好的语言)
  2. 使用确认后的风格和宽高比生成图像
  3. 每生成一页后报告进度
图像生成Skill选择:
  • 检查可用的图像生成Skill
  • 如果有多个可用Skill,询问用户偏好
角色参考图处理:
  • 如果Skill支持参考图像:传入
    characters/characters.png
  • 如果Skill不支持参考图像:将
    characters/characters.md
    的内容包含在提示中
会话管理: 如果图像生成Skill支持
--sessionId
:
  1. 生成唯一会话ID:
    comic-{topic-slug}-{timestamp}
  2. 所有页面使用同一个会话ID
  3. 确保生成的图像视觉风格一致

Step 5: Merge to PDF

步骤5:合并为PDF

After all images generated:
bash
npx -y bun ${SKILL_DIR}/scripts/merge-to-pdf.ts <comic-dir>
Creates
{topic-slug}.pdf
with all pages as full-page images.
所有图像生成完成后:
bash
npx -y bun ${SKILL_DIR}/scripts/merge-to-pdf.ts <comic-dir>
生成包含所有全页图像的
{topic-slug}.pdf
文件。

Step 6: Completion Report

步骤6:完成报告

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
漫画创作完成!
标题: [标题] | 风格: [风格] | 页数: [数量] | 宽高比: [比例] | 语言: [语言]
位置: [路径]
✓ 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:
  1. Identify page to edit (e.g.,
    03-page-enigma-machine.png
    )
  2. Update prompt in
    prompts/03-page-enigma-machine.md
    if needed
  3. If content changes significantly, update slug in filename
  4. Regenerate image using same session ID and aspect ratio
  5. Regenerate PDF
使用修改后的提示重新生成特定页面:
  1. 确定要编辑的页面(例如
    03-page-enigma-machine.png
  2. 如有需要,更新
    prompts/03-page-enigma-machine.md
    中的提示
  3. 如果内容变化较大,更新文件名中的别名
  4. 使用同一个会话ID和宽高比重新生成图像
  5. 重新生成PDF

Add New Page

添加新页面

Insert a new page at specified position:
  1. Specify insertion position (e.g., after page 3)
  2. Create new prompt with appropriate slug (e.g.,
    04-page-bletchley-park.md
    )
  3. Generate new page image (same aspect ratio)
  4. Renumber files: All subsequent pages increment NN by 1
    • 04-page-tragedy.png
      05-page-tragedy.png
    • Slugs remain unchanged
  5. Update
    storyboard.md
    with new page entry
  6. Regenerate PDF
在指定位置插入新页面:
  1. 指定插入位置(例如第3页之后)
  2. 创建带有合适别名的新提示(例如
    04-page-bletchley-park.md
  3. 生成新页面图像(使用相同宽高比)
  4. 重命名文件:所有后续页面的NN编号加1
    • 04-page-tragedy.png
      05-page-tragedy.png
    • 别名保持不变
  5. 更新
    storyboard.md
    ,添加新页面条目
  6. 重新生成PDF

Delete Page

删除页面

Remove a page and renumber:
  1. Identify page to delete (e.g.,
    03-page-enigma-machine.png
    )
  2. Remove image file and prompt file
  3. Renumber files: All subsequent pages decrement NN by 1
    • 04-page-tragedy.png
      03-page-tragedy.png
    • Slugs remain unchanged
  4. Update
    storyboard.md
    to remove page entry
  5. Regenerate PDF
删除页面并重编号:
  1. 确定要删除的页面(例如
    03-page-enigma-machine.png
  2. 删除图像文件和提示文件
  3. 重命名文件:所有后续页面的NN编号减1
    • 04-page-tragedy.png
      03-page-tragedy.png
    • 别名保持不变
  4. 更新
    storyboard.md
    ,移除该页面条目
  5. 重新生成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/)
Examples:
  • 00-cover-turing-story.png
  • 01-page-early-life.png
  • 02-page-cambridge-years.png
  • 03-page-enigma-machine.png
Slug rules:
  • Derived from page title/content (kebab-case)
  • Must be unique within comic
  • When page content changes significantly, update slug accordingly
Renumbering:
  • After add/delete, update NN prefix for affected pages
  • Slug remains unchanged unless content changes
  • Maintain sequential numbering with no gaps
文件使用有意义的别名以提高可读性:
NN-cover-[slug].png / NN-page-[slug].png
NN-cover-[slug].md / NN-page-[slug].md (位于prompts/目录下)
示例:
  • 00-cover-turing-story.png
  • 01-page-early-life.png
  • 02-page-cambridge-years.png
  • 03-page-enigma-machine.png
别名规则:
  • 由页面标题/内容生成(短横线分隔格式)
  • 在同一漫画中必须唯一
  • 当页面内容变化较大时,相应更新别名
重编号规则:
  • 添加/删除页面后,更新受影响页面的NN前缀
  • 除非内容变化,否则别名保持不变
  • 保持连续编号,无间隔

Style-Specific Guidelines

特定风格指南

Ohmsha Style (
--style ohmsha
)

Ohmsha风格(
--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.
教育类漫画的额外要求:
  • 默认:直接使用哆啦A梦系列角色 - 无需创建新角色
    • 大雄 (Nobita): 学生角色,充满好奇心的学习者
    • 哆啦A梦 (Doraemon): 导师角色,使用道具讲解概念
    • 胖虎 (Gian): 反派/挑战角色,代表障碍或误解
    • 静香 (Shizuka): 辅助角色,提出澄清问题
  • 仅当明确要求时使用自定义角色:
    --characters "Student:小明,Mentor:教授"
  • 必须使用视觉隐喻(道具、动作场景)- 禁止仅使用对话头像
  • 页面标题:叙事风格,而非“第X页:主题”
参考:详细指南请见
references/ohmsha-guide.md

References

参考资料

Detailed templates and guidelines in
references/
directory:
  • analysis-framework.md
    - Deep content analysis for comic adaptation
  • character-template.md
    - Character definition format and examples
  • storyboard-template.md
    - Storyboard structure and panel breakdown
  • ohmsha-guide.md
    - Ohmsha manga style specifics
  • styles/
    - Detailed style definitions
  • layouts/
    - Detailed layout definitions
详细模板和指南位于
references/
目录:
  • analysis-framework.md
    - 漫画改编的深度内容分析框架
  • character-template.md
    - 角色定义格式和示例
  • storyboard-template.md
    - 分镜结构和分镜拆解
  • ohmsha-guide.md
    - Ohmsha漫画风格细节
  • styles/
    - 详细风格定义
  • layouts/
    - 详细布局定义

Extension Support

扩展支持

Custom styles and configurations via EXTEND.md.
Check paths (priority order):
  1. .content-gen-skills/comic/EXTEND.md
    (project)
  2. ~/.content-gen-skills/comic/EXTEND.md
    (user)
If found, load before Step 1. Extension content overrides defaults.
通过EXTEND.md实现自定义风格和配置。
路径检查(优先级顺序):
  1. .content-gen-skills/comic/EXTEND.md
    (项目级)
  2. ~/.content-gen-skills/comic/EXTEND.md
    (用户级)
如果找到,在步骤1之前加载。扩展内容将覆盖默认设置。