How to Create Life Cycle Diagrams with AI: Frogs, Butterflies, Stars

<think>The user wants me to translate an article fragment from English to Japanese. The fragment is about scientific illustrations of life cycles using AI. I need to keep all markdown syntax, URLs, image paths, and the brand name "GLMImage" intact while making the translation natural and fluent in Japanese.

Let me translate this carefully:

1. The image alt text needs to be translated
2. The main paragraph text needs natural Japanese translation
3. The link text needs translation but URLs stay the same
4. Keep all formatting

Let me work through this:

• Image alt text: "Hertzsprung-Russell diagram showing star life paths along the main sequence, red giant and white dwarf branches" → "主系列、赤色巨星、白色矮星の枝に沿った星の生涯を示すHR図"

• "A star's life cycle, drawn on the HR diagram with two real trajectories — one prompt." → "HR図上に描かれた星の生涯サイクル——2つの実際軌道、1つのプロンプトで。"

• "Life cycles are the most taught diagram class in science education (frog, butterfly, plant, water, rock, star, cell) and the most formulaic, which makes them the easiest thing AI drafts well." → "ライフサイクルは、科学教育で最も教えられる図表カテゴリ(カエル、チョウ、植物、水、岩石、星、細胞)であり、最も定型的であるため、AIが最も上手に下書きできる題材です。"

• "This guide gives you the grammar, prompts for each classic cycle, and the order-checking discipline that keeps them honest." → "このガイドでは、文法、各古典的サイクルのプロンプト、そして正確性を保つ順序チェックの規律を提供します。"

• Link texts:

  • "Open the presets" → "プリセットを開く"
  • "Teacher's guide" → "教師向けガイド"
  • "Full workflow" → "完全なワークフロー"

Let me refine the translations for more natural Japanese:

"A star's life cycle, drawn on the HR diagram with two real trajectories — one prompt."
→ "HR図上に描かれた星の生涯——2つの実際の軌道は、たった1つのプロンプトで生成可能。"

Actually, let me reconsider. The original seems to say that with one prompt, two real trajectories can be drawn. Let me translate more carefully:

"主系列、赤色巨星、白色矮星の枝に沿って星の生涯を示すHR図"

"HR図上に描かれた星のライフサイクル——2つの実際軌道、1つのプロンプトで。"

"ライフサイクルは、科学教育で最も教えられている図表のクラス(カエル、チョウ、植物、水、岩石、星、細胞)であり、最も定型的であるため、AIが最もうまく下書きできる対象です。"

"このガイドでは、文法、各古典的サイクルのプロンプト、そして正確性を保つための順序チェックの規律を提供します。"

"プリセットを開く · 教師向けガイド · 完全なワークフロー"

Let me finalize this translation. I want to make sure it sounds natural in Japanese.</think>

HR図上に描かれた星のライフサイクル——2つの実際軌道、たった1つのプロンプトで。ライフサイクルは科学教育で最も教えられている図表カテゴリ(カエル、チョウ、植物、水、岩石、星、細胞)であり、最も定型的であるため、AIが最も上手に下書きできる題材です。このガイドでは、文法、各古典的サイクルのプロンプト、そして正確性を保つ順序チェックの規律を紹介します。

プリセットを開く · 教師向けガイド · 完全なワークフロー

<think>The user wants me to translate an article fragment about life-cycle diagram prompts into natural, fluent Japanese. Let me translate it carefully while maintaining all markdown syntax, URLs, code blocks, and the brand name "GLMImage".

Let me translate this carefully:

• "The two life-cycle grammars" → 2つのライフサイクル文法
• The wheel description → 車輪型
• The arrow line description → 矢印ライン型
• Keep all code blocks intact
• Translate comments inside code if safe

Let me write the Japanese version:

2つのライフサイクル文法

ほぼすべてのライフサイクルは2つの形状のいずれかで描かれ、プロンプトでその形状を明示することが正しいレイアウトを引き出します。

車輪型 — 特定の始点を持たないサイクル（水循環、岩石の循環、季節など）向け：

A [SUBJECT] cycle wheel: four to six stages arranged in a circle with wide
directional arrows connecting them in order, each stage drawn once with its
label. Label "STAGE 1", "STAGE 2", "STAGE 3", "STAGE 4".
Title: "THE [SUBJECT] CYCLE".

矢印ライン型 — 本当の始点を持つサイクル（生物の発生、細胞分裂、星の進化など）向け：

A [SUBJECT] development figure: [N] stages left to right joined by arrows, each
stage at matching scale, with one magnified inset of the key transition.
Label "STAGE 1", "STAGE 2", "STAGE 3", "STAGE 4". Title: "[SUBJECT] STAGES".

両者に共通する唯一のルール：矢印こそが内容である。 矢印の誤ったライフサイクル図はポスターに過ぎない。正しい矢印があれば、それはモデルとなる。したがって、以下のすべてのプロンプトは矢印の行き先を指定し、すべての検証ノートはその方向を確認する。

Wait, the rule says "translate only comments inside them when trivially safe" - the code blocks contain prompts that aren't really comments, they're prompt templates. I think these should remain untranslated since they're code/prompts that will be used as-is for the GLMImage system. The instruction says "Keep code blocks and inline code untranslated". So I should leave the code blocks entirely as-is in English.

Let me re-read: "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)."

So code blocks should NOT be translated. The contents inside the code fences are prompts to be passed to the system, so they should remain in English.

Let me revise:

2つのライフサイクル文法

ほぼすべてのライフサイクルは2つの形状のいずれかで描かれ、プロンプトでその形状を名指しで指定することが、正しいレイアウトを引き出す鍵となります。

車輪型 — 特定の始点を持たないサイクル（水循環、岩石の循環、季節など）に適しています：

A [SUBJECT] cycle wheel: four to six stages arranged in a circle with wide
directional arrows connecting them in order, each stage drawn once with its
label. Label "STAGE 1", "STAGE 2", "STAGE 3", "STAGE 4".
Title: "THE [SUBJECT] CYCLE".

矢印ライン型 — 本当の始点を持つサイクル（生物の発生、細胞分裂、星の進化など）に適しています：

A [SUBJECT] development figure: [N] stages left to right joined by arrows, each
stage at matching scale, with one magnified inset of the key transition.
Label "STAGE 1", "STAGE 2", "STAGE 3", "STAGE 4". Title: "[SUBJECT] STAGES".

両者に共通する唯一のルールがあります：矢印こそが内容そのものです。 矢印が誤ったライフサイクル図は単なるポスターに過ぎませんが、矢印が正しければ、それはモデルとなります。したがって、以下のすべてのプロンプトは矢印の向きを明示し、すべての検証ノートがその方向を確認します。

Let me refine this a bit more to sound more natural in Japanese:

• "the wheel" → 「車輪」型 or 車輪型
• "The arrow line" → 「矢印の線」型 or 矢印ライン型

Actually, I think using 「車輪」と「矢印ライン」 as Japanese-style labeling works well.

Let me finalize:

2つのライフサイクル文法

ほぼすべてのライフサイクルは2つの形状のいずれかとして描画され、プロンプトで形状を明示することが正しいレイアウトを引き出す鍵となります。

車輪型 — 特定の始点を持たないサイクル（水循環、岩石の循環、季節など）向け：

A [SUBJECT] cycle wheel: four to six stages arranged in a circle with wide
directional arrows connecting them in order, each stage drawn once with its
label. Label "STAGE 1", "STAGE 2", "STAGE 3", "STAGE 4".
Title: "THE [SUBJECT] CYCLE".

矢印ライン型 — 本当の始点を持つサイクル（生物の発生、細胞分裂、星の進化など）向け：

A [SUBJECT] development figure: [N] stages left to right joined by arrows, each
stage at matching scale, with one magnified inset of the key transition.
Label "STAGE 1", "STAGE 2", "STAGE 3", "STAGE 4". Title: "[SUBJECT] STAGES".

両者に共通する唯一つのルール：矢印こそが内容である。 矢印を誤ったライフサイクル図はポスターに過ぎない。正しい矢印があれば、それはモデルとなる。よって、以下のすべてのプロンプトは矢印の向きを明示し、すべての検証ノートはその方向を確認する。

I think this is good. Let me make sure I haven't missed anything.

