Here’s a thinking process:

1. **Analyze User 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, naturally, not treating assumptions as confirmed facts
  – Keep text truthful, professional, legible
  – Write entirely in Brazilian Portuguese, natural, clear, no unnecessary anglicisms
  – Target size: ~700 words
  – Output ONLY the HTML description, no title, no intro, no code block markers

  2. **Analyze the Input Data:**
  – Cargo: AUXILIAR DE SERVIÇOS GERAIS – SERRINHA – BA
  – Localização: Serrinha, Bahia
  – Truncated snippet: “Atividades: Responsável em realizar serviços de limpeza da unidade e canaletas, ensacamento de carvão, descarregamento de insumos, atuar na limpeza na área de planta e barragem, capinar e cercar de áreas, apoio geral para limpeza e organização de obras e limpeza da bacia de conterção.”

  3. **Identify What’s Given vs. What Can Be Generalized:**
  – Given: Job title, location, list of activities (truncated but clear on tasks)
  – Must NOT invent: salary, specific certifications, fake benefits, invented years of experience, specific requirements not implied
  – CAN use: general descriptions of these tasks as typical for an “Auxiliar de Serviços Gerais”, using standard professional language, but must remain truthful and not present assumptions as facts
  – The snippet lists specific tasks: cleaning, canaletas, coal bagging, unloading supplies, plant/barrage area cleaning, weeding/fencing areas, general support, worksite cleanup, containment basin cleaning

  4. **Determine the Structure (HTML only,

  and

  /
  • ):**
    – Need to produce a single block of HTML
    – Must use `

    ` and `

    • ` elements
      – No headings (so no `<h1`-`

      `)
      – No markdown formatting
      – No title, no intro text outside HTML, no code block markers in output
      – Target ~700 words in the content itself

      Structure idea:
      – Paragraph introducing the role, location, and general purpose
      – Unordered list of responsibilities (expanded from the snippet using general but truthful language)
      – Maybe a paragraph about requirements/profile, but must be careful not to invent specifics. I can use generic, standard language like “experiência em serviços de limpeza e manutenção de obras” but must not state exact years if not given. The snippet doesn’t mention requirements, so I should either omit a requirements section or keep it very general and implied.
      – Actually, the prompt says “expand a short truncated snippet into a complete description”. I should focus on expanding the activities section truthfully, using standard phrasing for each task, but not adding new factual claims.

      Let’s re-read constraint 1: “NÃO invente fatos específicos que não estejam implícitos no trecho fornecido ou nos campos dados — sem valores de salário fabricados além do que foi informado, sem certificações falsas, sem benefícios inventados, sem exigências de anos de experiência inventadas.”
      Constraint 2: “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.”
      So I can write things like “Realizar limpeza de unidades e canaletas, incluindo remoção de resíduos e manutenção da área” – this is generalizing the specific task, but it’s standard sector language, not inventing a fact. I just need to make sure it’s clearly presented as description of what the role entails, not as verified facts from a job posting I don’t have.

      Constraint 5: ~700 words. That’s quite long for just activities. I need to flesh it out to around 700 words of actual content within the HTML. I’ll need to multiple paragraphs and list items, but carefully. I need to count or approximate. 700 words in HTML with

      and

      • . I’ll need to be expansive but stay within the rules.

        Let’s plan the content:
        – Intro paragraph: about the company/role context (but carefully, not inventing). I can say “A vaga destina-se a profissionais que desejam atuar na manutenção de limpeza e organização em unidades industriais ou de construção civil, com foco em áreas específicas como canaletas, bacias de contenção e obras.” – This is general, not invented.
        – Then a list of responsibilities, expanded from the snippet. Each bullet can be a short paragraph or a list item with description. But the HTML structure only allows

        and

        /
        • . I can have
          • items, and each
          • can contain text. I can also have multiple

            paragraphs.
            – I need to reach ~700 words. That means I’ll have a lot of text. I’ll need to expand each responsibility from the snippet into a few sentences of general, standard description, making sure I don’t invent specific data. I can talk about the nature of the work, skills typically involved, environment, etc., using very careful, generic language that doesn’t claim specifics.

            Let’s outline the HTML content:
            Paragraph 1: Introduction to the role, location, purpose.
            Unordered list of responsibilities (expanded from snippet). Maybe 8-10 items, each with a few sentences inside the

          • . But
          • can contain block-level? In HTML5,
          • can contain flow content, including

            . But to be safe and valid, I’ll just put text directly inside

          • , or nested

            if allowed. The prompt says “use only

            and

            /
            • “. It doesn’t say I can’t nest

              inside

            • , but it says “use only

              and

              /
              • “. I think it means the only tags allowed are

                ,

                ,
                • . No others. So I can structure like:
                  • texto…

                  , and

                  texto…

                  . I can have multiple

                  and

                  • > blocks.

                    To reach 700 words, I need a lot of

                    and

                  • content. Let’s calculate: ~700 words. If I use average 15 words per
                  • sentence, I need many items. But I can make each
                  • a paragraph-length text. Actually,
                  • can contain entire paragraphs, but to stay within the tag restriction, I’ll just put text directly. I’ll structure as alternating

                    and

                  • items.

                    Wait, the prompt says: “use only

                    and

                    /
                    • , without headings, without markdown.” So I can use

                      and

                      • . I’ll create a series of

                        paragraphs and

                        • list items. I need to be careful not to use
                          

                          –

                          .

                          Let’s design the content strategy:
                          – I’ll start with a

                          introducing the vacancy.
                          – Then a

                          • for each responsibility, expanded.
                            – Maybe another

                            about profile or context, but keeping it generic.
                            – I need to ensure total word count is ~700. I’ll write extensively, but must stay truthful.

                            Key: I must not invent salary, certifications, benefits, years of experience. I can mention “atividades inerentes ao cargo” generally, but not specify exact years. I can say “experiência em serviços gerais” but that’s a requirement; the snippet doesn’t mention it, but the prompt says “sem exigências de anos de experiência inventadas”. Saying “experiência em serviços gerais” is a general category, not a specific year requirement. I’ll be cautious. Maybe I omit a separate requirements section, or include only what’s implicitly there.

                            Actually, the snippet only has “Atividades: …”. There’s no requirements section. So I should focus the description on the activities, maybe with an introductory paragraph about the role, and then the list of expanded activities. I’ll avoid adding a “requisitos” section unless I phrase it very carefully as “perfil sugerido” but that might be inventing. Better to stick to activities and maybe a closing paragraph about the importance of the role.

                            Let’s count words as I go. Aim for ~700. I’ll write in Brazilian Portuguese, natural.

                            Plan:
                            –

                            … introductory paragraph about the vacancy, location, and general nature of the work. ~100 words.
                            –

                            • … eight items, each expanded to ~70-80 words. That’s ~560-640 words. Plus intro ~100, total ~660-740. I’ll adjust.
                              – Each

                            • will contain a paragraph-like text describing that specific responsibility, using general sector language but not inventing facts. I’ll
                              • Empresa: Vagas de Emprego Bahia
                              • Localização: Serrinha, Bahia
                              • Categoria da Vaga: Unknown
                              • Tags da Vaga: Serrinha