ljg-classic: Ancient Chinese Annotation Card

Workflow Notification

Running the **AnnotateAndRender** workflow in the **ljg-classic** skill to annotate and render the chapter...

Workflow Routing

Workflows/AnnotateAndRender.md

Quick Contract

• Input must clearly specify the original text, book title, and chapter; when the version is unclear, retain the boundaries of variant readings.
• All non-punctuation segments of the original text must have corresponding annotations; do not only pick "key words".
• Cyan is used to explain characters, words, and grammar; vermilion for explaining the actions of entire sentences; ochre only marks variant readings and uncertain parts; chapter interpretations use warm paper with dark ink, and do not use long blue text.
• Interpretations inherit the straightforward Chinese of

  ljg-plain

  and the "Condition—Mechanism—Result, Migration, Boundary" framework of

  ljg-writes

  , but do not display writing scaffolds such as "Interpretation Boundary".
• By default, call the built-in

  image_gen

  to generate a wordless, low-distraction chapter theme image, placed between the chapter title and the original text; if image generation is unavailable, continue to generate a version without the image and explain the situation.
• By default, output a single long PNG of

  1080 × auto

  , while retaining JSON, HTML, and manifest files for review.

Gotchas

• "Character-by-character" means 100% coverage of the original text, not splitting fixed words into meaningless individual characters; set phrases, function words, and interchangeable character relationships are annotated according to the smallest meaningful unit.
• Annotations cannot rewrite the original text. Suspected wrong characters, interchangeable characters, or version differences in the base text are marked with

  variant

  , and cannot be silently replaced.
• If both character annotations and sentence annotations are written as long sentences, the original text will be obscured. Character annotations only solve local reading issues, while sentence annotations only supplement the current action or cause-effect relationship.
• Chapter interpretations are not repetitions of sentence-by-sentence translations, nor collections of golden sentences. They only focus on one core relationship and explain one migratable scenario or failure boundary.
• Boundaries should be naturally integrated into the text, without separate method titles such as "Interpretation Boundary", "Application Boundary", or "Migration Test"; these terms will pull readers out of the content and back to the writing background.
• The top illustration is responsible for condensing the core theme, not retelling the plot. Text, calligraphy, seals, watermarks, and high-saturation religious spectacles are prohibited in the image; overly detailed images will take away the primary reading right of the original text.
• The existence of the PNG file does not mean completion. Must verify the actual size, title and chapter, annotation coverage, page bottom, and the entire image as well as long image slices.
• Fixed image width does not mean fixed font size. When the text volume increases, first increase the page height and adjust line breaks; do not compress the font size of the main text to the point of being unreadable.
• Punctuation cannot be treated as an independent line-break unit. End-of-sentence punctuation and closing quotation marks follow the previous original text token; opening quotation marks at the start of a paragraph follow the next token to avoid orphan lines.

Examples

User: 「/ljg-classic 《道德经》第十六章，逐字注解并讲透」
→ Lock the book title, chapter, and base text
→ Generate character annotations, sentence annotations, and full-chapter interpretation paragraph by paragraph
→ Output a 1080px long PNG with the book title and chapter marked

User: 「把这段《论语·学而》做成文言文夹注图，最后写完整解读」
→ Cover every segment of the original text, mark interchangeable characters and grammar with separate colors
→ Use straightforward Chinese in the interpretation to clarify conditions, mechanisms, and results
→ Retain JSON, HTML, PNG, and acceptance manifest files

User: 「这句古文是什么意思？」
→ Do not trigger ljg-classic
→ Directly provide a short translation or use ljg-plain