The user wants me to generate a high-conversion, bottom-of-funnel product review page in HTML format based on the provided product data and strict editorial guidelines (Engine Editorial V39.0). Let me process the internal parameters first (silently): 1. **Product Name:** “Kit – Estimulação Cognitiva para Idosos” 2. **Title/Headline:** “Kit – Estimulação Cognitiva para Idosos” (same as product name essentially, but the prompt has `[titulo_conteudo]` as “Kit – Estimulação Cognitiva para Idosos” in the specs). 3. **Affiliate Link:** `https://go.hotmart.com/J88503595X?dp=1` **Calculations:** * **TOM DE VOZ (1st letter of Product Name: ‘K’):** ‘K’ is in group `A,F,K,P,U,Z` -> **Investigativa Pragmática**. * **COR LÍDER (1st letter of Title/Content: ‘K’):** ‘K’ is in group `A,F,K,P,U,Z` -> **`#0F52BA`** (Blue). * **ROTEIRO DE SEÇÕES (2nd letter of Product Name: ‘i’ -> ‘I’):** Wait, “Kit”. 1st letter K. 2nd letter **’i’**. Group 3 `[D,I,N,S,X]` -> **Forense Analítico**. Roteiro: ABERTURA_FUNIL → CTA_PRIMÁRIO → SEÇÃO_PRODUTO → SEÇÃO_PLAYBOOK → SEÇÃO_GARANTIA → SEÇÃO_DOWNLOAD_MEMBROS → SEÇÃO_CRONOGRAMA → CTA_FINAL. * **DISPONIBILIDADE FACTUAL (Count filled markers in `[dados_tecnicos]`):** The JSON provided has: `titulo`, `autor`, `preco_promo`, `preco_de`, `ranking`, `paginas`, `auditoria_livre`. The specific markers to check: `PRECO:`, `GARANTIA:`, `CARGA_HORARIA:`, `SUPORTE:`, `METODOLOGIA:`, `CERTIFICACAO:`, `COMUNIDADE:`, `BONUS:`, `ATUALIZACOES:`. Looking at the JSON: `preco_promo` exists (PRECO). `GARANTIA` not explicitly in top level, but standard Hotmart is 7-30 days. `CARGA_HORARIA` no. `SUPORTE` no. `METODOLOGIA` described in audit but not a field. `CERTIFICACAO` no. `COMUNIDADE` no. `BONUS` no. `ATUALIZACOES` no. Count = 1 (Preco). Maybe 2 if we count Garantia as standard Hotmart. **Result: Less than 3.** **Rule:** “Converta tudo para texto puro, mantendo apenas os dois blocos CTA”. No visual components (KPI, Timeline, Badges, Exec Summary Table) except Badges and CTAs? Wait: “Menos de 3: converta tudo para texto puro, mantendo apenas os dois blocos CTA”. And “Exceto BADGES e CTAs” was for 3-4. For <3: "converta tudo para texto puro, mantendo apenas os dois blocos CTA". So NO Badges panel, NO Exec Summary Table. Just text, CTA Primary, CTA Final, Garantia block, Download block. *Correction:* The prompt says in section 7 (COMPONENTE_BADGES) "Gere um badge para cada campo disponível...". But section 1 says "Menos de 3: converta tudo para texto puro, mantendo apenas os dois blocos CTA". Section 1 is the master rule. I must follow Section 1. So I will **omit** the Badges Panel (Section 7) and Exec Summary Table (Section 8). I will keep the two CTA cards, the Garantia Blockquote, and the Download Aside. **Data Extraction for Content:** * **Format:** PDF Digital (Digital Product). * **Platform:** Hotmart (implied by link `go.hotmart.com`). * **Price:** R$ 37,00. * **Guarantee:** Not explicit in JSON. Standard Hotmart usually 7, 15, or 30 days. I will assume standard CDC 7 days but mention Hotmart usually offers more. The prompt says: "Se `GARANTIA:` não estiver em `[dados_tecnicos]`, use o padrão legal de **7 dias** (CDC Art. 49 — produto digital)". I will use 7 days for the badge/text but mention Hotmart policy might extend. * **Content:** 480+ activities, cognitive stimulation, attention, memory, etc. For professionals, caregivers, family. PDF format. Printable. * **Critical Point:** Lack of scientific methodology detail, validation, progression clarity. * **PDF Experience:** Printing costs, static. * **Cost Benefit:** Low entry price, but printing adds up. **Writing Plan:** 1. **ABERTURA_FUNIL:** 2-3 paragraphs. Mention product name + "download" in first para. Answer legitimacy, value, access, guarantee. Journalistic tone. 2. **CTA_PRIMÁRIO:** HTML Card with Badges (Format, Guarantee, Platform, Official). Button with Leader Color (#0F52BA). Link inserted. 3. **SEÇÃO_PRODUTO:** (h2 + emoji) ~150-220 words. What is it, for whom, problem solved, value prop. Mention format, depth. 4. **SEÇÃO_PLAYBOOK:** (h2 + emoji) ~150-220 words. 3 pillars/mechanics. Practical application. Differential vs free content. 5. **SEÇÃO_GARANTIA:** (Blockquote) Mandatory. Leader color border. Policy, refund process, CDC Art 49. 6. **SEÇÃO_DOWNLOAD_MEMBROS:** (Aside) Mandatory. How access works (Hotmart members area), not direct download, no free/pirated version, devices. 7. **SEÇÃO_CRONOGRAMA:** (h2 + emoji) ~150-220 words. Structured list (ul/li) of absorption stages/modules. 8. **CTA_FINAL:** (Footer) Headline, concluding sentence, Button (Leader Color), Disclaimer. **Constraints Checklist:** * Only HTML tags: p, h3 (wait, instruction says h2 for sections, h3 not allowed? "Escreva EXCLUSIVAMENTE utilizando tags HTML limpas:
,
,
,
- , ,
,
,
,
,
.” -> It says h3. But section 4 says “Abra cada uma com `
` editorial”. Conflict. I will use `
` as per section 4 specific instruction, but the allowed tags list in section “REGRAS CRUCIAIS DE FORMATAÇÃO HTML” says `
`. Usually specific instruction overrides general. But “Escreva EXCLUSIVAMENTE utilizando tags HTML limpas:
,
…”. This is a hard constraint. I will use `
` for section headers to respect the tag whitelist, but style them like h2. Wait, the prompt says “Abra cada uma com `
` editorial com 1 emoji”. I will follow the specific instruction for the section structure (`
`) because the whitelist might be a generic “clean tags” list not exhaustive, but “EXCLUSIVAMENTE” is strong. However, the prompt *also* says “nunca use a tag
“. It doesn’t forbid h2. It lists h3 as allowed. I’ll use `
` to be safe on the “EXCLUSIVAMENTE” rule, but make it look like a section header. Actually, looking at the CTA_PRIMARIO template, it uses no headers. The CTA_FINAL uses `
`. The template for CTA_FINAL uses `
`. The template for Garantia uses `
`. The template for Download uses `
| , | ,
|
|---|