mirror of https://github.com/NousResearch/hermes-agent.git synced 2026-04-25 00:51:20 +00:00

Jim Liu 宝玉 a8beba82d0 refactor(skills): adapt baoyu-comic for Hermes

Port the upstream baoyu-comic skill to Hermes' tool ecosystem, matching
the earlier baoyu-infographic adaptation:

- metadata namespace openclaw -> hermes (+ tags, homepage)
- drop EXTEND.md preferences system (references/config/ removed,
  workflow Step 1.1 removed)
- user prompts via clarify (one question at a time) instead of
  AskUserQuestion batches
- image generation via image_generate instead of baoyu-imagine, with
  aspect-ratio mapping to landscape/portrait/square
- Windows/PowerShell/WSL shell snippets dropped
- file I/O referenced via Hermes write_file/read_file tools
- CLI-style --flags converted to natural-language options and
  user-intent cues (skill matching has no slash command trigger)

Add PORT_NOTES.md documenting the adaptations and a sync procedure.
Art-style/tone/layout reference files are preserved verbatim from
upstream v1.56.1.

2026-04-21 17:50:04 -07:00

2.9 KiB

Raw Blame History

Ohmsha Manga Guide Style

Guidelines for educational manga comics using the ohmsha preset.

Character Setup

Role	Default	Traits
Student (Role A)	大雄	Confused, asks basic but crucial questions, represents reader
Mentor (Role B)	哆啦A梦	Knowledgeable, patient, uses gadgets as technical metaphors
Antagonist (Role C, optional)	胖虎	Represents misunderstanding, or "noise" in the data

Custom characters: ask the user for role → name mappings (e.g., Student:小明, Mentor:教授, Antagonist:Bug怪).

Character Reference Sheet Style

For Ohmsha style, use manga/anime style with:

Exaggerated expressions for educational clarity
Simple, distinctive silhouettes
Bright, saturated color palettes
Chibi/SD (super-deformed) variants for comedic reactions

Outline Spec Block

Every ohmsha outline must start with:

【漫画规格单】
- Language: [Same as input content]
- Style: Ohmsha (Manga Guide), Full Color
- Layout: Vertical Scrolling Comic (竖版条漫)
- Characters: [List character names and roles]
- Character Reference: characters/characters.png
- Page Limit: ≤20 pages

Visual Metaphor Rules (Critical)

NEVER create "talking heads" panels. Every technical concept must become:

A tangible gadget/prop - Something characters can hold, use, demonstrate
An action scene - Characters doing something that illustrates the concept
A visual environment - Stepping into a metaphorical space

Examples

Concept	Bad (Talking Heads)	Good (Visual Metaphor)
Word embeddings	Characters discussing vectors	哆啦A梦拿出"词向量压缩机"，把书本压缩成彩色小球
Gradient descent	Explaining math formula	大雄在山谷地形上滚球，寻找最低点
Neural network	Diagram on whiteboard	角色走进由发光节点组成的网络迷宫

Page Title Convention

Avoid AI-style "Title: Subtitle" format. Use narrative descriptions:

❌ "Page 3: Introduction to Neural Networks"
✓ "Page 3: 大雄被海量单词淹没，哆啦A梦拿出'词向量压缩机'"

Ending Requirements

NO generic endings ("What will you choose?", "Thanks for reading")
End with: Technical summary moment OR character achieving a small goal
Final panel: Sense of accomplishment, not open-ended question

Good Endings

Student successfully applies learned concept
Visual callback to opening problem, now solved
Mentor gives summary while student demonstrates understanding

Bad Endings

"What do you think?" open questions
"Thanks for reading this tutorial"
Cliffhanger without resolution

Layout Preference

Ohmsha style typically uses:

webtoon (vertical scrolling) - Primary choice
dense - For information-heavy sections
mixed - For varied pacing

Avoid cinematic and splash for educational content.

2.9 KiB Raw Blame History Unescape Escape