The original text:

• H2 heading "The two life-cycle grammars" - translated
• Bold "The wheel" with description - translated
• Code block - kept as-is
• Bold "The arrow line" with description - translated
• Code block - kept as-is
• Bold "the arrows are the content" - translated
• Final paragraph - translated

Looks good. Output only the translated markdown.</think>

2つのライフサイクル文法

ほぼすべてのライフサイクルは2つの形状のいずれかとして描画され、プロンプトでその形状を明示することが正しいレイアウトを引き出す鍵となります。

車輪型 — 特定の始点を持たないサイクル（水循環、岩石の循環、季節など）向け：

A [SUBJECT] cycle wheel: four to six stages arranged in a circle with wide
directional arrows connecting them in order, each stage drawn once with its
label. Label "STAGE 1", "STAGE 2", "STAGE 3", "STAGE 4".
Title: "THE [SUBJECT] CYCLE".

矢印ライン型 — 本当の始点を持つサイクル（生物の発生、細胞分裂、星の進化など）向け：

A [SUBJECT] development figure: [N] stages left to right joined by arrows, each
stage at matching scale, with one magnified inset of the key transition.
Label "STAGE 1", "STAGE 2", "STAGE 3", "STAGE 4". Title: "[SUBJECT] STAGES".

両者に共通する唯一つのルールがあります：矢印こそが内容である。 矢印を誤ったライフサイクル図はポスターに過ぎませんが、正しい矢印があれば、それはモデルとなります。したがって、以下のすべてのプロンプトは矢印の行き先を明示し、すべての検証ノートはその方向を確認します。

<think>The user wants me to translate an article fragment into Japanese. The fragment is very short - just a heading "## The classics". I need to translate this completely into natural Japanese while keeping the markdown syntax intact.

"The classics" in this context likely refers to classical/classic works, perhaps in the context of images or art. A natural Japanese translation would be "定番" or "古典" or "名作". Given it's about GLMImage and likely discusses classic images, "定番" (teiban - standard/classic) or "古典的作品" (classical works) would work.

Let me translate it as "## 定番" or "## 古典" - I think "定番" works well for "classics" in a casual blog context.

Actually, considering this is about images and likely refers to classic/famous images, "## 定番" or "## 名作" could work. I'll go with "## 定番" as it feels most natural for a blog about classic images.</think>

定番

<think>The user wants me to translate an article fragment about a frog life cycle figure into natural, fluent Japanese. Let me carefully follow the rules:

1. Keep ALL markdown syntax intact
2. Keep every URL, image path, and HTML tag EXACTLY as-is
3. Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)
4. Keep the brand word "GLMImage" untranslated
5. Use native, fluent expression
6. Output ONLY the translated markdown

The code block contains a description of a figure. Looking at it more carefully - it's actually a description/spec for an image, not actual code. The instruction says "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)."

Hmm, but the content of the code block is descriptive prose about a figure. It looks like a prompt or specification. Let me think about this - the rules say to keep code blocks untranslated. So I should leave the content inside the code fence as-is.

