Here’s a thinking process:

1. **Analyze the Request:**
– **Role:** Professional job ad writer in Brazilian Portuguese
– **Task:** Expand a short, truncated job snippet into a complete, well-organized HTML description
– **Constraints:**
– Use only `

` and `

`/`
• ` tags (no headings, no markdown)
  – Do NOT invent specific facts not implied in the snippet or provided fields
  – Can use general/standard sector language appropriate to the role (e.g., “Operador de Empilhadeira” responsibilities), but naturally, not as confirmed facts
  – Keep text truthful, professional, legible
  – Write entirely in Brazilian Portuguese, natural and clear, no unnecessary anglicisms
  – Target size: ~700 words
  – Output ONLY the HTML description, no title, no introduction, no code block markers

  2. **Analyze the Input Data:**
  – **Cargo:** Operador de Extrusão
  – **Empresa:** Antilhas Embalagens & Soluções
  – **Localização:** Salvador, Bahia
  – **Trecho original (truncado):**
  “Responsável pela operação das máquinas, ajuste do equipamento, incluindo, leitura e análise da ordem de produção, checagem dimensional do produto, visando produzir material com qualidade, atendendo as necessidades dos clientes. Escolaridade Mínima: Ensino Médio (2º Grau) – convenio odontológico – convenio medico – fretado – refeição no local – cesta básica – participação dos lucros”

  3. **Identify What’s Given vs. What Can Be Expanded:**
  – Given: Job title, company, location, core responsibilities (operation of machines, equipment adjustment, reading/production order analysis, dimensional checking, quality focus, customer needs), minimum education (High School), benefits listed ( dental plan, medical plan, shuttle, meals on site, basic food basket, profit sharing)
  – NOT given: Specific years of experience, specific certifications, exact salary, detailed technical requirements beyond what’s implied, company size, specific production type, etc.
  – Constraint Check: “NÃO invente fatos específicos que não estejam implícitos…” -> I must not invent salary, specific certifications, exact experience years beyond what’s reasonable to imply without fabricating. I can use general sector language for an “Operador de Extrusão” role, but must frame it as typical duties, not as confirmed requirements for this specific job unless implied.
  – Constraint Check: “Você PODE usar linguagem geral e padrão do setor, apropriada ao cargo (ex.: responsabilidades típicas de um ‘Operador de Empilhadeira’), desde que apresente isso de forma natural e não trate suposições como fatos confirmados.” -> This is key. I can describe what an extrusion operator typically does, but I must be careful not to say “Requires 3 years experience” if not stated. I’ll keep it general and implied.
  – Constraint Check: “Mantenha o texto verdadeiro, profissional e legível — pensando em uma pessoa real decidindo se deve se candidatar.” -> Focus on clarity, honesty.
  – Constraint Check: “Escreva inteiramente em português do Brasil, natural e claro, sem anglicismos desnecessários.” -> OK.
  – Constraint Check: “Tamanho alvo: aproximadamente 700 palavras.” -> Need ~700 words in the HTML content.
  – Constraint Check: “Produza SOMENTE o HTML da descrição, nada além disso (sem título, sem introdução, sem marcação de bloco de código).” -> Output just the HTML, using `

  ` and `

  `/`
  • `. No headings, no markdown, no “` delimiters.

    4. **Determine the Structure (HTML only, `

    ` and `

    `/`
    • `):**
      – I need to create a coherent, flowing description using paragraphs and lists.
      – I should start with the role overview, then responsibilities, requirements, benefits, and location/company info.
      – Must avoid `<h1`-`

      `, no markdown headings. I can use `

      ` and `

      `/`
      • ` only.
        – I need to make sure the text is about 700 words. That’s quite long for an HTML snippet with only `

        ` and `

        `/`
        • `, but doable if I expand each section well.
          – I need to be careful not to invent specific benefits beyond what’s listed, but I can describe them in general terms consistent with the list: “convenio odontológico”, “convenio medico”, “fretado”, “refeição no local”, “cesta básica”, “participação dos lucros”. I’ll restate them naturally.
          – For responsibilities, I’ll use general extrusion operator duties that are implied: operating extruders, adjusting equipment, reading production orders, quality control, dimensional checks, ensuring output meets client needs. I’ll frame them as “entre outras” or “incluindo” but without inventing specifics not in the text.
          – For requirements, I’ll mention “Ensino Médio” as minimum, and maybe mention that experience in extrusion or packaging is a plus, but I won’t invent years. I’ll keep it general: “experiência na área é desejável” but carefully, or just focus on the listed minimum. Actually, the constraint says “NÃO invente fatos específicos…”. I can say “Experiência na área é um diferencial” if I want, but better to stick to what’s given or very general. I’ll probably just mention the minimum education and that knowledge of the area is welcome, but not specify years.
          – I need to reach ~700 words. That’s a lot. I’ll need to expand each section significantly with natural, professional text, repeating the benefits in different phrasing, describing the company’s focus, the role’s impact, etc., all while staying truthful to the snippet.

          Let outline the HTML structure:
          – `

          `: Introduction to the company and location, the role’s importance.
          – `

          `: Detailed responsibilities, drawn from the snippet and generalized appropriately.
          – `

          `/`
          • `: Minimum education and benefits list, but expanded with descriptive text within `

            ` or as list items that explain each benefit naturally.
            – `

            `: About the company, sector, what they offer.
            – `

            `/`
            • `: Maybe list responsibilities as bullet points, but the constraint says `
              `/`
              • ` are allowed. I can use them for responsibilities or benefits.
                – Need to ensure total word count ~700.

                Wait, let me re-read the constraint: “use only

                and

                /
                • , without headings, without markdown”. So I can have `

                  ` paragraphs and `

                  `/`
                  • ` lists. No `
                    

                    `, etc. I can have multiple `

                    ` and `

                    ` blocks.

                    I need to be very careful with word count. 700 words in HTML with only `

                    ` and `

                    `/`
                    • ` means I need to write a lot of text. I’ll structure it as a series of paragraphs and lists that naturally add up to ~700 words.

                      Let me plan the content:
                      – Paragraph 1: Company intro, location, mission in the packaging sector.
                      – Paragraph 2: Role context, why the extrusion operator matters.
                      – Paragraph 3: Core responsibilities extracted and expanded naturally from the snippet. I’ll list typical duties but phrase them as “entre as principais atividades” without inventing.
                      – List of responsibilities: maybe as `

                      • …` but I need to be careful not to invent items not implied. The snippet says: “operação das máquinas, ajuste do equipamento, leitura e análise da ordem de produção, checagem dimensional do produto, visando produzir material com qualidade, atendendo as necessidades dos clientes.” I’ll use these exact items or very close paraphrases, as they are given. I can put them in a `
                        `.
                        – Paragraph 4: Minimum education and what it implies.
                        – `
                        `/`
                        • ` for benefits: The snippet lists “convenio odontológico – convenio medico – fretado – refeição no local – cesta básica – participação dos lucros”. I’ll expand each in `
                        • ` with natural description, but staying true to what they are. E.g., “Convenio odontológico: assistência odontológica com cobertura para procedimentos preventivos e tratamentos.” But wait, I shouldn’t invent coverage details not implied. I’ll keep it generic: “Convenio odontológico” etc., and maybe describe them briefly in general terms that are standard but not fabricated. The constraint says “NÃO invente fatos específicos…”. So I can state the benefit names, and perhaps say “inclui assistência odontológica” without specifying what’s covered. I’ll just list them as items with brief, generic descriptions that are safe.
                          – Paragraph 5: About the workplace, location, what the candidate can expect.
                          – Closing paragraph encouraging application, but naturally.

                          Word count challenge: 700 words is a lot. I need to expand each section with professional, natural text. I’ll have to be careful to not contradict the “no invented facts” rule. I can add general industry context, describe the extrusion process in broad terms, talk about the packaging sector, the importance of quality, etc., as long as it’s not specific to the job beyond what’s implied.

                          Let me start drafting mentally, keeping track of word count. I’ll

                          • Empresa: Antilhas Embalagens & Soluções
                          • Localização: Salvador, Bahia
                          • Categoria da Vaga: Unknown
                          • Tags da Vaga: Salvador