The original text is the trunk; annotations grow attached to characters and words; the chapter interpretation reconnects the whole chapter into a judgment that can run. The final deliverable is a long PNG image marked with the book title and chapter, delivered to $HOME/Downloads/; the generation and re-verification process remains in the exclusive /tmp workspace.
Workflow Notification
When executing the workflow, output only text notifications:
Running the **AnnotateAndRender** workflow in the **ljg-classic** skill to annotate and render the chapter...
Do not send start, stage, or progress voice; completion voice is handled uniformly by the system.
Workflow Routing
| Workflow | Trigger | File |
|---|---|---|
| AnnotateAndRender | word-by-word annotation, colored interlinear notes, chapter interpretation, generate classical Chinese PNG | Workflows/AnnotateAndRender.md |
Quick contract
- The input must be able to determine the original text, book title, and chapter; when the edition is unclear, preserve the boundaries of textual variants.
- All non-punctuation original text segments have corresponding annotations; do not select only "key words."
- Cyan explains characters, words, and grammar; vermilion explains whole-sentence actions; ochre marks only textual variants and uncertainties; the chapter interpretation uses warm paper and deep ink, not long blue body text.
- The interpretation borrows
ljg-explain's plain Chinese and standards of understanding andljg-writes's "condition—mechanism—result, transfer, boundary"; the output still follows this workflow and does not add extra self-test or writing scaffolding. - By default, invoke the built-in
image_gento generate a wordless, low-distraction chapter-theme illustration, placed between the chapter title and the original text; if the image is unavailable, continue generating a no-image version and explain. - Each run first establishes an exclusive
/tmp/ljg-classic-*workspace; JSON, HTML, manifest, theme illustration, candidate PNG, and overlap QA slices are all placed only in that workspace. - Only after the candidate PNG passes hard acceptance is it copied to
$HOME/Downloads/as the final card; when the user explicitly specifies another final path, this instruction takes precedence. Do not overwrite files with the same name without explicit request.
Gotchas
- "Word-by-word" means 100% coverage of the original text, not splitting fixed words into meaningless individual characters; compounds, function-word roles, and phonetic-loan relationships are annotated by the smallest meaningful unit.
- Annotations must not rewrite the original text. Suspected typos, phonetic loans, or edition differences in the base text are marked with
variantand must not be silently replaced. - If both character/word notes and sentence-meaning notes are written as long sentences, the original text will be drowned out. Character/word notes solve only local reading; sentence-meaning notes supplement only the current action or causality.
- The chapter interpretation is not a repetition of sentence-by-sentence translation, nor a collection of quotable lines. It runs only one main relationship and explains one transferable scenario or failure boundary.
- Boundaries should be written naturally into the article, not set off under methodological headings such as "interpretation boundary," "application boundary," or "transfer test"; these words make readers jump from the content back to the writing backstage.
- The top illustration is responsible for compressing the motif, not retelling the plot. Text, calligraphy, seals, watermarks, and highly saturated religious spectacle are prohibited in the image; too much visual detail will seize the original text's first reading right.
- The existence of a PNG file does not count as completion. The actual dimensions, title and chapter, annotation coverage, page bottom, full image, and long-image slices must be checked.
- Do not render directly to Downloads. First accept the candidate PNG in
/tmp, then copy the final card, and read back the SHA-256 consistency of the candidate and delivered files. - A fixed image width does not mean a fixed font size. When the amount of text increases, first increase the page height and adjust line breaks; do not compress the body font size to the point of being hard to read.
- Punctuation cannot be treated as a unit that can be wrapped independently. Sentence-ending punctuation and closing quotation marks stay with the preceding source token; an opening quotation mark at the start of a paragraph stays with the following token to avoid orphan lines.
Examples
Example 1: Typesetting an entire chapter of classical Chinese
User: 「/ljg-classic 《道德经》第十六章，逐字注解并讲透」
→ 锁定书名、章节与底本
→ 逐段生成字词注、句义注和全章解读
→ 在独占 `/tmp` 工作区完成验收，只把带书名章节的 1080px 长 PNG 交付到 `$HOME/Downloads/`
Example 2: Source text provided by the user
User: 「把这段《论语·学而》做成文言文夹注图，最后写完整解读」
→ 原文逐片段覆盖，通假与语法另行标色
→ 解读用直白中文跑通条件、机制和结果
→ JSON、HTML、manifest、配图和 QA 切片保留在 `/tmp`；最终 PNG 交付到 `$HOME/Downloads/`
Example 3: Translate only one sentence
User: 「这句古文是什么意思？」
→ 不触发 ljg-classic
→ 直接做简短翻译；需要讲透章内概念或原理时使用 ljg-explain