[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F6Y4KXCDFMA88EHVM0DRVB":3,"skill-same:01M7F6Y4KXCDFMA88EHVM0DRVB":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7F6Y4KXCDFMA88EHVM0DRVB","anuncio",null,"Makes a hook-first, business-oriented ad from a briefing, using only the owner-approved brand: one master image plus the aspect-ratio adaptations the platform needs, text variations inside the platform limits, and an import sheet with everything Paused (Google Ads Editor CSV, or an experimental Meta sheet). Publishes nothing and calls no ad API. Runs unattended from the panel action estudio.anuncio. Use on: anúncio, anuncio, ad, Google Ads, Meta Ads.","stage2dev\u002Ftune-up","stage2dev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F205088513?v=4","01M7F6TJSVA061K0AHEMXHHZAA","01M7F6TJTDN359R5QXK9C5RAZD",1,"MIT","https:\u002F\u002Fgithub.com\u002Fstage2dev\u002Ftune-up\u002Fblob\u002Fmain\u002Ftune-up-studio\u002Fskills\u002Fanuncio\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: anuncio\ndescription: \"Makes a hook-first, business-oriented ad from a briefing, using only the owner-approved brand: one master image plus the aspect-ratio adaptations the platform needs, text variations inside the platform limits, and an import sheet with everything Paused (Google Ads Editor CSV, or an experimental Meta sheet). Publishes nothing and calls no ad API. Runs unattended from the panel action estudio.anuncio. Use on: anúncio, anuncio, ad, Google Ads, Meta Ads.\"\nallowed-tools: Read, Bash(${CLAUDE_PLUGIN_ROOT}\u002Fnode\u002Fnode_modules\u002F.bin\u002Fhyperframes *), Bash(python3 -I ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fqa_imagem.py *), Bash(python3 -I ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Ffontes.py *), Bash(python3 -I ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Ffotos.py *), Bash(python3 -I ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fanuncio.py *)\n---\n\n# Ad (images, texts and a paused import sheet)\n\nThis runs in the background. Nobody answers questions: never ask anything, never wait for a reply, never run `ls` or any command outside the list below. When a step fails twice, write it down and finish. Ad copy is in Brazilian Portuguese; your final answer is one short line in Brazilian Portuguese.\n\nNothing is published. Never call an ad platform, never write a sheet by hand: the sheet comes only from `anuncio.py --exportar`.\n\nThe prompt gives: the working folder (`{trabalho}`, your current folder), `Plataforma` (`google` or `meta`, called `P` below), `URL` (the landing page) and the briefing file. Write only inside the working folder. Use relative paths made of letters, digits, `_`, `.` and `\u002F` only (no `-`, no `..`).\n\n`AN` = `python3 -I ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fanuncio.py`. `W` = the absolute path of the working folder.\n\n## 1. Plan\n\n1. Read the briefing file named in the prompt. The scripts read the facts only from `entrada.md` in the working folder (the panel writes the briefing there): if the prompt names another file, Write its exact text to `entrada.md` first. Without it `AN --exportar` and `AN --final` fail.\n2. Run `AN --plano P`. It prints the pieces (`a1` is the master, the next ones are the adaptations), each with `largura`, `altura` and `nome`, and the text limits: for each field `[min items, max items, max characters]`.\n3. Read once: `${CLAUDE_PLUGIN_ROOT}\u002Freferencias\u002Fganchos.md` and `checklist-atencao.md` (same folder); for Meta pieces also the *Arrangements* section of `arquetipos-post.md` and `recursos-visuais.md`. They hold the hook families, the regulated-niche rules, the self-check and the visual devices; this file does not repeat them.\n\nAd angles (each variation takes one; pt-BR molds from invented businesses):\n\n| angle | what it says | mold |\n|---|---|---|\n| situation or pain | the reader's situation or pain | `Carro fazendo barulho ao frear?` |\n| outcome | the result, with time | `Inglês para reunião em [N] meses` |\n| proof | number, rating or customer quote | `Nota [nota] em [N] avaliações` |\n| curiosity | the hidden detail | `O passo que evita [problema]` |\n| comparison | old way vs this one | `Sem planilha: o contador manda o DAS pronto` |\n| real urgency | a written limit | `Agenda de [mês] abre dia [dia]` |\n| identity | who it is for | `Para quem abriu o MEI este ano` |\n| objection | the doubt answered | `Atende sábado? Sim, das 8h às 13h.` |\n\nGoogle RSA mix: 3-4 headlines with benefit or keyword, 2-3 proof (only with proof in the briefing), 2-3 CTA, 1-2 differential, 1 brand; each makes sense alone, in any order. Meta: every primary text a different angle, the hook inside its first 125 characters. \"Agende já\" and \"Marque agora\" are one variation.\n\n## 2. Brand (read-only, as the `marca-ler` skill)\n\nSame as the `post` skill: read `\u003Croot>\u002F.tune-up\u002Festudio\u002Fmarca\u002Fmarca.json` (root = the working folder path cut right before `\u002F.tune-up\u002F`), use only `campos` colors and fonts, run `python3 -I ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Ffontes.py --trabalho W` once and paste every printed line at the top of each piece's `\u003Cstyle>`. Also read `campos.nome`, `campos.descricao` and the top-level `tom.valor` (voice). Contrast comes from a script, never from you: run `python3 -I ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fqa_imagem.py --pares W` once and use only the color pairs it prints (text 4.5:1 or more; a headline of 88 px or more may use a pair of 3:1 or more). Meta only (a Google piece carries no logo): an `.svg` logo in `\u003Croot>\u002F.tune-up\u002Festudio\u002Fmarca\u002Fassets\u002F`: Read it and Write the same text to `a\u003CN>\u002Ffonte\u002Fassets\u002Flogo.svg`; a PNG, JPEG or WebP logo comes only from `fotos.py --logo`; no logo file: leave it out and say so in `resultado.md`. Never write in the brand folder.\n\nPhotos: when `marca.json` has a non-empty `fotos` list, images come only from `python3 -I ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Ffotos.py --trabalho W --para a\u003CN>\u002Ffonte` (Meta: add `--logo`, up to 2 photos; Google: add `--quantas 1`, never `--logo`). It copies them as `assets\u002Ffoto1.\u003Cext>` (the main photo), `assets\u002Ffoto2.\u003Cext>` and prints one line per file: use exactly those names. Never pick, read or copy an image yourself, and never use an image made by AI, drawn to look like a photo, or from anywhere else.\n\n## 3. Strategy\n\nBefore any text, write `estrategia.md`, one key per line, `key: value`, exactly these keys:\n\n```\nobjetivo: vender | receber mensagens | encher a agenda | lançar novidade | ensinar e ganhar seguidores (inferred from the briefing as ganchos.md says, plus \" (inferido)\")\npublico: \u003Cone segment in one situation, from the briefing and campos.descricao>\nestagio: frio | morno | quente\npromessa: \u003Cone sentence the ad keeps, only briefing facts; never a promise of results>\nprova: \u003Cbriefing facts used as proof> | nenhuma\narquetipo: \u003Can archetype of arquetipos-post.md (Meta) or the main angle (Google)>\ngancho 1: [family] \u003Ctext> | nota \u003C0-5> | \u003Cone-line critique>\ngancho 2: ...\ngancho 3: ...\nescolhido: \u003C1|2|3> | \u003Cwhy>\ncta: \u003Ctext> | leve|média|forte\nangulos: \u003Cthe angles used in the variations, at least 3 from the table above>\nfaltou: \u003Cwhat the owner could send next time> | nada\n```\n\nThe 3 hooks come from 3 different families, scored with the rubric of ganchos.md; when the briefing names an audience or a situation, one speaks to it and the offer goes to the support line. For Meta they are the candidates for the headline of `a1` and each fits the `titulos` limit printed by `--plano`. Use an angle only if the briefing has what it needs (no proof angle without proof).\n\n## 4. Texts\n\nWrite `textos.json` (and nothing else by hand about texts):\n\n- Google: `{\"plataforma\": \"google\", \"url\": \"\u003CURL>\", \"titulos\": [...], \"descricoes\": [...], \"caminhos\": [...]}`. Titles are headlines, `caminhos` are the 0 to 2 display path parts (no spaces).\n- Meta: `{\"plataforma\": \"meta\", \"url\": \"\u003CURL>\", \"titulos\": [...], \"textos_principais\": [...]}`.\n\nRules:\n- `url` is exactly the URL from the prompt.\n- Counts and characters inside the limits printed by `--plano`. Count characters; cut and rewrite until they fit. Give the maximum useful number of distinct variations; never repeat one.\n- Every variation comes from one angle of `angulos`: write in `estrategia.md` which index is which angle (`titulos 1: dor`, ...). Variations differ in angle, not in synonyms. Google follows the mix above. Meta: each `textos_principais` item is a different angle with its hook at the start.\n- No AI tics from checklist-atencao.md.\n- Only facts from the briefing. Never promise a result (sales, clients, ranking, \"garantido\"), never write a price, discount, date or number that is not in the briefing. The script checks sizes and fields; `AN --exportar` also refuses AI tics and numbers that are not in the briefing (`entrada.md`) or the brand kit.\n- No text starts with `=`, `+`, `-` or `@`.\n\nThen run `AN --exportar W --plataforma P`. Exit 0 = `export\u002F` has the sheet. Exit 1 = it prints the problems: fix `textos.json` and run again (at most 2 fix rounds).\n\n## 5. Master image and adaptations\n\nFor each piece of the plan write `a\u003CN>\u002Ffonte\u002Findex.html`, sized `largura` x `altura` of that piece, with the skeleton, rules and forbidden list of the `post` skill (`#root` and `data-width`\u002F`data-height` = the piece size; CSS only; colors only through `--` variables; fonts only `Brand Heading` \u002F `Brand Body`; no `\u003Cscript>`, no URL, no `data-layout-*`, no `gsap`, no image other than `assets\u002Flogo.svg` and the files `fotos.py` printed).\n\n- **Google** (`P` = `google`): the sheet makes a Search campaign, and Google rejects a Search image asset that carries text, a logo or a graphic overlay. So a Google piece has **no text at all and no logo**. With a main photo, the piece is that photo and nothing else: one `\u003Cimg src=\"assets\u002Ffoto1.\u003Cext>\">` filling `#root` (`width:100%; height:100%; object-fit:cover`), no other element, the same photo in every ratio. Without photos, no `assets\u002F` folder and no `\u003Cimg>`: it is a clean picture of the product or scene of the briefing, drawn as one inline `\u003Csvg>` of shapes (`path`, `circle`, `rect`, gradients; no `\u003Ctext>`, no `\u003Cimage>`) in the brand colors only, on a brand-color background, one clear subject filling the middle. A frame of plain CSS boxes counts as empty for the check: the subject must be the `\u003Csvg>`. `a1` is the master; the adaptation draws the same subject re-laid for its ratio. The headline goes only in `titulos`.\n- **Meta** (`P` = `meta`): `a1` is the master: the chosen hook as its `\u003Ch1>` (one headline from `titulos`), at most one short supporting line with the proof or the offer, `id=\"cta\"` with the action and what the person gets on the *CTA band* with the channel icon (the briefing's condition and deadline on it, never cut), the brand name written next to the logo, and one visual device from recursos-visuais.md that shows the product or the situation (the photo when there is one; `AN --final` fails a Meta piece that is only text). Headline sentences break by `\u003Cbr>`, and every 1-2 letter word is glued with `&nbsp;`. `#root` carries one `l-*` arrangement of arquetipos-post.md; its type scale times 1.33 (the piece is 1440 wide). Design it first. A photo goes in a fixed box with `object-fit: cover`; text never sits directly on it: always on a solid brand-color band or block with a pair printed by `--pares` (write the pair and its ratio in `resultado.md`). The adaptation keeps the master's message, colors and hierarchy, re-laid for its ratio (stacked, with more room). Keep all text at least 80 px from the edges.\n- **The 9:16 piece** (Stories\u002FReels): the app covers its top 14% and bottom 20%. Put every text inside one `\u003Cdiv id=\"safezone\">`, styled by one rule that contains exactly `#safezone{position:absolute;top:14%;bottom:20%;left:80px;right:80px;overflow:hidden}`; nothing else names `safezone`, and no `position:fixed` or `!important` anywhere. Colors and shapes may fill the whole frame.\n- No fake button, no price or promise that is not in the briefing.\n\nBefore the QA of each Meta piece, Read its snapshot and score `checklist-atencao.md` (one image: 9 items, items 3, 6 and 12 skipped): any item at 0, fix the worst (it counts as a fix round). The per-piece QA runs without `--atencao`.\n\nPer piece (`HF` = `${CLAUDE_PLUGIN_ROOT}\u002Fnode\u002Fnode_modules\u002F.bin\u002Fhyperframes`, absolute path; one command each, no `cd`, `;`, `>` or `|`):\n\n1. `HF snapshot a\u003CN>\u002Ffonte --at 0 --no-end -o a\u003CN>\u002Fsnap` -> `a\u003CN>\u002Fsnap\u002Fframe-00-at-0s.png`.\n2. `HF check a\u003CN>\u002Ffonte --json --strict`. Do not copy its output anywhere.\n3. `python3 -I ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fqa_imagem.py --source a\u003CN>\u002Ffonte --png W\u002Fa\u003CN>\u002Fsnap\u002Fframe-00-at-0s.png --width \u003Clargura> --height \u003Caltura> --out a\u003CN>\u002Fqa.json`. Exit 0 = green. Never use `--formato` here. The \"no text\" (Google) and \"safe zone\" (9:16) rules are checked by `AN --final`, not here.\n\nFix rounds: if the QA is not green, read `a\u003CN>\u002Fqa.json`, edit `a\u003CN>\u002Ffonte\u002Findex.html` and redo steps 1 to 3. At most 2 fix rounds per piece. Never silence a check; never write inside `.hyperframes\u002F`. A `snapshot` check with `Fonts failed` means the brand font is not on this machine: do not swap it and do not spend fix rounds on it.\n\n## 6. Finish\n\n1. `AN --final W --plataforma P --out final.json`. It re-checks every piece at its own size, the texts and the sheet, and writes the final line in `linha`.\n2. Write `resultado.md`: platform, one line per piece (`a\u003CN>\u002Fsnap\u002Fframe-00-at-0s.png`, size, green or `precisa do seu olho` with the failed checks), every title and description, the sheet path (`export\u002Fgoogle-ads-editor.csv` or `export\u002Fmeta-experimental.csv`), and the sentence `Nada foi publicado; tudo está pausado.` Then where each image goes: Google: `As imagens não vão na planilha: depois de importar, adicione-as como recursos de imagem da campanha de Pesquisa (a 1:1 é a obrigatória).` Meta: `A planilha usa só a peça 4:5 (a1). A peça 9:16 (a2) sobe à mão no posicionamento Stories e Reels.` and `Planilha da Meta EXPERIMENTAL: o formato de importação não foi conferido numa fonte oficial.` Also `autoavaliacao: \u003Cscore>\u002F9 | pior: \u003Citem> | corrigido: sim|não` (Meta), the photos used (or `sem fotos`), anything left out (logo, missing brand field), each generic brand font reported by `fontes.py` and, from `faltou`, `Para a próxima peça, mande: ...` (skip it when `faltou: nada`).\n3. Answer with the `linha` of `final.json`, exactly. Do not list or re-check files after that.\n","# Ad (images, texts and a paused import sheet)\n\nThis runs in the background. Nobody answers questions: never ask anything, never wait for a reply, never run `ls` or any command outside the list below. When a step fails twice, write it down and finish. Ad copy is in Brazilian Portuguese; your final answer is one short line in Brazilian Portuguese.\n\nNothing is published. Never call an ad platform, never write a sheet by hand: the sheet comes only from `anuncio.py --exportar`.\n\nThe prompt gives: the working folder (`{trabalho}`, your current folder), `Plataforma` (`google` or `meta`, called `P` below), `URL` (the landing page) and the briefing file. Write only inside the working folder. Use relative paths made of letters, digits, `_`, `.` and `\u002F` only (no `-`, no `..`).\n\n`AN` = `python3 -I ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fanuncio.py`. `W` = the absolute path of the working folder.\n\n## 1. Plan\n\n1. Read the briefing file named in the prompt. The scripts read the facts only from `entrada.md` in the working folder (the panel writes the briefing there): if the prompt names another file, Write its exact text to `entrada.md` first. Without it `AN --exportar` and `AN --final` fail.\n2. Run `AN --plano P`. It prints the pieces (`a1` is the master, the next ones are the adaptations), each with `largura`, `altura` and `nome`, and the text limits: for each field `[min items, max items, max characters]`.\n3. Read once: `${CLAUDE_PLUGIN_ROOT}\u002Freferencias\u002Fganchos.md` and `checklist-atencao.md` (same folder); for Meta pieces also the *Arrangements* section of `arquetipos-post.md` and `recursos-visuais.md`. They hold the hook families, the regulated-niche rules, the self-check and the visual devices; this file does not repeat them.\n\nAd angles (each variation takes one; pt-BR molds from invented businesses):\n\n| angle | what it says | mold |\n|---|---|---|\n| situation or pain | the reader's situation or pain | `Carro fazendo barulho ao frear?` |\n| outcome | the result, with time | `Inglês para reunião em [N] meses` |\n| proof | number, rating or customer quote | `Nota [nota] em [N] avaliações` |\n| curiosity | the hidden detail | `O passo que evita [problema]` |\n| comparison | old way vs this one | `Sem planilha: o contador manda o DAS pronto` |\n| real urgency | a written limit | `Agenda de [mês] abre dia [dia]` |\n| identity | who it is for | `Para quem abriu o MEI este ano` |\n| objection | the doubt answered | `Atende sábado? Sim, das 8h às 13h.` |\n\nGoogle RSA mix: 3-4 headlines with benefit or keyword, 2-3 proof (only with proof in the briefing), 2-3 CTA, 1-2 differential, 1 brand; each makes sense alone, in any order. Meta: every primary text a different angle, the hook inside its first 125 characters. \"Agende já\" and \"Marque agora\" are one variation.\n\n## 2. Brand (read-only, as the `marca-ler` skill)\n\nSame as the `post` skill: read `\u003Croot>\u002F.tune-up\u002Festudio\u002Fmarca\u002Fmarca.json` (root = the working folder path cut right before `\u002F.tune-up\u002F`), use only `campos` colors and fonts, run `python3 -I ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Ffontes.py --trabalho W` once and paste every printed line at the top of each piece's `\u003Cstyle>`. Also read `campos.nome`, `campos.descricao` and the top-level `tom.valor` (voice). Contrast comes from a script, never from you: run `python3 -I ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fqa_imagem.py --pares W` once and use only the color pairs it prints (text 4.5:1 or more; a headline of 88 px or more may use a pair of 3:1 or more). Meta only (a Google piece carries no logo): an `.svg` logo in `\u003Croot>\u002F.tune-up\u002Festudio\u002Fmarca\u002Fassets\u002F`: Read it and Write the same text to `a\u003CN>\u002Ffonte\u002Fassets\u002Flogo.svg`; a PNG, JPEG or WebP logo comes only from `fotos.py --logo`; no logo file: leave it out and say so in `resultado.md`. Never write in the brand folder.\n\nPhotos: when `marca.json` has a non-empty `fotos` list, images come only from `python3 -I ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Ffotos.py --trabalho W --para a\u003CN>\u002Ffonte` (Meta: add `--logo`, up to 2 photos; Google: add `--quantas 1`, never `--logo`). It copies them as `assets\u002Ffoto1.\u003Cext>` (the main photo), `assets\u002Ffoto2.\u003Cext>` and prints one line per file: use exactly those names. Never pick, read or copy an image yourself, and never use an image made by AI, drawn to look like a photo, or from anywhere else.\n\n## 3. Strategy\n\nBefore any text, write `estrategia.md`, one key per line, `key: value`, exactly these keys:\n\n```\nobjetivo: vender | receber mensagens | encher a agenda | lançar novidade | ensinar e ganhar seguidores (inferred from the briefing as ganchos.md says, plus \" (inferido)\")\npublico: \u003Cone segment in one situation, from the briefing and campos.descricao>\nestagio: frio | morno | quente\npromessa: \u003Cone sentence the ad keeps, only briefing facts; never a promise of results>\nprova: \u003Cbriefing facts used as proof> | nenhuma\narquetipo: \u003Can archetype of arquetipos-post.md (Meta) or the main angle (Google)>\ngancho 1: [family] \u003Ctext> | nota \u003C0-5> | \u003Cone-line critique>\ngancho 2: ...\ngancho 3: ...\nescolhido: \u003C1|2|3> | \u003Cwhy>\ncta: \u003Ctext> | leve|média|forte\nangulos: \u003Cthe angles used in the variations, at least 3 from the table above>\nfaltou: \u003Cwhat the owner could send next time> | nada\n```\n\nThe 3 hooks come from 3 different families, scored with the rubric of ganchos.md; when the briefing names an audience or a situation, one speaks to it and the offer goes to the support line. For Meta they are the candidates for the headline of `a1` and each fits the `titulos` limit printed by `--plano`. Use an angle only if the briefing has what it needs (no proof angle without proof).\n\n## 4. Texts\n\nWrite `textos.json` (and nothing else by hand about texts):\n\n- Google: `{\"plataforma\": \"google\", \"url\": \"\u003CURL>\", \"titulos\": [...], \"descricoes\": [...], \"caminhos\": [...]}`. Titles are headlines, `caminhos` are the 0 to 2 display path parts (no spaces).\n- Meta: `{\"plataforma\": \"meta\", \"url\": \"\u003CURL>\", \"titulos\": [...], \"textos_principais\": [...]}`.\n\nRules:\n- `url` is exactly the URL from the prompt.\n- Counts and characters inside the limits printed by `--plano`. Count characters; cut and rewrite until they fit. Give the maximum useful number of distinct variations; never repeat one.\n- Every variation comes from one angle of `angulos`: write in `estrategia.md` which index is which angle (`titulos 1: dor`, ...). Variations differ in angle, not in synonyms. Google follows the mix above. Meta: each `textos_principais` item is a different angle with its hook at the start.\n- No AI tics from checklist-atencao.md.\n- Only facts from the briefing. Never promise a result (sales, clients, ranking, \"garantido\"), never write a price, discount, date or number that is not in the briefing. The script checks sizes and fields; `AN --exportar` also refuses AI tics and numbers that are not in the briefing (`entrada.md`) or the brand kit.\n- No text starts with `=`, `+`, `-` or `@`.\n\nThen run `AN --exportar W --plataforma P`. Exit 0 = `export\u002F` has the sheet. Exit 1 = it prints the problems: fix `textos.json` and run again (at most 2 fix rounds).\n\n## 5. Master image and adaptations\n\nFor each piece of the plan write `a\u003CN>\u002Ffonte\u002Findex.html`, sized `largura` x `altura` of that piece, with the skeleton, rules and forbidden list of the `post` skill (`#root` and `data-width`\u002F`data-height` = the piece size; CSS only; colors only through `--` variables; fonts only `Brand Heading` \u002F `Brand Body`; no `\u003Cscript>`, no URL, no `data-layout-*`, no `gsap`, no image other than `assets\u002Flogo.svg` and the files `fotos.py` printed).\n\n- **Google** (`P` = `google`): the sheet makes a Search campaign, and Google rejects a Search image asset that carries text, a logo or a graphic overlay. So a Google piece has **no text at all and no logo**. With a main photo, the piece is that photo and nothing else: one `\u003Cimg src=\"assets\u002Ffoto1.\u003Cext>\">` filling `#root` (`width:100%; height:100%; object-fit:cover`), no other element, the same photo in every ratio. Without photos, no `assets\u002F` folder and no `\u003Cimg>`: it is a clean picture of the product or scene of the briefing, drawn as one inline `\u003Csvg>` of shapes (`path`, `circle`, `rect`, gradients; no `\u003Ctext>`, no `\u003Cimage>`) in the brand colors only, on a brand-color background, one clear subject filling the middle. A frame of plain CSS boxes counts as empty for the check: the subject must be the `\u003Csvg>`. `a1` is the master; the adaptation draws the same subject re-laid for its ratio. The headline goes only in `titulos`.\n- **Meta** (`P` = `meta`): `a1` is the master: the chosen hook as its `\u003Ch1>` (one headline from `titulos`), at most one short supporting line with the proof or the offer, `id=\"cta\"` with the action and what the person gets on the *CTA band* with the channel icon (the briefing's condition and deadline on it, never cut), the brand name written next to the logo, and one visual device from recursos-visuais.md that shows the product or the situation (the photo when there is one; `AN --final` fails a Meta piece that is only text). Headline sentences break by `\u003Cbr>`, and every 1-2 letter word is glued with `&nbsp;`. `#root` carries one `l-*` arrangement of arquetipos-post.md; its type scale times 1.33 (the piece is 1440 wide). Design it first. A photo goes in a fixed box with `object-fit: cover`; text never sits directly on it: always on a solid brand-color band or block with a pair printed by `--pares` (write the pair and its ratio in `resultado.md`). The adaptation keeps the master's message, colors and hierarchy, re-laid for its ratio (stacked, with more room). Keep all text at least 80 px from the edges.\n- **The 9:16 piece** (Stories\u002FReels): the app covers its top 14% and bottom 20%. Put every text inside one `\u003Cdiv id=\"safezone\">`, styled by one rule that contains exactly `#safezone{position:absolute;top:14%;bottom:20%;left:80px;right:80px;overflow:hidden}`; nothing else names `safezone`, and no `position:fixed` or `!important` anywhere. Colors and shapes may fill the whole frame.\n- No fake button, no price or promise that is not in the briefing.\n\nBefore the QA of each Meta piece, Read its snapshot and score `checklist-atencao.md` (one image: 9 items, items 3, 6 and 12 skipped): any item at 0, fix the worst (it counts as a fix round). The per-piece QA runs without `--atencao`.\n\nPer piece (`HF` = `${CLAUDE_PLUGIN_ROOT}\u002Fnode\u002Fnode_modules\u002F.bin\u002Fhyperframes`, absolute path; one command each, no `cd`, `;`, `>` or `|`):\n\n1. `HF snapshot a\u003CN>\u002Ffonte --at 0 --no-end -o a\u003CN>\u002Fsnap` -> `a\u003CN>\u002Fsnap\u002Fframe-00-at-0s.png`.\n2. `HF check a\u003CN>\u002Ffonte --json --strict`. Do not copy its output anywhere.\n3. `python3 -I ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fqa_imagem.py --source a\u003CN>\u002Ffonte --png W\u002Fa\u003CN>\u002Fsnap\u002Fframe-00-at-0s.png --width \u003Clargura> --height \u003Caltura> --out a\u003CN>\u002Fqa.json`. Exit 0 = green. Never use `--formato` here. The \"no text\" (Google) and \"safe zone\" (9:16) rules are checked by `AN --final`, not here.\n\nFix rounds: if the QA is not green, read `a\u003CN>\u002Fqa.json`, edit `a\u003CN>\u002Ffonte\u002Findex.html` and redo steps 1 to 3. At most 2 fix rounds per piece. Never silence a check; never write inside `.hyperframes\u002F`. A `snapshot` check with `Fonts failed` means the brand font is not on this machine: do not swap it and do not spend fix rounds on it.\n\n## 6. Finish\n\n1. `AN --final W --plataforma P --out final.json`. It re-checks every piece at its own size, the texts and the sheet, and writes the final line in `linha`.\n2. Write `resultado.md`: platform, one line per piece (`a\u003CN>\u002Fsnap\u002Fframe-00-at-0s.png`, size, green or `precisa do seu olho` with the failed checks), every title and description, the sheet path (`export\u002Fgoogle-ads-editor.csv` or `export\u002Fmeta-experimental.csv`), and the sentence `Nada foi publicado; tudo está pausado.` Then where each image goes: Google: `As imagens não vão na planilha: depois de importar, adicione-as como recursos de imagem da campanha de Pesquisa (a 1:1 é a obrigatória).` Meta: `A planilha usa só a peça 4:5 (a1). A peça 9:16 (a2) sobe à mão no posicionamento Stories e Reels.` and `Planilha da Meta EXPERIMENTAL: o formato de importação não foi conferido numa fonte oficial.` Also `autoavaliacao: \u003Cscore>\u002F9 | pior: \u003Citem> | corrigido: sim|não` (Meta), the photos used (or `sem fotos`), anything left out (logo, missing brand field), each generic brand font reported by `fontes.py` and, from `faltou`, `Para a próxima peça, mande: ...` (skip it when `faltou: nada`).\n3. Answer with the `linha` of `final.json`, exactly. Do not list or re-check files after that.\n",{"name":5,"description":7,"allowed-tools":23},"Read, Bash(${CLAUDE_PLUGIN_ROOT}\u002Fnode\u002Fnode_modules\u002F.bin\u002Fhyperframes *), Bash(python3 -I ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fqa_imagem.py *), Bash(python3 -I ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Ffontes.py *), Bash(python3 -I ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Ffotos.py *), Bash(python3 -I ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fanuncio.py *)","main","bbde73350fc3c138bffa1e546839b190e0d415bc","tune-up-studio\u002Fskills\u002Fanuncio",0,"https:\u002F\u002Fgithub.com\u002Fstage2dev\u002Ftune-up","https:\u002F\u002Fgithub.com\u002Fstage2dev","Tuning the unnecessary.","2026-11-14 05:05:23",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add stage2dev\u002Ftune-up --skill anuncio",{"tool":38,"command":39},"bunx","bunx skills add stage2dev\u002Ftune-up --skill anuncio",{"tool":41,"command":42},"pnpm","pnpm dlx skills add stage2dev\u002Ftune-up --skill anuncio","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstage2dev\u002Ftune-up\u002Fblob\u002Fmain\u002Ftune-up-studio\u002Fskills\u002Fanuncio\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M7F6Z7DAMCW5ES2ED8FGCC8C","instalar","One-step setup of the WhatsApp sales screen on this computer: Docker, the local Evolution API and the sales service, step by step in plain words. Use on: install, set up WhatsApp, prepare sales; instalar, preparar, preparar o WhatsApp, setup WhatsApp, configurar vendas.","https:\u002F\u002Fgithub.com\u002Fstage2dev\u002Ftune-up\u002Fblob\u002Fmain\u002Fvendas\u002Fskills\u002Finstalar\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M7F6Z0BKKW3MGNAM1NJ16JHV","video","Makes a hook-first, business-oriented silent vertical reel (9:16, 1080x1920 MP4, 10 or 15 s) from a briefing, using only the owner-approved brand: strategy, the reel composition of the studio kit filled with the script and a hero drawn for this briefing, motion by the studio JavaScript engine (seek-safe, no network), render or slide reserve, and the studio QA. Runs unattended from the panel actions estudio.video and estudio.video-motion. Use on: vídeo, reel, reels, story em vídeo.","https:\u002F\u002Fgithub.com\u002Fstage2dev\u002Ftune-up\u002Fblob\u002Fmain\u002Ftune-up-studio\u002Fskills\u002Fvideo\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7F6YS17B793E58C07S5EX5R","post","Makes a hook-first, business-oriented still post or carousel (PNG per frame) from a briefing, using only the owner-approved brand: strategy first, one chosen hook, a composition of the studio kit with a hero drawn for this briefing, one call to action, and every frame checked by the studio QA. Runs unattended from the panel action estudio.post. Use on: post, carrossel, carousel, peça estática, post do Instagram.","https:\u002F\u002Fgithub.com\u002Fstage2dev\u002Ftune-up\u002Fblob\u002Fmain\u002Ftune-up-studio\u002Fskills\u002Fpost\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7F6YFJNJP6PT3YTFEBRQW9V","marca","Discovers the project's brand (colors, fonts, logo, name) from its own files and shows it to the owner for approval in the panel. Use on: discover the brand, descobrir marca, identidade visual do projeto, marca do estúdio.","https:\u002F\u002Fgithub.com\u002Fstage2dev\u002Ftune-up\u002Fblob\u002Fmain\u002Ftune-up-studio\u002Fskills\u002Fmarca\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7F6YBJ20F1GJN7ZFJJK8Y7Y","marca-ler","Reads the project's brand (marca.json) and says whether the owner approved it. Read-only: never approves, edits or writes anything. Use on: read the brand, is the brand approved, ler marca, marca aprovada.","https:\u002F\u002Fgithub.com\u002Fstage2dev\u002Ftune-up\u002Fblob\u002Fmain\u002Ftune-up-studio\u002Fskills\u002Fmarca-ler\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7F6XXKWAG54EWAE7DC3E5BM","connect","Guides the owner through connecting their own marketing accounts one service at a time, checks each connection read-only and records the result. Use on: connect my marketing accounts, set up marketing, what is missing; conectar contas de marketing, cadastro, o que falta.","https:\u002F\u002Fgithub.com\u002Fstage2dev\u002Ftune-up\u002Fblob\u002Fmain\u002Ftune-up-mkt\u002Fskills\u002Fconnect\u002FSKILL.md",[],[]]