Tempo e Temperatura Perfeito para Peixe Assado
We need to produce a complete article per directives. Must start with a
tag of contextualization, no intro fluff. Then we need to follow the structure. Given product: Receita de Peixe Assado. Affiliate link is “#”. So no link. We must not use markdown formatting except allowed tags:
,
,,- , ,
,,, ,. Also we can use
/
inside as per FAQ block, but those are HTML tags. We need to produce article in Markdown and HTML clean? The instruction says “Gere o artigo completo formatado em Markdown e HTML limpo agora.” But also “Escreva EXCLUSIVAMENTE utilizando tags HTML limpas”. So we must output HTML tags only, no markdown syntax like #. So we need to output pure HTML? Use tags like,
,,- , ,
, etc. We need to include: – Part 1: Resposta direta (first 2 paragraphs) in tags. – Then “FICHA TÉCNICA RÁPIDA” use a highlighted block in Markdown? But we must use HTML tags only. Could use
maybe? But only allowed tags listed:,
,,- , ,
,,, ,. So we cannot use
or. But we can maybe use
for title, then a
for each attribute? Or we can use
for list. The spec says "Use um bloco destacado em Markdown" but we cannot use markdown. However we can approximate with HTML. Maybe useFICHA TÉCNICA RÁPIDA
then a
with the data? Or use
. But allowed tags include,,, . So we can create a table for technical sheet. - Ingredients list: with- . - Steps: maybe use
for each step? Not required but can use. - Part 2: Storytelling etc. Must include sections: "HISTÓRIA, ORIGEM OU SEGREDOS DA RECEITA" maybe as. - Variation and related recipes: maybe. - FAQ in HTML using etc. Must use
and
. Those tags are not listed but maybe allowed because they are HTML tags; the directive only listed allowed tags but not exclusive? It says "Escreva EXCLUSIVAMENTE utilizando tags HTML limpas:,
,,- , ,
,,, ,." So only those tags are allowed.
and
are not in that list, so we cannot use them. However the directive for FAQ says "Formate a FAQ em HTML limpo:" and shows and
. But those tags are not in allowed list. This is contradictory. However the higher-level instruction says we must obey the formatting rules. The allowed tags list includes only those. So we cannot use either? It is not listed. Actually is not listed. So we cannot use. But the FAQ block uses wrapper. This is contradictory. We need to decide which rule takes precedence. The "REGRAS DE FORMATAÇÃO HTML" says "Escreva EXCLUSIVAMENTE utilizando tags HTML limpas:,
,,- , ,
,,, ,." So we can only use those tags. Therefore we cannot use
,
,
, etc. But the FAQ section explicitly requires that HTML structure. Possibly we can embed that structure using only allowed tags? But
and
are not allowed. However maybe they consider them part of HTML tags allowed? The list is not exhaustive? It says "tags HTML limpas:,
,,- , ,
,,, ,." It might be that they only listed commonly used tags but allowed others? However they said "EXCLUSIVAMENTE utilizando tags HTML limpas: ..." So we should restrict to those. But then the FAQ block cannot be implemented as instructed. Maybe we can simulate using
and- only? But the FAQ format expects
/
. Could we use as summary? Not exactly. Given the constraints, perhaps we can output the FAQ using and- only, but the instruction says "Formate a FAQ em HTML limpo:" and shows that structure. I think we must follow that structure, even if tags not listed, because it's part of the required output. The higher-level rule about allowed tags might be superseded by the specific requirement for FAQ. But the "REGRAS DE FORMATAÇÃO HTML" is a higher-level constraint. However the FAQ block is part of the content spec and uses those tags. I think we should include them, as they are HTML tags, even if not in the allowed list. The allowed list might be just examples, not exhaustive. The instruction says "Escreva EXCLUSIVAMENTE utilizando tags HTML limpas:
,
,,- , ,
,,, ,." That suggests we should not use any other tags. But then we cannot use
or
. However the FAQ block explicitly uses and
. This is contradictory. Given the need to produce a correct answer, I will include the FAQ using and
as required, because it's explicit. The allowed tags list might be not strictly enforced for that block. I think it's okay. We must not use any other tags like,, etc. Only is allowed. So we can use for headings. We must not use markdown syntax like #. So we will output pure HTML. We must not use any extra commentary, notes, etc. Just the article. We must start with a
tag of contextualization. We must not include any intro generic. So first
should directly address the search intent: talk about the dish, its differential, promise. Then we need to include "FICHA TÉCNICA RÁPIDA" maybe as
FICHA TÉCNICA RÁPIDA
then a table. Then ingredients list
Ingredientes e medidas precisas
then
. Then "Modo de preparo passo a passo" maybe asModo de Preparo
then
steps? Could use
but not allowed. Could use
with- steps. We need to include variations, story, FAQ, card for afiliado (but link is "#", so we omit). Then final practical closing with 3 tips. We must not use cliches like "Em suma". So just end with tips. We must not use any bold/italic markup except . That's allowed. We must not use any other formatting. We must not use any link except if affiliate link present, but it's "#", so we omit. We must not use any extra tags beyond allowed. We need to include the FAQ block exactly as specified, with etc. Those styles are inline CSS, allowed? Not listed but maybe okay. The instruction didn't forbid CSS inline. It only listed tags. So we can include style attributes. We need to include
and
which are not in allowed list but required. I'll include them. We must not use any other tags like. So keep minimal. Now craft the content. First contextualization: maybe talk about the importance of a perfect baked fish recipe, crispiness, juiciness, easy. Then "FICHA TÉCNICA RÁPIDA" as a table: maybe use
with rows: Tempo de Preparo, Tempo de Forno, Rendimento, Dificuldade. Then ingredients list. Then steps. Then story/history:História ou Segredo da Receita
then
content. Then variations:
Variações e Acompanhamentos
then
with variations. Then FAQ: implement as per spec. Then afiliado card: omitted. Then final practical: 3 tips maybe as. Make sure no extra headings beyond. Use for emphasis. Now produce final HTML. Let's draft. Start:O peixe assado perfeito combina crocância na cobertura, interior suculento e aroma que lembra cozinhas tradicionais. Esta versão traz técnica de tempero equilibrado e tempo de forno otimizado, garantindo resultado profissional mesmo na cozinha caseira.
Then maybe a heading for "FICHA TÉCNICA RÁPIDA". Use
FICHA TÉCNICA RÁPIDA
then table.
Tempo de Preparo 30 minutos Tempo de Forno 20 minutos Rendimento 4 porções Dificuldade Fácil
Then ingredients:
Ingredientes e medidas precisas
- 4 filés de peixe branco (600 g no
| , | ,
|
|---|