20 Prompts de Diagramas de Física e Engenharia: Forças, Circuitos e Engrenagens

<think>The user wants me to translate an article fragment into natural, fluent Portuguese. I need to keep all markdown syntax, URLs, image paths, HTML tags, code blocks, and the brand word "GLMImage" untranslated. Let me translate this carefully.

The content is about AI-generated scientific illustrations, specifically engineering cutaways. I need to translate it into fluent Brazilian/European Portuguese while maintaining the technical tone.

Let me translate:

• "Wind turbine nacelle cutaway along the drivetrain with rotor hub, main shaft, gearbox, generator and yaw bearing labeled" - this is an image alt text
• "A nacelle cutaway — hub, shaft, gearbox, generator, yaw bearing, all on one drivetrain — from one prompt."
• "Engineering is cutaway country, and cutaways are what AI drafting does best: big machines, named components, clean section views."
• "Here are 20 physics and engineering prompts with labels and verify notes."
• "Open the engineering presets" - link text
• "Full workflow" - link text
• "All 30 examples" - link text
• "One honest boundary first: this works for schematic engineering — machines explained, mechanisms named, energy flows traced. It does not work for exact engineering: real circuit schematics, dimensioned drawings, anything where geometry encodes numbers. For those, generate the explanatory picture, then draw the exact one in a real tool."

Let me create a natural Portuguese translation.</think>

Um corte transversal da nacele — cubo, eixo, caixa de engrenagens, gerador, anel de guinada, tudo em um único trem de força — a partir de um único prompt. Engenharia é o território dos cortes transversais, e cortes transversais são o que a produção com IA faz de melhor: máquinas grandes, componentes nomeados, vistas em seção limpas. Aqui estão 20 prompts de física e engenharia com legendas e notas de verificação.

Abrir os predefinições de engenharia · Fluxo de trabalho completo · Todos os 30 exemplos

Primeiro, um limite honesto: isso funciona para engenharia esquemática — máquinas explicadas, mecanismos nomeados, fluxos de energia traçados. Não funciona para engenharia exata: esquemas de circuitos reais, desenhos dimensionados, qualquer coisa em que a geometria codifica números. Para esses casos, gere a imagem explicativa e depois desenhe a versão exata em uma ferramenta adequada.