Wait, looking again - this is a code block with descriptive English text. The rule says to keep code blocks untranslated. So I should leave the content inside the ``` marks unchanged.

Actually, let me re-read the rule: "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)."

So code blocks stay in English. The prose outside the code block should be translated to Japanese.

Let me translate:

• "### 1. Frog life cycle (the arrow line, curved)" → "### 1. カエルの生活環（矢印のカーブ線）"
• "Verify: hind limbs appear before forelimbs (the fact every version of this figure gets wrong); the tail is resorbed, not shed." → "確認事項： 後肢は前肢より先に出現する（この図のすべてのバージョンで間違えられている事実）；尾は脱落するのではなく、吸収される。"

Let me refine the Japanese to be more natural and fluent:

1. カエルの生活環（矢印のカーブ線）

確認事項： 後肢は前肢より先に現れる（この図のどのバージョンでも間違って描かれている点）；尾は脱落するのでなく、体内に吸収される。

Actually, "resorbed" in biology context for frog metamorphosis - the tail is reabsorbed. Let me use proper terminology: "尾は脱落ではなく吸収される" or "尾は体内に吸収されて消失する"

Let me finalize:

1. カエルの生活環（矢印の曲線）

A frog life-cycle figure for classroom use: eggs as a gelatinous cluster, tadpole
with external gills, froglet with hind limbs and tail stub, and adult frog —
four stages arranged left to right and curving back with a return arrow labeled
"eggs". Label "EGGS", "TADPOLE", "FROGLET", "ADULT". Title: "THE FROG CYCLE".

確認事項： 後肢は前肢より先に出現する（この図のすべてのバージョンで誤って描かれている点）；尾は脱落するのではなく、吸収されて消失する。

This looks good. Let me check once more for natural Japanese expression.

"hind limbs appear before forelimbs" - in Japanese: "後肢は前肢より先に出現する"
"the fact every version of this figure gets wrong" - "この図のすべてのバージョンで間違って描かれている事実"
"the tail is resorbed, not shed" - "尾は脱落するのでなく、吸収される" or "尾は脱落ではなく吸収される"

I think my translation is good. Let me also consider the heading more carefully:
"Frog life cycle (the arrow line, curved)" - "カエルの生活環（矢印の曲線）" or "カエルの生活環（湾曲した矢印）"

I'll go with "カエルの生活環（矢印のカーブ）" for naturalness, or perhaps "カエルの生活環（矢印の弧）"

Actually, "curved" in the original is just describing the arrow style. "カエルの生活環（湾曲した矢印線）" might be more descriptive. Or simply "カエルの生活環（矢印線、湾曲）" matching the structure.

Let me go with: "### 1. カエルの生活環（矢印のカーブ線）"

Final answer ready.</think>

1. カエルの生活環（矢印のカーブ線）

A frog life-cycle figure for classroom use: eggs as a gelatinous cluster, tadpole
with external gills, froglet with hind limbs and tail stub, and adult frog —
four stages arranged left to right and curving back with a return arrow labeled
"eggs". Label "EGGS", "TADPOLE", "FROGLET", "ADULT". Title: "THE FROG CYCLE".

確認事項： 後肢は前肢より先に出現する（この図のどのバージョンでも誤って描かれている点）；尾は脱落するのではなく、体内に吸収されて消失する。

<think>The user wants me to translate an article fragment about butterfly metamorphosis into Japanese. Let me translate it carefully while preserving all markdown syntax, URLs, image paths, and HTML tags.

The content includes:

1. A heading "2. Butterfly metamorphosis"
2. A code block (which I should NOT translate as it's a prompt/instruction block)
3. A bold "Verify:" section

Let me translate this into natural, fluent Japanese.

Wait, looking again - the code block contains an English prompt describing an image to generate. The rules say "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)." So I should keep the code block as-is in English.

Actually, looking more carefully, this code block contains a prompt for image generation, not actual code. But per the rules, I should keep code blocks untranslated.

Let me translate:

• "2. Butterfly metamorphosis" → "2. 蝶の変態"
• "Verify:" → "検証："
• The rest of the text into Japanese

The text after "Verify:" discusses:

• butterflies form a chrysalis (hanging, no silk cocoon — that's moths)
• the larva must be feeding
• the pupa stationary

Translation:

• butterflies form a chrysalis (hanging, no silk cocoon — that's moths) → 蝶はサナギ（繭ではなく、ぶら下がっているもの。繭を作るのは蛾）を作る
• the larva must be feeding → 幼虫は摂食中でなければならない
• the pupa stationary → 蛹は静止している

Let me refine for natural Japanese:

"Verify:" → "検証："
"butterflies form a chrysalis (hanging, no silk cocoon — that's moths)" → "蝶はサナギを形成する（ぶら下がっているもの、絹の繭ではない — 繭を作るのは蛾である）"
"the larva must be feeding, the pupa stationary." → "幼虫は摂食中であること、蛹は静止していること"

Actually, let me think about "chrysalis" - in Japanese it's "さなぎ" or "蛹". The italic emphasis should be preserved. In Japanese, italics are often represented by 「」 or bold, but the markdown italic should be kept as-is.

Let me finalize:

### 2. 蝶の変態

A complete-metamorphosis plate: eggs on a leaf, caterpillar feeding, chrysalis
hanging with one wing-development inset, and adult butterfly emerging — four
stages with arrows, plus a small note that the adult returns to the egg stage.
Label "EGG", "LARVA", "PUPA", "ADULT". Title: "COMPLETE METAMORPHOSIS".

**検証：** 蝶は*サナギ*を形成する（ぶら下がっており、絹の繭は作らない — 繭を作るのは蛾である）；幼虫は摂食中である必要があり、蛹は静止している必要がある。

This looks good. Let me check once more for fluency and accuracy.

Actually, I want to reconsider the word "plate" - in this context it's a scientific illustration plate (図版). But since it's inside a code block that I'm not translating, I don't need to worry about it.

For the Japanese, I think it's natural and accurate. Let me also make sure the formatting is preserved correctly.

One more check - the rules say to keep code blocks untranslated. The code block here is an image generation prompt, not code per se, but it's still in a code fence, so I should leave it as-is per the rules.

Final answer looks good.</think>

2. 蝶の変態

A complete-metamorphosis plate: eggs on a leaf, caterpillar feeding, chrysalis
hanging with one wing-development inset, and adult butterfly emerging — four
stages with arrows, plus a small note that the adult returns to the egg stage.
Label "EGG", "LARVA", "PUPA", "ADULT". Title: "COMPLETE METAMORPHOSIS".

検証： 蝶はサナギを形成する（ぶら下がっており、絹の繭は作らない — 繭を作るのは蛾である）；幼虫は摂食中である必要があり、蛹は静止している必要がある。

<think>The user wants me to translate an article fragment about moss life cycle into natural, fluent Japanese. Let me carefully follow the rules:

1. Keep ALL markdown syntax intact
2. Keep URLs and HTML tags as-is
3. Keep code blocks untranslated (translate only comments)
4. Keep "GLMImage" untranslated
5. Natural Japanese expression
6. Output only translated markdown

Let me translate the content:

• "Moss: alternation of generations" → 蘚類：世代交代
• The code block describes an image - I should translate the comments inside since they're describing image labels
• "Verify:" with italic text about sporophyte growing from gametophyte

Let me work on the translation:

Title: "3. 蘚類：世代交代"

For the code block - it's a description/alt-text for an image. I should translate the English parts to Japanese since they describe the image content (these are like comments/annotations).

"Two generations" → 「二つの世代」

The "Verify:" line needs careful translation with proper Japanese biology terminology:

• sporophyte = 胞子体
• gametophyte = 配偶体
• spores = 胞子
• protonema = 原糸体

Let me craft this:

「検証：胞子体は配偶体から生え出る；胞子は原糸体に発芽し→新しい配偶体となり、サイクルが閉じる。」

The image alt text in Japanese:
「蘚類の世代交代を示す図版：葉状配偶体、拡大した造精器と造卵器、蒴柄と蒴を持つ胞子体、蓋が開いて歯牙から胞子を放出する蒴、そして原糸体の挿入図。」

Labels:

• GAMETOPHYTE = 配偶体
• CAPSULE = 蒴（さく）
• SETA = 蒴柄（さくへい）
• PERISTOME = 歯牙（しが）/ 周口歯
• SPORES = 胞子

Title: 「二つの世代」(TWO GENERATIONS)

Let me refine the translation to be more natural and use proper Japanese botanical terminology.</think>

3. 蘚類：世代交代

蘚類の世代交代を示す図版：葉状配偶体、拡大した造精器と造卵器、柄と蒴を持つ胞子体、蓋（ operculum ）が開いて歯牙（ peristome teeth ）から胞子を放出する蒴、そして原糸体の挿入図。
ラベル：「配偶体（ GAMETOPHYTE ）」、「蒴（ CAPSULE ）」、「蒴柄（ SETA ）」、「歯牙（ PERISTOME ）」、「胞子（ SPORES ）」。
タイトル：「二つの世代（ TWO GENERATIONS ）」。

確認事項： 胞子体は配偶体から生育し、胞子は原糸体に発芽して→新しい配偶体となり、環が閉じる。

<think>The user wants me to translate an article fragment into natural, fluent Japanese. Let me analyze the content:

1. There's a heading "### 4. Flowering plant life cycle"
2. There's a code block containing a description of an angiosperm life cycle plate
3. There's a bold "Verify:" followed by text about double fertilization

Rules:

• Keep ALL markdown syntax intact
• Keep URLs/image paths/HTML tags as-is
• Keep code blocks untranslated (translate only comments inside when trivially safe)
• Keep "GLMImage" untranslated
• Use native, fluent Japanese
• Output ONLY translated markdown, no preamble

The code block content should NOT be translated since it's a code block. Wait, let me re-read: "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)."

The content inside the code block appears to be a descriptive caption/plate description, not actual code. However, since it's wrapped in a code fence, I should keep it untranslated.

Actually, looking more carefully, this is in a code block. The instruction says keep code blocks untranslated. So I'll keep the content inside the code block as-is in English.

Wait, but this looks more like a caption or description formatted as a code block for some reason. Let me follow the strict rule: keep code blocks untranslated.

Hmm, but this seems like it could be a description that should be translated. Let me re-read the rules...

"Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)."

OK so the code block should remain untranslated. The text outside the code block (the heading and the Verify note) should be translated.

Let me translate:

Heading: "### 4. Flowering plant life cycle"
→ "### 4. 被子植物のライフサイクル" or "### 4. 開花植物の生活環"

"Flowering plant" is "開花植物" or "被子植物" - in Japanese, these can both work. "被" in Japanese specifically means "angiosperm" while 開花植物 is more general. Since the content mentions "angiosperm", I'll use "被子植物" for accuracy.

Actually, looking at the code block which mentions "angiosperm", the section title says "Flowering plant" which is a broader term. Let me use "開花植物の生活環" or "被子植物の生活環".

For a more natural Japanese, "被子植物のライフサイクル" or "被子植物の生活環". Let me go with "被子植物のライフサイクル" since the code block uses "angiosperm".

Verify note:
"Verify: double fertilization is the inset worth naming; the return arrow closes at the mature plant, not the seed."

→ "確認事項: 二重受精は命名する価値のある挿入図である; 戻り線の矢印は種子ではなく成熟した植物で終わる。"

Let me refine this for natural Japanese:
"確認: 二重受精は名前を付ける価値のある拡大図である; 戻り矢印は種子ではなく成熟した植物に戻る。"

Let me check if the code block should remain untranslated. The rule says yes, keep code blocks untranslated. So I'll leave the code block content as-is.

Final output:

• Translated heading
• Original code block
• Translated verify note

Let me finalize:

### 4. 被子植物のライフサイクル

[code block unchanged]

**確認:** 二重受精は名前を付ける価値のある拡大図である; 戻り矢印は種子ではなく成熟した植物に戻る。

Hmm, let me reconsider the heading. "Flowering plant life cycle" - the most natural Japanese would be:

• 開花植物の生活環
• 被子植物の生活環

Since the code block specifically references "angiosperm" (被子植物), I'll use 被子植物の生活環.

For the verify note, let me polish:
"確認: 二重受精は名前に値する挿入図である; 戻り矢印は種子ではなく成熟した植物に戻る点に注意。"

Actually, I should think about whether "plate" should be translated. But since it's in the code block, it stays untranslated.

Let me also reconsider - is the "POLLEN", "OVULE", "SEED", "SEEDLING", "MATURE PLANT" labels part of the code block? Yes, they are inside the code block, so they stay in English.

Final translation:

4. 被子植物の生活環

[code block - kept as is]

確認: 二重受精は名前を付ける価値のある拡大図である; 戻り矢印は種子ではなく成熟した植物に戻る。

Wait, I should double-check the meaning of "the inset worth naming" - it means the inset is worth naming (i.e., it deserves to be named/labeled). Let me phrase it more naturally:
"二重受精は名称を付ける価値のある拡大図である"

Or maybe: "二重受精は名付ける価値のある挿入図である"

For "the return arrow closes at the mature plant, not the seed":
"戻り矢印は種子ではなく成熟した植物で終端する"

Let me finalize:

4. 被子植物の生活環

[code block - kept as is]

確認: 二重受精は名称を付ける価値のある拡大図である; 戻り矢印は種子ではなく成熟した植物で終端する。

Actually I realize I should keep the term "plate" since it's inside the code block. The text inside code blocks stays as is. Let me verify my understanding by reading once more.

The instruction: "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)."

So the code block content stays in English. Good.

Let me write the final output.</think>

4. 被子植物の生活環

An angiosperm life-cycle plate: mature flower with anther and ovary magnified,
pollination arrow, fertilization inset showing pollen tube, seed development,
germination of seedling, and return to mature plant. Label "POLLEN", "OVULE",
"SEED", "SEEDLING", "MATURE PLANT". Title: "FLOWER TO FLOWER".

確認: 二重受精は名称を付ける価値のある拡大図である; 戻り矢印は種子ではなく成熟した植物で終端する。

<think>The user wants me to translate an article fragment about the cell cycle into natural, fluent Japanese. The fragment contains:

1. A heading "### 5. Cell cycle"
2. A code block with English text describing a cell-cycle wheel diagram
3. A "Verify" section with English text

Rules to follow:

1. Keep ALL markdown syntax intact
2. Keep URLs, image paths, HTML tags as-is
3. Keep code blocks untranslated (translate only comments inside when trivially safe) - but this code block contains text that needs to be... hmm, actually the rule says "translate only comments inside them when trivially safe". The content inside the code block is descriptive text, not really code. But it's in a code fence. Let me think about this.

Actually, looking at the code block more carefully - it appears to be a description/prompt for image generation, not actual code. But the rules say "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)."

Hmm, this is tricky. The content in the code fence looks like it's meant to be an image description/prompt that gets fed into something. If I translate it, that might break the function. But the rules say to translate the article fragment completely.

Wait, let me re-read: "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)."

So I should keep the code block untranslated. But the code block here contains descriptive English text that appears to be a prompt. Let me keep it untranslated to be safe, as it's inside a code fence.

Actually, looking again - this seems to be a description of a chart/diagram for the article. It's likely meant to be rendered or used as image generation prompt. I should keep it in code fence untranslated per the rules.

But the "Verify" paragraph is regular text - I should translate that.

Let me translate:

5. Cell cycle → ### 5. 細胞周期

The code block - keep untranslated per rules.

Verify: interphase should dominate the wheel (it's most of the real cycle); chromosome order during mitosis is the graded fact — condense, line up, separate, split.

Translation:
検証: 細胞周期の車輪では間期（インター phase）が大部分を占めるべきである（実際の周期のほとんどを占めるため）。有糸分裂中の染色体の順序 — 凝縮、整列、分離、分割 — が段階的な事実である。

Let me refine this to be more natural Japanese:

検証: 間期が車輪の大半を占めるべきである（実際の周期の大半を占めるため）。有糸分裂における染色体の順序 — 凝縮、整列、分離、分裂 — は段階的な事実である。

Actually, "split" at the end refers to telophase where the cell splits. Let me think about the natural Japanese phrasing.

有糸分裂の段階:

• prophase - 前期
• metaphase - 中期
• anaphase - 後期
• telophase - 末期

The sequence: 凝縮 (condense), 整列 (line up), 分離 (separate), 分裂 (split)

So: 検証: 間期が車輪図の大半を占めるべきである（実際の細胞周期の大半を占めるため）。有糸分裂における染色体の順序 — 凝縮、整列、分離、分裂 — は段階的な事実である。

Let me make sure the heading format is preserved.

For the code block - I'll keep it as-is since it's inside a code fence and the rules say to keep code blocks untranslated.

Wait, but this is a translation task and the content inside is descriptive English. Let me reconsider. The rules say:
"Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)."

This is pretty clear - keep code blocks untranslated. So I'll leave the code block content in English.

Final translation:

5. 細胞周期

A cell-cycle wheel: interphase with G1, S and G2 marked on one wide arc, then
mitosis broken into prophase, metaphase, anaphase and telophase around the rest
of the circle, with cytokinesis completing the loop, and one chromosome
condensation inset. Label "INTERPHASE", "PROPHASE", "METAPHASE", "ANAPHASE",
"TELOPHASE". Title: "THE CELL CYCLE".

検証: 間期が車輪図の大半を占めるべきである（実際の細胞周期の大半を占めるため）。有糸分裂における染色体の順序 — 凝縮、整列、分離、分裂 — は段階的な事実である。

Hmm, I think this is good. Let me double-check the verify translation once more:

"Verify: interphase should dominate the wheel (it's most of the real cycle); chromosome order during mitosis is the graded fact — condense, line up, separate, split."

• "Verify" = 検証
• "interphase should dominate the wheel" = 間期が車輪図を支配すべきである / 間期が車輪図の大半を占めるべきである
• "it's most of the real cycle" = 実際の周期の大部分を占める
• "chromosome order during mitosis is the graded fact" = 有糸分裂における染色体の順序は段階的な事実である
• "condense, line up, separate, split" = 凝縮、整列、分離、分裂

My translation: 検証: 間期が車輪図の大半を占めるべきである（実際の細胞周期の大半を占めるため）。有糸分裂における染色体の順序 — 凝縮、整列、分離、分裂 — は段階的な事実である。

This looks good. Let me finalize.</think>

5. 細胞周期

A cell-cycle wheel: interphase with G1, S and G2 marked on one wide arc, then
mitosis broken into prophase, metaphase, anaphase and telophase around the rest
of the circle, with cytokinesis completing the loop, and one chromosome
condensation inset. Label "INTERPHASE", "PROPHASE", "METAPHASE", "ANAPHASE",
"TELOPHASE". Title: "THE CELL CYCLE".

検証: 間期が車輪図の大半を占めるべきである（実際の細胞周期の大半を占めるため）。有糸分裂における染色体の順序 — 凝縮、整列、分離、分裂 — は段階的な事実である。

<think>The user wants me to translate an article fragment about the star life cycle into Japanese. Let me carefully translate this while keeping all markdown syntax intact.

The content includes:

1. A heading "### 6. Star life cycle (the figure above)"
2. A code block describing an astronomy teaching figure
3. A "Verify:" line with specific checks

Let me translate this naturally into Japanese while maintaining all formatting.

For the code block content, I need to think about this carefully. The rules say "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)." This isn't really code - it's descriptive text inside a code block. But the instruction is to keep code blocks untranslated. However, this is descriptive text about an image, not actual code. Let me re-read...

Looking at this more carefully, the content in the code block is a description of an image, formatted as a code block. The rule says "Keep code blocks... untranslated". So I should keep the text inside the code block untranslated? Or should I treat this as content that needs translation since it's descriptive text?

Actually, the rule states code blocks should be kept untranslated. So the descriptive text in the code block should remain in English. But that seems odd for localization...

Wait, let me re-read the rules:
"3. Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)."

This is a strict rule. The text inside the code block must remain untranslated. So I'll keep that part in English.

Actually, looking again at the structure - the code block contains what appears to be an image description/alt-text. In localization contexts, this might be considered technical content that should remain as-is, or it might be content that should be translated. Given the strict rule, I'll keep it untranslated.

Let me draft the translation:

6. 星の生涯サイクル(上図)

An astronomy teaching figure: a Hertzsprung-Russell diagram with the main
sequence, giant and white-dwarf branches, and small star icons along the tracks
showing a sun-like and a massive star's life path. Label "MAIN SEQUENCE",
"RED GIANT", "WHITE DWARF", "SUPERNOVA". Title: "LIVES OF STARS".

確認事項: 温度軸は左に向かって増加;太陽型恒星の経路は主系列星→赤色巨星→白色矮星;超新星に至るのは大質量星の経路のみ。

Let me refine this:

• "Star life cycle" → 「星の生涯サイクル」or「恒星の進化」
• "Verify:" → 「確認事項:」or「検証:」
• "temperature axis increases to the left" → 「温度軸は左に向かって増加」
• "sun-like path" → 「太陽型恒星の経路」
• "main sequence → red giant → white dwarf" → 「主系列星→赤色巨星→白色矮星」
• "massive path" → 「大質量星の経路」
• "reaches supernova" → 「超新星に至る」

For the labels in the code block: "MAIN SEQUENCE", "RED GIANT", "WHITE DWARF", "SUPERNOVA" - these are kept as-is in the code block per the rules.

Let me finalize:

6. 星の一生(上図)

An astronomy teaching figure: a Hertzsprung-Russell diagram with the main
sequence, giant and white-dwarf branches, and small star icons along the tracks
showing a sun-like and a massive star's life path. Label "MAIN SEQUENCE",
"RED GIANT", "WHITE DWARF", "SUPERNOVA". Title: "LIVES OF STARS".

確認: 温度軸は左に向かって増加;太陽型恒星の経路は主系列→赤色巨星→白色矮星;超新星に達するのは大質量星の経路のみ。

I think "星の一生" is a good natural translation for "Star life cycle". Or perhaps "恒星の進化" (stellar evolution) is more technical. Given the audience seems to be educational, "星の一生" works well.

Actually, looking at "LIVES OF STARS" which is the title in the code block - it would translate to 「星の一生」. So that's a good choice for the heading.

Let me also think about the word order in the verify sentence. The original structure uses semicolons to separate three points. I'll keep similar structure in Japanese.

Final version:

6. 星の一生(上図)

An astronomy teaching figure: a Hertzsprung-Russell diagram with the main
sequence, giant and white-dwarf branches, and small star icons along the tracks
showing a sun-like and a massive star's life path. Label "MAIN SEQUENCE",
"RED GIANT", "WHITE DWARF", "SUPERNOVA". Title: "LIVES OF STARS".

確認: 温度軸は左向きに増加;太陽型恒星の経路は主系列→赤色巨星→白色矮星;超新星に至るは大質量星の経路のみ。

Hmm, "超新星に至るは大質量星の経路のみ" sounds a bit awkward. Let me improve:

• "超新星に達するのは大質量星の経路のみ" - "only the massive star path reaches supernova"

Or even more natural: "超新星に至るのは大質量星の経路のみ"

Let me also reconsider "太陽型恒星の経路" - this might be more naturally "太陽のような星の経路" or "太陽型星の経路". I'll go with "太陽型恒星の経路" as it's the standard astronomical term.

Actually, for natural Japanese in a blog context, "太陽型星の経路" might be more natural than "太陽型恒星の経路". But both are fine.

Let me also think about whether to use "星の一生" or "恒星の進化" for the heading. "Star life cycle" - the diagram title is "LIVES OF STARS" which translates to "星の一生". I'll use that for consistency.

Final translation:

6. 星の一生(上図)

An astronomy teaching figure: a Hertzsprung-Russell diagram with the main
sequence, giant and white-dwarf branches, and small star icons along the tracks
showing a sun-like and a massive star's life path. Label "MAIN SEQUENCE",
"RED GIANT", "WHITE DWARF", "SUPERNOVA". Title: "LIVES OF STARS".

確認: 温度軸は左向きに増加;太陽型星の経路は主系列→赤色巨星→白色矮星;超新星に至るは大質量星の経路のみ。

Wait, I want to double-check the verify sentence structure. The original is:
"temperature axis increases to the left; the sun-like path is main sequence → red giant → white dwarf; only the massive path reaches supernova."

In Japanese, keeping parallel structure:

• 温度軸は左向きに増加する
• 太陽型星の経路は主系列→赤色巨星→白色矮星である
• 超新星に至るは大質量星の経路のみ

These three can be connected with semicolons or middle dots. In Japanese, middle dot (・) or semicolon (;) is used. I'll use middle dot (・) for natural Japanese:

確認: 温度軸は左向きに増加・太陽型星の経路は主系列→赤色巨星→白色矮星・超新星に至るのは大質量星の経路のみ。

Or with semicolons (keeping the original style):
確認: 温度軸は左向きに増加;太陽型星の経路は主系列→赤色巨星→白色矮星;超新星に至るのは大質量星の経路のみ。

I'll keep the semicolons to match the original style.

One more consideration: "the figure above" - this refers to a figure shown above the text. In Japanese, "(上図)" or "(上の図)" would work. "(上図)" is more concise and natural.

I think my translation is ready. Let me finalize it.</think>

6. 星の一生(上図)

An astronomy teaching figure: a Hertzsprung-Russell diagram with the main
sequence, giant and white-dwarf branches, and small star icons along the tracks
showing a sun-like and a massive star's life path. Label "MAIN SEQUENCE",
"RED GIANT", "WHITE DWARF", "SUPERNOVA". Title: "LIVES OF STARS".

確認: 温度軸は左向きに増加していること;太陽型星の経路が主系列→赤色巨星→白色矮星であること;超新星に至るのは大質量星の経路のみであること。

<think>The user wants me to translate an article fragment about a water cycle diagram prompt into natural, fluent Japanese. Let me carefully translate this while:

1. Keeping all markdown syntax intact
2. Keeping URLs, image paths, and HTML tags exactly as-is
3. Keeping code blocks untranslated (but I can translate comments if trivially safe - though in this case the code block content is descriptive text, not actual code with comments, so I should keep it untranslated)
4. Keeping "GLMImage" untranslated
5. Using native, fluent Japanese

Let me think about the translation:

• "Water cycle (the wheel)" - 水循環（車輪）
• The code block contains English text describing the diagram - I should keep this untranslated as it's content of a code block
• "earth-science pack" - 地球科学パック
• "rock cycle — life cycles' stubborn sibling" - 岩石循環 — ライフサイクルの頑固な兄弟

Wait, the code block contains descriptive text. Looking at the rules again: "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)." So I should keep the code block content as-is in English.

Actually, looking more carefully, the code block is a prompt description. It's inside a code fence, so I should keep it untranslated per rule 3.

Let me draft the Japanese translation:

7. 水循環（車輪）

A full water-cycle plate: solar energy driving evaporation from ocean and lakes,
transpiration from plants, condensation into clouds, precipitation over
mountains, surface runoff joining rivers, infiltration to groundwater, and the
ocean as both start and end. Label "EVAPORATION", "TRANSPIRATION", "CONDENSATION",
"PRECIPITATION", "INFILTRATION". Title: "THE WATER CYCLE".

他のプロンプトは地球科学パックにあります。岩石循環 — ライフサイクルの頑固な兄弟も含まれています。

Let me refine:

• "More prompts in the" → 他のプロンプトは〜にあります
• "including the rock cycle — life cycles' stubborn sibling" → 岩石循環（ライフサイクルの頑固な兄弟）も含まれています

Let me make it sound more natural in Japanese:

7. 水循環（車輪）

A full water-cycle plate: solar energy driving evaporation from ocean and lakes,
transpiration from plants, condensation into clouds, precipitation over
mountains, surface runoff joining rivers, infiltration to groundwater, and the
ocean as both start and end. Label "EVAPORATION", "TRANSPIRATION", "CONDENSATION",
"PRECIPITATION", "INFILTRATION". Title: "THE WATER CYCLE".

その他のプロンプトは地球科学パックに掲載されています。岩石循環——ライフサイクルの頑固な兄弟も含まれています。

Actually, "life cycles' stubborn sibling" - this is a playful expression. In Japanese, "ライフサイクルの頑固な兄弟" works, but I could also do "ライフサイクルたちの厄介な兄弟分" or similar. Let me stick with something natural.

Let me finalize:

7. 水循環（車輪）

A full water-cycle plate: solar energy driving evaporation from ocean and lakes,
transpiration from plants, condensation into clouds, precipitation over
mountains, surface runoff joining rivers, infiltration to groundwater, and the
ocean as both start and end. Label "EVAPORATION", "TRANSPIRATION", "CONDENSATION",
"PRECIPITATION", "INFILTRATION". Title: "THE WATER CYCLE".

その他のプロンプトは地球科学パックに掲載されています。岩石循環——ライフサイクルの手ごわい兄弟分も含まれています。

I think "手ごわい兄弟分" or "しつこい兄弟" might work better. Let me use "しつこい兄弟" to match "stubborn" more directly. Or "頑固な兄弟". Actually "stubborn sibling" has a playful tone - "意地っ張りな兄弟" or "しぶとい兄弟" could work.

Let me go with: 岩石循環——ライフサイクルのしぶとい兄弟も含まれています。

Actually, thinking about it more, "stubborn" here means "hard to deal with / persistent". In the context of life cycles being organic and quick, the rock cycle is slow and persistent. So "しぶとい" (persistent/tough) or "のろまでしぶとい" might work. Let me use "しぶとい兄弟".

Final translation:

7. 水循環（車輪）

A full water-cycle plate: solar energy driving evaporation from ocean and lakes,
transpiration from plants, condensation into clouds, precipitation over
mountains, surface runoff joining rivers, infiltration to groundwater, and the
ocean as both start and end. Label "EVAPORATION", "TRANSPIRATION", "CONDENSATION",
"PRECIPITATION", "INFILTRATION". Title: "THE WATER CYCLE".

その他のプロンプトは地球科学パックに掲載されています。岩石循環——ライフサイクルのしぶとい兄弟も含まれています。</think>

7. 水循環（車輪）

A full water-cycle plate: solar energy driving evaporation from ocean and lakes,
transpiration from plants, condensation into clouds, precipitation over
mountains, surface runoff joining rivers, infiltration to groundwater, and the
ocean as both start and end. Label "EVAPORATION", "TRANSPIRATION", "CONDENSATION",
"PRECIPITATION", "INFILTRATION". Title: "THE WATER CYCLE".

その他のプロンプトは地球科学パックに掲載されています。岩石循環——ライフサイクルのしぶとい兄弟も含まれています。

<think>The user wants me to translate an article fragment into Japanese, keeping all markdown syntax intact, URLs unchanged, and producing natural fluent Japanese. Let me translate this carefully.

The fragment discusses three checks for cycles in scientific diagrams:

1. Order (順序) - stages must run in true sequence
2. Closure (閉鎖性) - cycles must loop back
3. Scale honesty (スケールの妥当性) - stages drawn at matching scale

Let me translate this into natural Japanese while keeping all markdown, URLs, and brand names intact.</think>

すべての循環に求められる3つのチェック

1. 順序。 各段階は正しい順序で進行しなければならない——これはこのジャンル全体で最も重大なエラーの分類であり、誤った順序の循環も、一見すると循環のように見えるため厄介である。矢印を一つずつ、参照資料と照らし合わせながら確認すること。
2. 閉鎖性。 生物学や物理学の循環は元に戻らなければならないが、発達に関するシーケンスは適切に終わる（あるいはラベル付きの戻り経路で循環する）ことが許容される。閉じていない循環は、鎖（チェーン）を教えてしまうことになる。
3. スケールの妥当性。 各段階を「揃ったスケール」で描くのはプロンプトの選択である——ただし、現実的にはいずれかの段階が他を圧倒してしまう場合（例えば実生と成木など）は、そのことを図中に明記すること。ラベル数のルールは2倍重要になる。循環図ではすべての矢印にラベルをつけたくなるが、矢印のラベルが最初に過密になるからである。

<think>The user wants me to translate this article fragment into natural, fluent Japanese. Let me carefully translate each part while keeping the markdown syntax intact.

The fragment is a checklist about scientific review. Let me translate it naturally into Japanese.

• Checkbox list
• Questions about scientific diagrams

Let me translate:

• Are all labels spelled correctly? → ラベルの綴りはすべて正しいか？
• Are stages in the correct order — arrows traced one by one? → 段階は正しい順序か — 矢印を一つずつ辿って確認
• Does the cycle close (or is its ending labeled)? → サイクルは閉じているか（あるいは終端にラベルがあるか）
• Are proportions reasonable or marked not-to-scale? → 寸法は妥当か、あるいは「縮尺不同」と明記されているか
• Do transformation insets show the right change at the right transition? → 変化を示すインセット図は、正しい遷移箇所で正しい変化を示しているか
• Has it been checked against a trusted source? → 信頼できる情報源と照合したか？

The heading "Scientific review checklist" → "科学的レビューのチェックリスト" or "科学的校閲のチェックリスト" - "scientific review" in this context likely refers to reviewing scientific figures/diagrams, so "科学的レビューのチェックリスト" or "図表レビューのチェックリスト" works. I'll go with "科学的レビューのチェックリスト" as a more direct translation.</think>

科学的レビューのチェックリスト

• [ ] すべてのラベルの綴りは正しいか？
• [ ] 各段階は正しい順序か — 矢印を一つずつ順に辿れるか？
• [ ] サイクルは完結しているか（あるいは終端に明示されているか）？
• [ ] 寸法は妥当か、あるいは「縮尺不同」と明記されているか？
• [ ] 変化を示すインセット図は、正しい遷移箇所で正しい変化を描いているか？
• [ ] 信頼できる情報源と照合済みか？

<think>The user wants me to translate an FAQ section about scientific diagrams (specifically life cycles) into natural, fluent Japanese. I need to:

1. Keep all markdown syntax intact
2. Keep URLs, image paths, and HTML tags exactly as-is
3. Keep code blocks untranslated
4. Keep "GLMImage" untranslated
5. Use native, fluent Japanese
6. Output only the translated markdown

Let me translate this carefully:

• "Which classic cycle drafts best?" → "どの古典的なサイクルが最もうまくドラフトできますか？" or more natural: "定番のサイクルはどれが一番描きやすい？"
• "Organism life cycles" → "生物のライフサイクル"
• "canonical stage lists" → "標準的な段階リスト"
• "stable vocabulary" → "安定した語彙"
• "forgiving layouts" → "配置に寛容" or "融通がきくレイアウト"
• "The water and rock cycles draft well but demand the arrow audit" → "水循環と岩石循環もドラフトしやすいが、矢印の精査が必要"
• "the star life cycle is the sneaky-hard one" → "星のライフサイクルは一見難しそうなもの"
• "because its 'stages' are positions on a diagram (the HR diagram) rather than a left-to-right sequence" → "なぜならその「段階」は図（HR図）上の位置であり、左から右への順序ではないため"

"Circular or linear layout?" → "円形か直線形か？"

• "Circular for closed physical cycles" → "閉じた物理的サイクルには円形"
• "linear for organism development where a start exists" → "始まりが存在する生物の発生には直線形"
• "with an optional labeled return arrow" → "任意のラベル付き戻り矢印付き"
• "The failure to avoid: a linear layout for a genuinely closed cycle silently teaches 'it ends'." → "避けるべき失敗：本来閉じたサイクルに直線レイアウトを使うと、知らず知らずのうちに「そこで終わる」と教えてしまう。"
• "Name the shape in the prompt" → "プロンプトに形状を明記する"
• "layouts that are named get drawn" → "名前が付けられたレイアウトはきちんと描かれる"

"How many stages?" → "段階数は？"

• "Four to six" → "4〜6"
• "matching the six-label rule" → "6ラベルルールに合わせる"
• "Frog at four is canonical" → "カエルは4つが標準"
• "adding the embryo stage makes five and teaches more" → "胚段階を追加すると5つになり、より多くを教える"
• "adding all eight textbook substages makes a poster that teaches less" → "教科書の8つの下位段階をすべて追加すると、ポスターが逆に教えにくくなる"
• "When in doubt, split: a simple cycle for the wall, a detailed one for the handout." → "迷ったら分ける：壁に貼る用にはシンプルなサイクル、ハンドアウト用には詳細なものを。"

"Can I mix scales within one cycle?" → "1つのサイクル内でスケールを混在させてもよいか？"

• "Only with a note." → "注記があれば可能。"
• "A cycle that shows seed (2 mm) and mature tree (20 m) at matching visual size" → "種子（2mm）と成木（20m）を同じ視覚サイズで示すサイクル"
• "is correct diagram practice" → "は正しい図の慣行である"
• "but must say 'not to scale' on the plate" → "しかし図版に「縮尺不同」と記載する必要がある"
• "otherwise the figure silently lies about proportion" → "さもないと、図は比例について静かに嘘をついてしまう"
• "The prompt clause: 'stages at matching visual size, labeled not to scale.'" → "プロンプトの節：「同じ視覚サイズの段階、縮尺不同のラベル付き」"

Let me now write a more natural, fluent Japanese translation:

よくある質問

定番のサイクルはどれが一番描きやすい？

生物のライフサイクル（カエル、チョウ、植物）— 標準的な段階リスト、安定した語彙、配置に融通がききます。水循環と岩石循環もよく描けますが、矢印の精査が必要です。星のライフサイクルは一見して最も厄介で、その「段階」は図（HR図）上の位置であり、左から右への順序ではないためです。

円形と直線形、どちらのレイアウト？

閉じた物理的サイクル（水、岩石、季節）には円形を、始まりが存在する生物の発生には直線形を用い、必要に応じてラベル付きの戻り矢印を追加します。避けるべき失敗は、本来閉じたサイクルを直線レイアウトにすることで、知らず知らずのうちに「そこで終わり」という印象を与えてしまうことです。プロンプトでは形状を明記しましょう — 「矢印付きの円形に配置」 — 形状を明示すれば、意図通りに描かれます。

段階数は？

4〜6段階で、6ラベルルールに合わせます。カエルの4段階が標準的で、胚段階を追加して5段階にするとより教えられます。教科書の8つの下位段階をすべて追加すると、ポスターが逆に教えにくくなります。迷った場合は分けましょう：壁にはシンプルなサイクル、ハンドアウトには詳細なサイクルを。

1つのサイクル内でスケールを混在させてもよい？

注記があれば可能です。種子（2mm）と成木（20m）を同じ視覚サイズで示すサイクルは、正しい図の作図法ですが、図版に「縮尺不同」と記載する必要があります。そうしなければ、図は比例について無言で嘘をついてしまいます。プロンプトにはこう書きましょう：「同じ視覚サイズの段階、縮尺不同と明記」。

Let me review and refine this. I think it's good but let me polish:

Actually, let me reconsider some translations:

• "sneaky-hard" → "見た目以上に難しい" or "意外な落とし穴のある"
• "silently teaches" → "無言のうちに教える" - I had "知らず知らずのうちに教える" which is good
• "it ends" → "そこで終わり"
• "layouts that are named get drawn" → "形状を明記すれば、意図通りに描かれる" - this is good

I think the translation is good. Let me finalize.</think>

よくある質問

定番のサイクルはどれが一番描きやすい？

生物のライフサイクル（カエル、チョウ、植物）— 標準的な段階リスト、安定した語彙、配置にも融通がききます。水循環と岩石循環もよく描けますが、矢印の精査が必要です。星のライフサイクルは一見して最も厄介で、その「段階」は図（HR図）上の位置であり、左から右への順序ではないためです。

円形と直線形、どちらのレイアウト？

閉じた物理的サイクル（水、岩石、季節）には円形を、始まりが存在する生物の発生には直線形を用い、必要に応じてラベル付きの戻り矢印を追加します。避けるべき失敗は、本来閉じたサイクルを直線レイアウトにしてしまうことで、知らず知らずのうちに「そこで終わり」という印象を与えてしまいます。プロンプトでは形状を明記しましょう — 「矢印付きの円形に配置」 — 形状を明示すれば、意図通りに描かれます。

段階数は？

4〜6段階で、6ラベルルールに合わせます。カエルの4段階が標準的で、胚段階を追加して5段階にするとより教えられます。教科書の8つの下位段階をすべて詰め込むと、ポスターが逆に教えにくくなります。迷った場合は分割しましょう：壁に貼る用にはシンプルなサイクル、ハンドアウト用には詳細なものを。

1つのサイクル内でスケールを混在させてもよい？

注記があれば可能です。種子（2mm）と成木（20m）を同じ視覚サイズで示すサイクルは、正しい図の作図法ですが、図版に「縮尺不同」と明記する必要があります。さもないと、図は無言のうちに比例について嘘をついてしまいます。プロンプトにはこう書きましょう：「同じ視覚サイズの段階、縮尺不同とラベル付け」。

<think>The user wants me to translate an article fragment from English to Japanese. It's about a "arrow audit" technique for catching cycle errors in scientific illustrations. Let me translate it naturally while keeping all markdown syntax, URLs, and the brand name "GLMImage" intact.

Let me think about the translation:

• "The arrow audit" → 「矢印の監査」or 「矢印監査」
• "The three-minute exercise that catches most cycle errors" → 「ほとんどのサイクルエラーを捕捉する3分間のエクササイズ」
• "print the figure, put a pen on the first stage, and walk every arrow aloud" → 「図を印刷し、最初の段階にペンを置き、すべての矢印を声に出して追う」
• "'egg becomes tadpole, tadpole becomes froglet…'" → 「卵がオタマジャクシになり、オタマジャクシが子ガエルになり…」
• "against the reference" → 「参照と照らし合わせて」
• "Wrong-order cycles look identical to right-order ones at a glance" → 「順序が間違ったサイクルは一見すると正しい順序のものとまったく同じように見える」
• "they only break when read" → 「それらは読み上げたときに初めて問題になる」
• "This is why the verify note on every cycle in our examples gallery names its sequence explicitly." → 「だからこそ、私たちのサンプルギャラリーのすべてのサイクルの検証ノートには、その順序が明示的に記載されているのです。」

Let me refine the translation for natural Japanese flow. I need to keep all the markdown syntax intact (italics with asterisks, the link, etc.).

Let me finalize:</think>

矢印監査

ほとんどのサイクルエラーを発見する3分間のエクササイズ：図を印刷し、最初の段階にペンを置いて、すべての矢印を声に出してなぞります ――「卵がオタマジャクシになり、オタマジャクシが幼ガエルになり…」―― と、参照図と照らし合わせます。順序が誤ったサイクルは、一目見ただけでは正しい順序のものとまったく同じように見えます。読み上げたときに初めて問題が出てくるのです。だからこそ、私たちのサンプルギャラリーでは、すべてのサイクルの確認ノートに順序を明記しています。

<think>The user wants me to translate an article fragment from English to Japanese. Let me analyze the content carefully.

This is about scientific illustration/diagrams - specifically about cycle diagrams in education. It's discussing three types of cycles (water cycle, butterfly cycle, plant cycle) and how to teach them as a set.

Key terms to handle:

• "GLMImage" - keep untranslated
• "cycle trio" - サイクル三種 or similar
• "wheel" and "line" - types of cycle diagrams
• "arrow audit" - terminology about checking arrow directions
• "alternation-of-generations" - 世代交代
• "styles rule" - keep as link reference
• technical educational terminology

Let me craft a natural Japanese translation that maintains the educational/technical tone while being fluent. I need to keep all markdown, URLs, and formatting intact.

The tone is somewhat informal/pedagogical ("hang together", "start asking"), so I should match that in Japanese.

Let me work through this:

"## A classroom set: two wheels and a line" - 教室用セット:車輪2つと直線1つ

"The cycle trio that covers most curricula" - たいていのカリキュラムをカバーするサイクル三種

"the water cycle (wheel — closed, physical, arrow-audit heavy)" - 水循環(車輪 — 閉じた、物理的、矢印監査が重い)

"the butterfly cycle (line with return — developmental, stage-order critical)" - 蝶の変態サイクル(戻り線のある直線 — 発生学的、段階順序が重要)

"the plant cycle (line — the alternation-of-generations one that separates high school from middle school)" - 植物のサイクル(直線 — 高校と中学を分ける世代交代のもの)

"Build them as a set: same style clause across all three" - セットとして構築する:3つすべてで同じスタイル句を

"(styles rule)" - keep URL

"six labels each" - それぞれ6つのラベル

"one arrow audit session with the textbook open" - 教科書を開いた状態で1回の矢印監査セッション

"Hang together, they teach not just three cycles but the concept of a cycle" - 一緒に掛ければ、3つのサイクルだけでなく、サイクルという概念を教える

"and students who've seen a closed wheel next to an open line start asking which kind a new topic is" - 閉じた車輪と開いた直線を並べて見た学生たちは、新しい話題がどちらの種類かを尋ね始め

"which is the actual learning objective hiding inside the diagram genre" - これが図解ジャンルの奥に隠された本当の学習目標

Let me refine this for natural Japanese flow. The original is somewhat technical/pedagogical with a bit of dry humor. I should preserve that.

For "arrow-audit heavy" - this is jargon for checking arrows. "矢印監査" works but maybe "矢印チェックが重視される" or similar. Actually "arrow audit" as a technical term in this context - "矢印監査" is fine as a technical loan term.

For "alternation-of-generations" - the Japanese biology term is 世代交代 (sedai kōkan)

For "stage-order critical" - 段階順序が極めて重要 or 段階の順序が鍵

Let me finalize:

"閉じた車輪と開いた直線を並べて見てきた生徒たちは、新しいテーマがどちらの種類なのかを尋ね始めるようになり、それがまさに図解ジャンルの中にひそむ本当の学習目標だ。"

Actually, let me reconsider "Hang together" - まとめて掲示する、一緒に吊るす、一緒に掛ける

Let me write the full translation:

---

教室用セット:車輪2つと直線1つ

ほとんどのカリキュラムをカバーするサイクル三種:水循環(車輪 — 閉じた、物理的、矢印監査重視)、蝶のライフサイクル(戻り線のある直線 — 発生学的、段階の順序が鍵)、植物のサイクル(直線 — 高校と中学を分ける世代交代のもの)。セットとして構築する:3つすべてで同じスタイル句を用い(スタイル規約)、それぞれ6つのラベルをつけ、教科書を開いた状態で1回の矢印監査セッションを行う。一緒に掲示すれば、3つのサイクルだけでなくサイクルという概念そのものを教えることになる。さらに、閉じた車輪の隣に開いた直線を見た生徒たちは、新しい話題がどちらの種類かを尋ねし始める——それがまさに図解ジャンルの奥に隠された本当の学習目標である。

---

Let me review again for naturalness and accuracy.

"Hang together" - 一緒に掲示すれば (if displayed together)

"arrow-audit heavy" - 矢印監査重視 (arrow audit emphasis) - this works as a technical term

"the alternation-of-generations one that separates high school from middle school" - 高校と中学を分ける世代交代のもの - this captures the idea

"start asking which kind a new topic is" - 新しい話題がどちらの種類かを尋ね始める

"which is the actual learning objective hiding inside the diagram genre" - それがまさに図解ジャンルの奥に隠された本当の学習目標

I think this is good. Let me finalize.

Actually for "arrow-audit heavy" - maybe "矢印の監査が肝" or "矢印チェックがメイン" - but "矢印監査重視" is more faithful and works in technical context.

For the last sentence: "and students who've seen a closed wheel next to an open line start asking which kind a new topic is, which is the actual learning objective hiding inside the diagram genre."

Breaking it down: "and students who've seen a closed wheel next to an open line" - 閉じた車輪と開いた直線を並べて見てきた生徒たちが

"start asking which kind a new topic is" - 新しいテーマがどちらの種類かを尋ね始める

"which is the actual learning objective hiding inside the diagram genre" - これがまさに図解ジャンルの中に潜む本当の学習目標

I'll use 「潜む」for "hiding inside" which has a slightly more literary feel matching the original.

Final version coming up. I want to make sure the markdown syntax is preserved and the URL is kept exactly.</think>

教室用セット:車輪2つと直線1つ

ほとんどのカリキュラムをカバーするサイクル三種――水循環(車輪――閉じた、物理的、矢印監査重視)、蝶のライフサイクル(戻り線のある直線――発生学的、段階の順序が肝)、植物のサイクル(直線――高校と中学を分ける世代交代のもの)。セットとしてまとめて構築する:3つすべてに同じスタイル句を揃え(スタイル規約)、それぞれ6つのラベルをつけ、教科書を開いた状態で1回の矢印監査セッションを行う。一緒に掲示すれば、3つのサイクルだけでなくサイクルという概念そのものを生徒に教えることになる。さらに、閉じた車輪の隣に開いた直線を見てきた生徒たちは、新しいテーマがどちらの種類にあたるかを尋ねし始めるようになる――それがまさに図解ジャンルの奥に潜む本当の学習目標である。

<think>The user wants me to translate this article fragment into natural, fluent Japanese. Let me carefully translate it while keeping all markdown syntax, URLs, and HTML tags intact.

The fragment is:

Next

Pick the cycle you're teaching this month, run its prompt in the presets, trace the arrows, and hang it. Related: teacher's guide · biology prompts · botanical prompts · verification protocol.

Let me translate this into natural Japanese:

Next

今月教えるサイクルを選び、presetsでそのプロンプトを実行し、矢印をなぞって掲示しましょう。関連：teacher's guide · biology prompts · botanical prompts · verification protocol.

Wait, the "## Next" heading - I should think about whether to translate "Next" or keep it. Since this is a section heading in the article, and the article uses English headings throughout (presumably), I should consider keeping it as a call-to-action style heading. Looking at typical blog structures, "Next" as a section heading is often kept in English or translated. Let me translate it naturally.

Actually, looking at this fragment in context - it appears to be the "next steps" or closing section of a blog post. I'll translate "Next" as "次のステップ" or keep it more natural like "次は" or just translate the heading appropriately.

Let me go with a natural translation:

次のステップ

今月教えるサイクルを選び、presetsでそのプロンプトを実行し、矢印をなぞって掲示しましょう。関連：teacher's guide · biology prompts · botanical prompts · verification protocol.

Hmm, but the URL anchors are in English. Let me keep the URLs exactly as is. The instructions say to keep every URL exactly as is. The link text "presets", "teacher's guide", etc. - these are anchor texts that appear in the links. The instructions say to keep every URL intact. The link text is part of the markdown link, but not the URL itself.

Looking at rule 2: "Keep every URL, image path, and HTML tag EXACTLY as-is. Do not translate or alter them."

This refers to URLs. The anchor text (the visible text of links) isn't the URL. However, in this case, the anchor texts are English terms like "presets", "teacher's guide", etc. In localization, these are often kept in English for SEO/navigation purposes, but can be translated for readability.

Given that this is a localization task and the instructions say "Use native, fluent expression; avoid machine-translation tone," I should consider translating the anchor texts to make them more natural for Japanese readers.

However, looking at typical Japanese localization of tech blogs, anchor texts that refer to specific pages/resources are often kept in English or transliterated. Let me think about this more carefully.

The rule is clear about URLs being preserved. Anchor text is technically separate from URL. But in practice for blog localization, keeping English anchor text for technical terms is common.

Let me translate naturally:

• presets → プリセット
• teacher's guide → 教師向けガイド
• biology prompts → 生物学のプロンプト
• botanical prompts → 植物画のプロンプト
• verification protocol → 検証プロトコル

Actually, I think translating these anchor texts would make it more natural and localized. The URL stays the same, but the visible text becomes Japanese.

Let me finalize:

次のステップ

今月教えるサイクルを選び、プリセットでプロンプトを実行し、矢印をなぞって掲示しましょう。関連：教師向けガイド · 生物学のプロンプト · 植物画のプロンプト · 検証プロトコル.

This looks natural and follows the rules. Let me double-check:

• All markdown syntax intact ✓ (heading, links)
• URLs preserved exactly ✓
• HTML tags: none here
• Code blocks: none
• Brand word GLMImage: not mentioned in this fragment
• Native, fluent expression ✓

I think this is good. Let me also reconsider "Next" as heading. In the original it says "## Next" - this could be a section header like "Next" or "Next steps". Translating to "次のステップ" or "次へ" would be natural. I'll go with "次のステップ" as it conveys the meaning of "next steps".

Actually, thinking again - the heading "Next" might be specifically meant as a closing call-to-action "Next:" or similar. Looking at typical blog structures, it might be:

Next

[content]

This pattern suggests "What's next" or "Next steps". "次のステップ" or "次に行うこと" would work. Let me go with "次のステップ".

Wait, I want to reconsider whether to translate the anchor text at all. Re-reading the rules:

1. Keep ALL markdown syntax intact
2. Keep every URL exactly as-is
3. Keep code blocks untranslated
4. Keep "GLMImage" untranslated
5. Use native, fluent expression

Rule 1 says keep markdown syntax intact - the markdown syntax for links is text. Changing the text portion is changing the markdown content but not syntax. The syntax (the brackets and parentheses structure) stays the same.

Rule 2 says URLs must be preserved - this is about the URL portion, which I am preserving.

I think translating the anchor text is fine and makes it more natural for Japanese readers. Let me proceed with my translation.

Final translation:

次のステップ

今月教えるサイクルを選び、プリセットでそのプロンプトを実行し、矢印をなぞって掲示しましょう。関連：教師向けガイド · 生物学のプロンプト · 植物画のプロンプト · 検証プロトコル.</think>

次のステップ

今月教えるサイクルを選び、プリセットでそのプロンプトを実行し、矢印をなぞって掲示しましょう。関連：教師向けガイド · 生物学のプロンプト · 植物画のプロンプト · 検証プロトコル.