<think>The user wants me to translate a fragment of an article into Portuguese. The fragment is just a heading: "## Cutaways and machines". I need to translate it to natural Portuguese while keeping the markdown syntax (##) intact.

"Cutaways and machines" - "Cutaways" could mean "recortes" or "cortes" (in film/production context). "Machines" = "máquinas".

In the context of film/production (which seems likely given "GLMImage" appears to be related to some kind of production tool), "cutaways" typically refers to shots that cut away from the main action. In Portuguese, this could be "cortes" or "recortes".

I'll go with "Cortes e máquinas" as a natural translation.</think>

Cortes e máquinas

<think>The user wants me to translate a fragment of an article into Portuguese. The fragment appears to be about wind turbine components. Let me translate it carefully, keeping all markdown syntax, code blocks, and technical terms appropriately translated.

Let me translate:

1. The heading "Wind turbine nacelle" → "Nacelle de turbina eólica"
2. The code block content - this is describing an image/illustration. I should translate the English content into Portuguese, keeping it in the code block.
3. The bold "Verify:" → "Verificar:"
4. The technical description after that.

Let me be careful with:

• Keep code block syntax intact
• Translate the content inside the code block (since it's descriptive text, not actual code)
• Keep technical accuracy

For the code block content - it's actually a description/prompt for an illustration, not executable code. I should translate this descriptive text into Portuguese while keeping the code fence intact.

Translation:

"Nacelle de turbina eólica"

Code block content:
"Corte transversal de uma nacelle ao longo do trem de força: cubo do rotor recebendo as cargas das pás, eixo principal, multiplicador aumentando a velocidade, gerador e armário do conversor atrás, com o rolamento de yaw na interface com a torre. Rotule 'CUBO DO ROTOR', 'EIXO PRINCIPAL', 'MULTIPLICADOR', 'GERADOR', 'ROLAMENTO DE YAW'. Título: 'O QUE TEM NA NARIZ'."

Hmm, "WHAT'S IN THE NOSE" - in wind turbine context, "nose" can be translated as "nariz" but a more technical Brazilian Portuguese term might be "gondola" or just keep the concept. Actually, the nacelle is sometimes called "gondola" in Portuguese. But "nariz" is the literal translation and it's used in informal contexts. Let me use "gondola" or keep it as is for playfulness... Actually, "o que tem na nacelle" might work better, or keep the playful "nariz".

Let me reconsider. In Portuguese wind energy terminology:

• Nacelle = nacelle (kept as is) or gondola
• Rotor hub = cubo do rotor
• Main shaft = eixo principal
• Gearbox = multiplicador (or caixa de engrenagens)
• Generator = gerador
• Yaw bearing = rolamento de yaw (or mancal de orientação)
• Converter cabinet = armário do conversor
• Tower interface = interface com a torre
• Blade loads = cargas das pás

For "WHAT'S IN THE NOSE" - this is a colloquial/playful title. "O QUE TEM NA NACELLE" or "O QUE HÁ NO NARIZ" - I'll go with a natural translation.

Let me finalize:

Verificar: o fluxo de potência vai cubo → eixo → multiplicador → gerador (a velocidade aumenta, o torque diminui); yaw é a rotação de toda a nacelle, não das pás.

Actually, looking again at the code block - it's clearly describing an illustration with labels. The text is descriptive prose with English labels. I should translate the descriptive prose but the labels themselves (like "ROTOR HUB") - should they be translated? Looking at the rules, code blocks should be kept untranslated except for trivial comments. But this isn't really a code block in the programming sense, it's a code-fenced block of descriptive text. The labels in the description are quoted strings, so they would be the actual text in the image. I think I should translate them since they would appear as Portuguese text in the illustration if it's for a Portuguese version.

Hmm, the rule says "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)." This is a code-fenced block but it's descriptive prose, not code. The labels inside are textual content meant to appear in an image. I think the spirit of the rule is to keep actual code untranslated, but this is descriptive content for an illustration. I'll translate it as it's part of the article content, not actual code.

Let me write the final version:</think>

1. Nacelle de turbina eólica

Corte transversal de uma nacelle ao longo do trem de força: cubo do rotor
recebendo as cargas das pás, eixo principal, multiplicador elevando a
rotação, gerador e armário do conversor logo atrás, com o mancal de yaw na
interface com a torre. Rotular "CUBO DO ROTOR", "EIXO PRINCIPAL",
"MULTIPLICADOR", "GERADOR", "MANCAL DE YAW". Título: "O QUE HÁ NA GÔNDOLA".

Verificar: o fluxo de potência vai cubo → eixo → multiplicador → gerador (a rotação aumenta para cima, o torque diminui); yaw é a rotação de toda a nacelle, não das pás.

<think>The user wants me to translate a fragment of an article into natural, fluent Portuguese. Let me carefully translate it while keeping all markdown syntax, URLs, code blocks, and the brand name "GLMImage" intact.

Let me translate the content:

1. The heading "Fuel cell stack" → "Pilha de células de combustível"
2. The code block (which describes an image prompt) - I should translate the content but keep the code block structure. Actually, looking more carefully, the code block is a descriptive prompt for an image. I should translate the text inside it to Portuguese.
3. The image markdown with the URL - keep URL as-is
4. The verify note - translate to Portuguese

Let me work through this carefully:

• "### 2. Fuel cell stack" → "### 2. Pilha de células de combustível"

• The code block contains a description of an image prompt. I should translate it:
  "A fuel-cell stack cutaway: repeating membrane-electrode-assemblies and bipolar
  plates, hydrogen entering the anode channel, oxygen the cathode channel, protons
  crossing the membrane, and electrons forced through an external circuit lighting
  a bulb. Label "MEA", "BIPOLAR PLATE", "ANODE", "CATHODE", "EXTERNAL CIRCUIT".
  Title: "STACK ANATOMY"."

→ "Uma vista em corte de uma pilha de células de combustível: conjuntos membrana-eletrodo e placas bipolares repetidos, hidrogênio entrando no canal do ânodo, oxigênio no canal do cátodo, prótons atravessando a membrana e elétrons forçados por um circuito externo acendendo uma lâmpada. Rotular "MEA", "PLACA BIPOLAR", "ÂNODO", "CÁTODO", "CIRCUITO EXTERNO". Título: "ANATOMIA DA PILHA"."

• The image markdown stays as-is (URL preserved)
• "Verify: protons cross the membrane, electrons cannot — that's the whole figure; H₂ in at the anode, O₂ at the cathode." → "Verificar: os prótons atravessam a membrana, os elétrons não podem — essa é a ideia central da figura; H₂ entra no ânodo, O₂ no cátodo."

Let me make sure the code block is properly formatted and the Portuguese reads naturally.</think>

2. Pilha de células de combustível

Vista em corte de uma pilha de células de combustível: conjuntos membrana-eletrodo e
placas bipolares repetidos, hidrogênio entrando no canal do ânodo, oxigênio no canal
do cátodo, prótons atravessando a membrana e elétrons forçados por um circuito externo
acendendo uma lâmpada. Rotular "MEA", "PLACA BIPOLAR", "ÂNODO", "CÁTODO", "CIRCUITO EXTERNO".
Título: "ANATOMIA DA PILHA".

Verificar: os prótons atravessam a membrana, os elétrons não podem — essa é a essência do esquema; H₂ entra no ânodo, O₂ no cátodo.

<think>The user wants me to translate an article fragment into Portuguese. Let me carefully translate it while keeping all markdown syntax, URLs, image paths, and HTML tags intact. I also need to keep the brand "GLMImage" untranslated and the code block untranslated.

Let me translate:

"Turbofan engine cutaway" → "Corte de um motor turbofan" or "Vista em corte de um motor turbofan"

The code block should remain untranslated.

"Verify" → "Verifique" or "Verificar"

Let me produce a natural, fluent Portuguese translation.</think>

3. Corte de um motor turbofan

A turbofan engine cutaway from intake to exhaust: fan, low-pressure and
high-pressure compressors, combustion chamber, turbines, and nozzle, with airflow
paths split into bypass and core. Label "FAN", "COMPRESSOR", "COMBUSTOR",
"TURBINE", "BYPASS". Title: "SUCK, SQUEEZE, BANG, BLOW".

Verifique: o duto de derivação (bypass) contorna o núcleo; a combustão ocorre entre o compressor e a turbina.

<think>The user wants me to translate a fragment of an article about bicycle drivetrains into Portuguese. I need to maintain all markdown syntax, URLs, image paths, and code blocks exactly as they are. The code block contains a description of a mechanical figure - I should not translate the code block content itself (it's essentially a description/specification), but the surrounding markdown text and the "Verify" line should be translated to Portuguese.

Wait, let me re-read the rules. Rule 3 says "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)." So the code block stays in English.

The labels in the code block like "CHAINRING", "CASSETTE", "DERAILLEUR", "JOCKEY WHEEL" are part of the code block, so they stay untranslated.

The image alt text "Bicycle drivetrain with cassette and derailleur labeled" - this is an image path/alt text. Rule 2 says keep URLs, image paths, and HTML tags exactly as-is. The alt text is part of the markdown image syntax. I think I should keep it as-is since it's image-related metadata. Actually, alt text is meant to describe the image for accessibility - it's not a URL or path per se, but it's tied to the image. To be safe and follow rule 2 strictly (which mentions image path), I'll keep the alt text as-is.

The "Verify:" line and the bold "Verify:" should be translated.

Let me translate:

"### 4. Bicycle drivetrain" → "### 4. Transmissão de bicicleta"

The code block stays in English.

"" - keep as-is

"Verify: the chain's upper run is under tension (it pulls); ratio inset must show teeth counts that divide correctly." → "Verificar: o trecho superior da corrente está sob tensão (puxa); o detalhe do ratio deve mostrar contagens de dentes que se dividam corretamente."

Let me refine the Portuguese:

• "Transmissão de bicicleta" is good for drivetrain
• "Bicycle drivetrain" could also be "Sistema de transmissão de bicicleta" but "Transmissão de bicicleta" is concise and natural
• "Verify" → "Verificar"
• "the chain's upper run is under tension (it pulls)" → "o trecho superior da corrente está sob tensão (puxa)" or "o lance superior da corrente está sob tensão (traciona)" - "traciona" might be more technical
• "ratio inset must show teeth counts that divide correctly" → "o detalhe do ratio deve mostrar contagens de dentes que se dividam corretamente" - "ratio" in Portuguese cycling context is often kept as "ratio" or "relação". The English text uses "gear-ratio" and "ratio inset". I'll use "relação" or keep "ratio" - in Brazilian Portuguese cycling terminology, "relação de transmissão" is common. I'll use "relação" or "ratio". Actually, the term is technical and "ratio" is widely understood in cycling context. But to be more Portuguese, "relação" would be better.

Let me write: "o detalhe da relação deve mostrar a contagem de dentes que se divide corretamente"

Actually, re-reading: "ratio inset must show teeth counts that divide correctly" - "teeth counts that divide correctly" means the tooth numbers should be divisible (mathematically). So: "o detalhe da relação deve mostrar contagens de dentes que se dividam corretamente" or "que se dividem corretamente" (present indicative vs subjunctive - here it's a statement of requirement, but after "deve mostrar" which expresses requirement, the subordinate clause can use either; the subjunctive "se dividam" or indicative "se dividem" both work, but since it's stating a requirement that must be met, subjunctive might be slightly more appropriate, though indicative is also fine).

I'll go with: "o detalhe da relação deve mostrar contagens de dentes que se dividam corretamente" or use indicative "se dividem" - both are acceptable. Let me use "se dividam" to match the subjunctive mood often used in such specifications, or "se dividem" for simplicity. Actually, since the main clause uses present indicative "deve", the subordinate clause should typically also be indicative: "que se dividem corretamente".

Final translation:
"Verificar: o lance superior da corrente está sob tensão (traciona); o detalhe da relação deve mostrar contagens de dentes que se dividem corretamente."

Or with "trecho superior" instead of "lance superior":
"Verificar: o trecho superior da corrente está sob tensão (puxa); o detalhe da relação deve mostrar contagens de dentes que se dividem corretamente."

I think "trecho superior" is clearer. And "puxa" or "traciona" - "tracionar" is more technical for tension in mechanics. "Puxa" is more colloquial but also used. Let me use "traciona" or keep "puxa" since "it pulls" is "puxa" in Portuguese.

Actually "the chain's upper run is under tension (it pulls)" - parenthetical explains "under tension" with "it pulls" meaning the chain is pulling/taut. "Está sob tensão (traciona)" or "(puxa)". "Traciona" is better for a drive line context. But "puxa" is the direct translation of "pulls".

I'll go with: "Verificar: o trecho superior da corrente está sob tensão (traciona); o detalhe da relação deve mostrar contagens de dentes que se dividem corretamente."

Wait - "relação inset" or "ratio inset" - the word "inset" means a smaller image/diagram inserted into the main figure. In Portuguese: "detalhe", "recorte", "inserto". "Detalhe" works well. "Quadro inserido" is also possible but "detalhe" is concise.

Let me finalize:

4. Transmissão de bicicleta

[code block - unchanged]

[image - unchanged]

Verificar: o trecho superior da corrente está sob tensão (traciona); o detalhe da relação deve mostrar contagens de dentes que se dividem corretamente.

This looks good. Natural Portuguese, technical terminology appropriate, all formatting preserved.</think>

4. Transmissão de bicicleta

A mechanical figure of a bicycle drivetrain: crankset with chainrings, chain
wrapping the rear cassette, rear derailleur cage with jockey wheels, and a
gear-ratio calculation inset comparing two chainring-cog pairs.
Label "CHAINRING", "CASSETTE", "DERAILLEUR", "JOCKEY WHEEL".
Title: "THE DRIVE LINE".

Verificar: o trecho superior da corrente está sob tensão (traciona); o detalhe da relação deve mostrar contagens de dentes que se dividem corretamente.

<think>The user wants me to translate a fragment into Portuguese. The fragment is just "## Materials" which is a markdown heading. I'll translate it to "## Materiais" in Portuguese.</think>

Materiais

<think>The user wants me to translate the article fragment into Portuguese. Let me carefully translate everything while keeping:

1. Markdown syntax intact
2. URLs exactly as-is
3. Code blocks untranslated
4. "GLMImage" brand untranslated
5. Natural, fluent Portuguese

Let me translate the content:

The heading "Carbon fiber laminate" → "Laminado de fibra de carbono"

The code block contains a prompt for image generation. Looking at the instructions, it says "Keep code blocks and inline code untranslated". However, this appears to be a descriptive text for an image/diagram. Let me re-read the rules...

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

This is a code block (fenced with ```), so I should keep it untranslated. But wait - this looks more like a text description/prompt rather than actual code. However, the rule is clear - keep code blocks untranslated. So I'll leave the code block as-is.

Actually, looking again, the description is in English and seems to be a prompt for generating a diagram. Since it's in a code block, per rule 3, I should keep it untranslated.

Let me translate the rest:

"Caption" text would be the image alt text and any surrounding text. Looking at the original, there's:

• Heading: "### 5. Carbon fiber laminate"
• Code block (untranslated per rule 3)
• Image markdown with alt text

The alt text: "Carbon fiber laminate exploded view with plies labeled"
This is inside the image markdown . The alt text is part of the markdown image syntax. I should consider whether to translate this. The rule says "Keep every URL, image path, and HTML tag EXACTLY as-is. Do not translate or alter them."

The alt text in markdown is the part inside ![...]. Technically the URL is the part in parentheses. The alt text in brackets could be considered separate. However, image alt text typically describes the image and is usually translated for accessibility purposes. But the strictest reading would be to keep it as-is too.

Hmm, let me re-read: "Keep every URL, image path, and HTML tag EXACTLY as-is."

The image path is the URL. The alt text isn't really a URL or image path or HTML tag. But to be safe and maintain professional quality, I should probably translate the alt text as it's descriptive text, not a technical element.

Actually, in localization practice, image alt text IS typically translated because it's user-facing content. So I'll translate it.

Translated alt text: "Vista explodida de laminado de fibra de carbono com camadas rotuladas"

Let me write out the full translation:

5. Laminado de fibra de carbono

[Code block - untranslated]

Wait, I need to think about the code block again. The code block contains an English prompt. The rule says to keep code blocks untranslated. So I'll leave it as-is.

Actually, I should reconsider. This isn't really code - it's a text description/prompt. But it IS in a code fence, which marks it as something to preserve. The rule is explicit: "Keep code blocks and inline code untranslated". So I'll leave it.

Final translation:</think>

5. Laminado de fibra de carbono

An exploded view of a carbon-fiber composite laminate: stacked plies at
alternating zero and ninety degree orientations, an inset of one woven ply, and a
side view of the cured stack with a magnified fiber-matrix interface.
Label "PLY", "WEAVE", "MATRIX", "INTERFACE". Title: "PLY BY PLY".

<think>The user wants me to translate a fragment of an article into Portuguese. Let me analyze the content:

1. There's a heading "### 6. Carbon nanotube chirality" - needs translation
2. There's a code block with image description - needs translation
3. There's an image with alt text - alt text needs translation, but the URL stays
4. There's a "Verify" note - needs translation

Let me translate this naturally into Portuguese:

• "Carbon nanotube chirality" → "Quiralidade de nanotubos de carbono"
• "A materials figure of carbon nanotubes..." → The whole description needs to be in Portuguese
• "Verify:" → "Verificar:" or "Verificação:"
• The alt text needs translation

Let me write this out:

### 6. Quiralidade de nanotubos de carbono

Uma figura de materiais sobre nanotubos de carbono: uma folha de grafeno enrolada mostrando como
o ângulo de enrolamento determina o tipo de tubo, três tubos resultantes marcados como metálicos ou
semicondutores, e um feixe agrupado de tubos paralelos. Rótulos "ÂNGULO DE ENROLAMENTO",
"METÁLICO", "SEMICONDUTOR", "FEIXE". Título: "A QUIRALIDADE IMPERA".

![Figura de quiralidade de nanotubos de carbono com ângulo de enrolamento rotulado](https://img.glmimage.app/uploads/assets/blog/physics-engineering-diagram-prompts--en-inline-5-v4.webp)
**Verificar:** a quiralidade corresponde à direção de enrolamento na folha — os tubos marcados devem corresponder aos ângulos desenhados.

Let me refine this for natural fluency in Portuguese. The phrase "Chirality Rules" could be translated as "A Quiralidade Manda" or "A Quiralidade Impera" or kept more literally. Let me think...

"CHIRALITY RULES" - this is a play on words, common in English. In Portuguese, it could be:

• "A QUIRALIDADE IMPERA"
• "QUIRALIDADE REGE"
• "A QUIRALIDADE MANDA"

I'll go with something natural. "A QUIRALIDADE REGE" sounds good, or "QUIRALIDADE IMPERA". Let me use "A QUIRALIDADE REGE" - it flows nicely.

Actually, looking again, "CHIRALITY RULES" is a common idiom (like "X rules") meaning "X is dominant/important". In Portuguese it could be "A QUIRALIDADE MANDA" or "A QUIRALIDADE REGE". Let me use "A QUIRALIDADE REGE".

For the labels:

• "ROLL ANGLE" → "ÂNGULO DE ENROLAMENTO"
• "METALLIC" → "METÁLICO"
• "SEMICONDUCTING" → "SEMICONDUTOR"
• "BUNDLE" → "FEIXE"

These are technical terms that should be kept consistent with their usual translations in materials science in Portuguese.

Let me finalize:</think>

6. Quiralidade de nanotubos de carbono

Uma figura de materiais sobre nanotubos de carbono: uma folha de grafeno enrolada mostrando como
o ângulo de enrolamento determina o tipo de tubo, três tubos resultantes marcados como metálicos ou
semicondutores, e um feixe agrupado de tubos paralelos. Rótulos "ÂNGULO DE ENROLAMENTO",
"METÁLICO", "SEMICONDUTOR", "FEIXE". Título: "A QUIRALIDADE REGE".

Verificar: a quiralidade corresponde à direção de enrolamento na folha — os tubos marcados devem corresponder aos ângulos desenhados.

<think>The user wants me to translate a heading fragment into Portuguese. The fragment is "## Forces and mechanisms" which is a markdown heading. I need to translate it completely and naturally into Portuguese while keeping the markdown syntax intact.

"## Forces and mechanisms" translates to "## Forças e mecanismos" in Portuguese.

Since this is just a heading with no other content, I'll output just the translated heading.</think>

Forças e mecanismos

<think>The user wants me to translate an article fragment about physics (free-body diagram) into Portuguese. Let me carefully translate while preserving all markdown, code blocks, and the brand name "GLMImage".

Let me translate this carefully:

• "Free-body diagram, block on incline" → "Diagrama de corpo livre, bloco em plano inclinado"
• The code block describes a physics diagram - I should keep this in English since it's a code block, but the user says "translate only comments inside them when trivially safe". This is a description/caption, not code or comments. Hmm, but it's inside a code fence. Let me re-read rule 3: "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)."

So I should keep code blocks untranslated. The content inside is a description, not code per se, but it's wrapped in a code fence. I'll keep it untranslated.

Wait, but it's a description of an image. Let me think about this. The user has wrapped this descriptive text in a code fence. According to rule 3, code blocks should be kept untranslated. So I'll keep the content of the code block in English.

Actually, looking more carefully, this seems to be an image alt-text or description that's wrapped in a code block. Rule 3 says keep code blocks untranslated. So I'll leave it as is.

For the "Verify" line - this is a verification note. Let me translate it:

• "Verify:" → "Verificar:" or "Verifique:"
• "weight points to Earth's center (straight down), not perpendicular to the slope" → "o peso aponta para o centro da Terra (para baixo), não perpendicular à rampa"
• "the most common physics-figure error there is" → "o erro mais comum em figuras de física nesse caso"

Let me put it all together.</think>

7. Diagrama de corpo livre, bloco em plano inclinado

A physics free-body diagram: a block on a 30-degree incline with three clean
vectors — weight straight down, normal force perpendicular to the surface, and
friction along the surface opposing sliding — plus a small inset resolving weight
into parallel and perpendicular components. Label "WEIGHT", "NORMAL FORCE",
"FRICTION". Title: "FORCES ON AN INCLINE".

Verificar: o peso aponta para o centro da Terra (exatamente para baixo), e não perpendicular à rampa — o erro mais comum em figuras de física nesse contexto.

<think>The user wants me to translate an article fragment about gear trains into natural, fluent Portuguese. Let me analyze what needs to be translated:

1. The heading "Gear train" - translate to Portuguese
2. The code block content (alt text/description) - the figure description should be translated, but it's inside a code block. The instructions say "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)."

Wait, let me re-read this. The code block here contains what looks like alt text/description content for an image, not actual code. But the instruction says to keep code blocks untranslated. However, this is a figure description/caption in a code block format.

Looking at it more carefully, the content inside the code block is a description of a figure, not actual programming code. It's descriptive text about a gear-train figure. The instruction says "Keep code blocks and inline code untranslated" - so I should keep it untranslated.

Actually, let me reconsider. The instructions say to keep code blocks untranslated. But this content is clearly descriptive prose meant to be read, not code. However, I should follow the rules strictly. The code block format is preserved, so the content inside should remain in English.

Hmm, but the rule also says "translate only comments inside them when trivially safe." There are no comments in this block - it's all descriptive text.

Let me re-read the rules:

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

So I should keep the code block content untranslated. But wait, this is a figure description, which is the content that needs to be displayed to readers. If I don't translate it, Portuguese readers won't understand the figure description.

Let me think about this more carefully. The content inside the code block is:

A gear-train figure: driver and driven spur gears meshing with an idler between
them, rotation arrows on each, a ratio annotation, and one gear-tooth mesh inset
showing the involute contact. Label "DRIVER", "IDLER", "DRIVEN", "MESH".
Title: "GEARS IN TRAIN".

This appears to be alt text for an image or a figure caption specification. Since it's in a code block, by the rules, I should keep it untranslated. But this would leave it in English in a Portuguese article.

Actually, I think the safest interpretation is: the code block format must be preserved (```), and the content inside should be kept as-is per rule 3. The instructions are clear.

Now for the other parts:

• "Gear train" → "Trem de engrenagens" or "Trens de engrenagens"
• "Verify:" → "Verificar:" or "Verifique:"
• "adjacent gears counter-rotate; the idler changes direction but not ratio." → Portuguese translation

Let me translate:

• "Gear train" → "Trem de engrenagens" (this is the standard term in Portuguese mechanical engineering)
• "Verify:" → "Verifique:" or "Verificar:"
• "adjacent gears counter-rotate; the idler changes direction but not ratio." → "engrenagens adjacentes giram em sentidos opostos; a engrenagem intermediária (idler) muda a direção, mas não a relação."

Actually, looking at the content more carefully, the code block contains the figure description/alt text. In many technical documentation contexts, the alt text and figure descriptions are meant to be translated along with the article. However, the rules explicitly say to keep code blocks untranslated.

I'll follow the rules strictly and keep the code block content in English, while translating the surrounding prose.

Let me finalize the translation:

8. Trem de engrenagens

[Keep as-is per rules]

Verifique: engrenagens adjacentes giram em sentidos opostos; a engrenagem intermediária (idler) muda a direção, mas não a relação de transmissão.

Wait, I need to reconsider. Looking at the code block content again - this is clearly descriptive text about a figure (an image), formatted as a code block for some reason in the original. It's not actual code.

But the rules are explicit: "Keep code blocks and inline code untranslated". So I must keep it untranslated.

However, I should consider that the terms "DRIVER", "IDLER", "DRIVEN", "MESH" are labels in the figure, so they might be kept in English even if the description was translated. But since the whole block is to be kept untranslated, they stay as-is.

Let me provide the translation:

8. Trem de engrenagens

A gear-train figure: driver and driven spur gears meshing with an idler between
them, rotation arrows on each, a ratio annotation, and one gear-tooth mesh inset
showing the involute contact. Label "DRIVER", "IDLER", "DRIVEN", "MESH".
Title: "GEARS IN TRAIN".

Verifique: engrenagens adjacentes giram em sentidos opostos; a engrenagem intermediária muda a direção, mas não a relação de transmissão.

Hmm, "idler" in Portuguese mechanics is often kept as "idler" or translated as "engrenagem intermediária" or "engrenagem parasita" (though "parasita" has a negative connotation). "Polia intermediária" or "roda intermediária" are also used. In the context of gears, "engrenagem intermediária" is most common.

Actually, looking at the original text, it uses "idler" as a technical term. In Brazilian Portuguese mechanical engineering, "engrenagem intermediária" or simply keeping "idler" is common. Let me use "engrenagem intermediária" as it's more descriptive.

Let me also check: "counter-rotate" means to rotate in opposite directions. In Portuguese: "girar em sentidos opostos" or "contra-girar" (less common). "Girar em sentidos opostos" is more natural.

Final translation:

8. Trem de engrenagens

[unchanged code block]

Verifique: engrenagens adjacentes giram em sentidos opostos; a engrenagem intermediária (idler) muda a direção, mas não a relação.

I think this is good. Let me write the final output.</think>

8. Trem de engrenagens

A gear-train figure: driver and driven spur gears meshing with an idler between
them, rotation arrows on each, a ratio annotation, and one gear-tooth mesh inset
showing the involute contact. Label "DRIVER", "IDLER", "DRIVEN", "MESH".
Title: "GEARS IN TRAIN".

Verifique: engrenagens adjacentes giram em sentidos opostos; a engrenagem intermediária (idler) inverte o sentido de rotação, mas não altera a relação de transmissão.

<think>The user wants me to translate an article fragment from English to Portuguese. The fragment is about a four-stroke engine cycle. Let me translate it carefully, keeping all markdown syntax intact.

The text includes:

1. A heading "Four-stroke engine cycle"
2. A code block describing an image
3. A bold "Verify:" line with instructions

Let me translate this naturally into Portuguese while keeping the markdown structure intact.

"Four-stroke engine cycle" → "Ciclo do motor a quatro tempos"

The code block content describes an image, which should remain in English as it's a technical description of a visual. Actually, let me reconsider - the instructions 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.

"Verify: intake valve open only on intake, exhaust only on exhaust; spark belongs in the power stroke's start." → "Verificar: válvula de admissão aberta somente na admissão, escapamento somente no escapamento; a faísca pertence ao início do tempo de combustão."

Let me refine the Portuguese translation to be natural and fluent.</think>

9. Ciclo do motor a quatro tempos

A four-panel row of the four-stroke cycle: intake, compression, power, exhaust —
each panel showing piston position, valve state and a motion arrow, with the
crankshaft angle noted beneath. Label "INTAKE", "COMPRESSION", "POWER",
"EXHAUST". Title: "FOUR STROKES".

Verificar: válvula de admissão aberta somente na admissão, válvula de escapamento aberta somente no escapamento; a faísca pertence ao início do tempo de combustão.

<think>The user wants me to translate a blog fragment into Portuguese. However, I notice the user only provided a heading "## Electricity, schematic-style" and nothing else. There's no actual article content to translate beyond this heading.

I should translate just this heading since that's the only content provided. Let me provide a natural Portuguese translation.</think>

Eletricidade, em estilo esquemático

<think>The user wants me to translate an article fragment into Portuguese. Let me look at the content:

1. A heading "### 10. Simple circuit"
2. A code block containing a prompt for image generation
3. A verification note with bold text

I need to:

• Translate the heading
• Keep the code block content untranslated (it's an image generation prompt in English)
• Translate the verification note
• Keep markdown syntax intact
• Keep the brand "GLMImage" untranslated (not mentioned here but good to note)

Let me translate:

Heading: "### 10. Simple circuit" → "### 10. Circuito simples"

The code block contains an image generation prompt - I should keep this untranslated as per the rules about code blocks.

Verification note: "Verify: the LED symbol must point along current flow; conventional current leaves the positive terminal."
→ "Verificar: o símbolo do LED deve apontar ao longo do fluxo de corrente; a corrente convencional sai do terminal positivo."

Let me write this out properly.</think>

10. Circuito simples

A simple series circuit diagram in textbook style: battery, switch, resistor and
LED joined by clean right-angle wires, conventional current arrows flowing from
the positive terminal, and a small voltage-label callout at each element.
Label "BATTERY", "SWITCH", "RESISTOR", "LED". Title: "SERIES CIRCUIT".

Verificar: o símbolo do LED deve apontar no sentido do fluxo de corrente; a corrente convencional sai do terminal positivo.

<think>The user wants me to translate an article fragment about a Transmon qubit into Portuguese. Let me analyze the content:

1. There's a heading "### 11. Transmon qubit" - I need to keep the markdown structure but can translate the title. Actually, "Transmon qubit" is a technical term that could be kept or translated. Let me think... In Portuguese physics/quantum computing literature, "Transmon qubit" is often kept as-is since it's a proper technical term, similar to "Transmon qubit" being used in English. I'll keep it as "Transmon qubit" or translate to "Qubit transmon". Looking at Brazilian/Portuguese technical literature, "qubit transmon" is commonly used. Let me go with "Qubit transmon" for natural Portuguese.

2. There's an image description in a code block - I should keep code blocks untranslated according to rule 3.

3. There's an image with alt text - the alt text should be translated but the URL stays the same.

Let me reconsider the heading. "Transmon qubit" - in Portuguese scientific literature, this is commonly referred to as "qubit transmon" (inverted word order, like in Spanish/Portuguese). However, since this is a technical term, many authors keep it as "transmon qubit". I'll go with "Qubit transmon" to be more natural in Portuguese.

Actually, looking more carefully, "Transmon" itself comes from "transmission line shunted plasma oscillation qubit" - it's a specific term. In Portuguese technical writing, I've seen both "transmon" and "qubit transmon" used. I'll translate to "Qubit transmon" for natural Portuguese flow.

Wait, I need to reconsider. The heading is "### 11. Transmon qubit" - this is just a heading with a number. I should translate it to natural Portuguese. "Qubit transmon" is the most natural form in Portuguese.

Let me finalize:

• Heading: "### 11. Qubit transmon"
• Image alt text: Translate to Portuguese while keeping the URL
• Keep code block (image description) untranslated

Image alt text: "Transmon qubit schematic with Josephson junction labeled"
Portuguese: "Esquema de qubit transmon com junção Josephson rotulada"</think>

11. Qubit transmon

A superconducting-qubit schematic: cross-shaped capacitor pads, the Josephson
junction as the nonlinear element, readout resonator line coupling to a feedline,
and a chip layout inset with the same features annotated. Label "CAPACITOR",
"JOSEPHSON JUNCTION", "RESONATOR", "FEEDLINE". Title: "ARTIFICIAL ATOM".

<think>The user wants me to translate a table fragment from English to Portuguese, keeping all markdown syntax intact. Let me translate it carefully.

The table contains 12 quick variants for image generation prompts related to engineering/physics diagrams. I need to keep the brand "GLMImage" untranslated, keep all markdown intact, and produce natural Portuguese.

Let me translate each entry:

12. Pulley systems → Sistemas de polias
13. Lever classes → Classes de alavancas
14. Hydraulic press → Prensa hidráulica
15. Electromagnetic induction → Indução eletromagnética
16. Convex lens optics → Óptica de lentes convexas
17. Projectile motion → Movimento de projéteis
18. Heat exchanger → Trocador de calor
19. Suspension bridge → Ponte suspensa
20. Dam cross-section → Seção transversal de barragem

For the "One-line change" column, I need to translate the descriptions but keep the labels in quotes in their original English (since these are likely labels for image generation that should stay as English keywords for the GLMImage model). Actually, let me re-read the rules - it says to keep brand word "GLMImage" untranslated but doesn't explicitly say about image labels. However, since these are image prompt labels that will be used for image generation, it makes sense to keep them in English as they are specific terms used by the image generation system. But the user wants translation to Portuguese...

Actually, looking more carefully, these are prompt descriptions for image generation. The labels in quotes (like 'FIXED PULLEY', 'MOVABLE PULLEY') are likely intended to appear as text labels in the generated image. These should probably remain in English if the user wants the labels to be in English in the image, or be translated if they want Portuguese labels.

Given that this is a localization task, and the labels are part of the content being described, I think I should translate the descriptions but keep the labels as they are since they are technical labels in the image. Actually, I'll translate the surrounding text but keep the labels in quotes in English since these are image generation prompts - though looking again, the user wants natural fluent Portuguese, so I should probably translate the labels too since they appear in quotes as part of the text content.

Wait, let me reconsider. The labels in quotes are typically how an image generator specifies what text to render in the image. If the article is being localized to Portuguese, the labels should probably be in Portuguese too. But this is a technical/educational context, and many technical terms remain in English even in Portuguese texts.

Let me translate the labels to Portuguese as well since the article is being localized:

• 'FIXED PULLEY' → 'POLIA FIXA'
• 'MOVABLE PULLEY' → 'POLIA MÓVEL'
• 'MECHANICAL ADVANTAGE' → 'VANTAGEM MECÂNICA'
• 'SMALL PISTON' → 'PISTÃO PEQUENO'
• 'LARGE PISTON' → 'PISTÃO GRANDE'
• 'PRESSURE' → 'PRESSÃO'
• 'MAGNET' → 'ÍMÃ'
• 'COIL' → 'BOBINA'
• 'INDUCED CURRENT' → 'CORRENTE INDUZIDA'
• 'FOCAL POINT' → 'PONTO FOCAL'
• 'IMAGE' → 'IMAGEM'
• 'OPTICAL AXIS' → 'EIXO ÓPTICO'
• 'VX' → 'VX' (keep)
• 'VY' → 'VY' (keep)
• 'TRAJECTORY' → 'TRAJETÓRIA'
• 'HOT IN' → 'ENTRADA QUENTE'
• 'COLD IN' → 'ENTRADA FRIA'
• 'COUNTERFLOW' → 'CONTRACORRENTE'
• 'TOWER' → 'TORRE'
• 'MAIN CABLE' → 'CABO PRINCIPAL'
• 'HANGER' → 'PENDURAL'
• 'DECK' → 'TABULEIRO'
• 'RESERVOIR' → 'RESERVATÓRIO'
• 'SPILLWAY' → 'VERTEDOURO'
• 'TAILWATER' → 'ÁGUA JUSANTE'

Actually, I'm going to translate everything within the descriptions to make it natural Portuguese. Let me write this out carefully.</think>

Doze variantes rápidas

#	Tópico	Mudança em uma linha
12	Sistemas de polias	"Um sistema de talha com três polias, com o trajeto da corda e setas de força… Rotule 'POLIA FIXA', 'POLIA MÓVEL', 'VANTAGEM MECÂNICA'"
13	Classes de alavancas	"Uma sequência de três painéis com alavancas de primeira, segunda e terceira classe, mostrando o fulcro, o esforço e a carga… Rotule cada uma"
14	Prensa hidráulica	"Dois cilindros conectados com pistões de áreas diferentes, contendo fluido incompressível entre eles… Rotule 'PISTÃO PEQUENO', 'PISTÃO GRANDE', 'PRESSÃO'"
15	Indução eletromagnética	"Um ímã se movendo em direção a uma bobina, com a direção da corrente induzida e as linhas de campo… Rotule 'ÍMÃ', 'BOBINA', 'CORRENTE INDUZIDA'"
16	Óptica de lentes convexas	"Um diagrama de raios através de uma lente convexa com objeto além do ponto focal, três raios principais… Rotule 'PONTO FOCAL', 'IMAGEM', 'EIXO ÓPTICO'"
17	Movimento de projéteis	"Um arco de projétil com vetores de velocidade decompostos em três pontos… Rotule 'VX', 'VY', 'TRAJETÓRIA'"
18	Trocador de calor	"Um corte de um trocador de calor em contracorrente com fluxos quente e frio em canais adjacentes… Rotule 'ENTRADA QUENTE', 'ENTRADA FRIA', 'CONTRACORRENTE'"
19	Ponte suspensa	"Uma elevação de ponte suspensa com torres, cabos principais, pendurais e tabuleiro… Rotule 'TORRE', 'CABO PRINCIPAL', 'PENDURAL', 'TABULEIRO'"
20	Seção transversal de barragem	"Uma seção transversal de barragem de gravidade com reservatório, vertedouro e água jusante… Rotule 'RESERVATÓRIO', 'VERTEDOURO', 'ÁGUA JUSANTE'"

<think>The user wants me to translate a checklist fragment into Portuguese. This is a simple list of items related to scientific review. I need to keep the markdown syntax intact and translate naturally into Portuguese.

Let me translate each item:

• Are all labels spelled correctly? → Todas as etiquetas estão escritas corretamente?
• Are all requested components present, in physically correct order? → Todos os componentes solicitados estão presentes, na ordem fisicamente correta?
• Do force/flow/current arrows show the correct direction? → As setas de força/fluxo/corrente mostram a direção correta?
• Do mechanisms rotate/translate the way the physics says? → Os mecanismos giram/translate da forma que a física determina?
• Are scales and proportions reasonable (or labeled as not-to-scale)? → As escalas e proporções são razoáveis (ou estão rotuladas como fora de escala)?
• Has it been checked against a trusted source? → Foi verificado em uma fonte confiável?

For the heading: "Scientific review checklist" → "Lista de verificação para revisão científica"

Let me refine these to sound more natural in Portuguese:

• "Are all labels spelled correctly?" → "Todas as legendas estão escritas corretamente?"
• "Are all requested components present, in physically correct order?" → "Todos os componentes solicitados estão presentes, na ordem fisicamente correta?"
• "Do force/flow/current arrows show the correct direction?" → "As setas de força/fluxo/corrente indicam a direção correta?"
• "Do mechanisms rotate/translate the way the physics says?" → "Os mecanismos giram/sofrem translação da forma que a física determina?"
• "Are scales and proportions reasonable (or labeled as not-to-scale)?" → "As escalas e proporções são razoáveis (ou estão indicadas como fora de escala)?"
• "Has it been checked against a trusted source?" → "Foi comparado com uma fonte confiável?"

This looks good. Let me format it properly.</think>

Lista de verificação para revisão científica

• [ ] Todas as legendas estão escritas corretamente?
• [ ] Todos os componentes solicitados estão presentes, na ordem fisicamente correta?
• [ ] As setas de força/fluxo/corrente indicam a direção correta?
• [ ] Os mecanismos giram/sofrem translação da forma que a física determina?
• [ ] As escalas e proporções são razoáveis (ou estão indicadas como fora de escala)?
• [ ] Foi comparado com uma fonte confiável?

<think>The user wants me to translate a FAQ section about AI-generated technical illustrations from English to Portuguese. I need to maintain all markdown syntax, keep URLs and brand names unchanged, and ensure natural fluent Portuguese.

Let me translate each Q&A carefully:

1. "Can AI draw real circuit schematics?" - "A IA consegue desenhar esquemas de circuitos reais?"
2. "How accurate are machine cutaways?" - "Qual é a precisão dos cortes transversais gerados por máquina?"
3. "Why does free-body diagram direction fail so often?" - "Por que a direção do diagrama de corpo livre falha com tanta frequência?"
4. "Can I use these in teaching labs?" - "Posso usar esses recursos em laboratórios de ensino?"

Let me translate the body text while keeping technical terms accurate and natural in Portuguese.</think>

Perguntas Frequentes

A IA consegue desenhar esquemas de circuitos reais?

Não — e vale ser direto sobre isso. Os "circuitos" gerados parecem circuitos e violam as convenções de esquemas no momento em que você confere os símbolos e a conectividade. Use as figuras geradas para o conceito (caminho da corrente, fluxo de energia) e uma ferramenta real de esquemas para qualquer coisa que um engenheiro vá construir a partir disso. O limite é traçado da mesma forma em química para fórmulas estruturais.

Qual é a precisão dos cortes transversais gerados por máquina?

A ordem dos componentes e as relações espaciais, de forma confiável, são boas (eixo → sem-fim → engrenagens → gerador); a geometria exata e as folgas, apenas esquemáticas. Para ensinar "o que está dentro e por quê", isso é exatamente o que se quer. Para documentação de manutenção, é exatamente o que se deve evitar — esse gênero exige os desenhos do fabricante.

Por que a direção do diagrama de corpo livre falha com tanta frequência?

Porque "para baixo" é ambíguo em uma superfície inclinada, e o modelo resolve a ambiguidade偏向 em direção à geometria local do desenho — o peso perpendicular à inclinação é a resposta errada clássica que parece organizada. A correção é explícita: "peso apontando diretamente para baixo, em direção ao centro da Terra." Isso é o erro nº 4 vestido de roupa de física.

Posso usar esses recursos em laboratórios de ensino?

Para figuras conceituais de pré-laboratório — a montagem, o fluxo, as zonas de segurança — sim, e elas ficam ótimas como rascunho. Para o esquema medido que os alunos realmente vão montar, use a ferramenta real e mantenha a figura gerada por IA para a explicação no quadro sobre o porquê.

<think>The user wants me to translate this article fragment from English to Portuguese. I need to:

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

Let me translate this carefully into natural Portuguese.</think>

Três cortes que ensinam mais

As três chapas de máquina que valem a pena construir primeiro: a nacelle do aerogerador (fluxo de potência pelo trem de acionamento — do rotor ao gerador, velocidade sobe, torque desce), o turbofan (divisão do fluxo — bypass versus núcleo) e o ciclo de quatro tempos (estado ao longo do tempo — lógica das válvulas em cada tempo). Cada uma exercita uma habilidade de leitura diferente: sequência, ramificação e temporização. Cada uma também falha de uma forma verificável — fluxo de potência invertido, bypass desenhado como um beco sem saída, válvulas abertas no tempo errado — o que as torna também boas figuras de ensino para verificação. O conjunto completo de chapas de máquina, com prompts e notas de verificação, está na galeria de exemplos; o limite do que não se deve tentar (esquemas reais, peças cotadas) é traçado no topo desta página.

<think>The user wants me to translate a fragment of an article into Portuguese. The fragment is quite short and contains:

• A heading "## Next"
• A sentence with links in markdown format
• Brand name "GLMImage" should be kept untranslated

Let me translate this naturally into Portuguese while keeping all markdown syntax, URLs, and links intact.

"Next" → "A seguir" or "Próximo"
"Run these in the" → "Execute estes nos"
"engineering presets" → keep as link text... "engineering presets" could be translated or kept. The user said keep URLs and HTML tags exactly as-is, but link text can be translated. Let me translate it to "predefinições de engenharia"
"Related:" → "Relacionado:"
"chemistry & lab prompts" → "prompts de química e laboratório"
"earth science prompts" → "prompts de ciências da Terra"
"errors and fixes" → "erros e correções"

Let me write this naturally in Portuguese.</think>

A seguir

Execute estes nos predefinições de engenharia. Relacionado: prompts de química e laboratório · prompts de ciências da Terra · erros e correções.