wizz-method 2.18.0 → 2.19.0

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "wizz-method",
-  "version": "2.18.0",
+  "version": "2.19.0",
   "description": "Wizz Method: método de agência orientado por IA em PT-BR",
   "keywords": [
     "agile",
@@ -61,6 +61,7 @@
     "format:check": "prettier --check \"**/*.{js,cjs,mjs,json,yaml}\"",
     "format:fix": "prettier --write \"**/*.{js,cjs,mjs,json,yaml}\"",
     "format:fix:staged": "prettier --write",
+    "generate:dispatch-rule": "node tools/generate-dispatch-rule.mjs",
     "generate:subagents": "node tools/generate-subagents.mjs",
     "install:wizz": "node tools/installer/wizz-cli.js install",
     "lint": "eslint . --ext .js,.cjs,.mjs,.yaml --max-warnings=0",
@@ -68,8 +69,9 @@
     "lint:md": "markdownlint-cli2 \"**/*.md\"",
     "prepare": "command -v husky >/dev/null 2>&1 && husky || exit 0",
     "quality": "npm run format:check && npm run lint && npm run lint:md && npm run docs:build && npm run quality:validate",
-    "quality:validate": "npm test && npm run validate:refs && npm run validate:registry-schema && npm run validate:method-refs && npm run validate:model-ids && npm run validate:skills && npm run docs:validate-sidebar && npm run validate:generated && npm run eval:routing && npm run eval:feature && npm run eval:output",
+    "quality:validate": "npm test && npm run validate:refs && npm run validate:registry-schema && npm run validate:method-refs && npm run validate:model-ids && npm run validate:skills && npm run docs:validate-sidebar && npm run docs:validate-links && npm run validate:generated && npm run eval:routing && npm run eval:feature && npm run eval:output",
     "rebundle": "node tools/bundle-web-bundles.js",
+    "release": "node tools/release.mjs",
     "sync:check": "node tools/sync-check.mjs",
     "sync:global": "node tools/sync-global.mjs",
     "test": "node test/run-tests.js && npm run sync:check",
@@ -122,7 +124,7 @@
     "test:trace-report": "node test/test-trace-report.js",
     "test:urls": "node test/test-parse-source-urls.js",
     "test:workflow-path-regex": "node test/test-workflow-path-regex.js",
-    "validate:generated": "npm run test:dispatch-rule && npm run test:routing-table-refs && npm run test:subagents-parity",
+    "validate:generated": "npm run test:dispatch-rule && node tools/generate-dispatch-rule.mjs --check && npm run test:routing-table-refs && npm run test:subagents-parity",
     "validate:method-refs": "node tools/validate-method-refs.js --strict",
     "validate:model-ids": "node tools/validate-model-ids.mjs",
     "validate:refs": "node tools/validate-file-refs.js --strict",

package/removals.txt

@@ -69,3 +69,13 @@ taste-redesign
 
 # Removida na auditoria de contexto (2026-08-28): knowledge graph descontinuado.
 graphify
+
+# Renomeadas para o prefixo wizz- (2026-10-15): as 7 que ficavam de fora.
+# Nesses caminhos do projeto quem escrevia era o próprio install do Wizz.
+cerebro
+ctc-align
+enhance-prompt
+find-skills
+pesquisa-de-publico-do-piva
+security-audit-pentest
+site-launch-kit

package/skills-registry.yaml

@@ -171,7 +171,7 @@ areas:
         door: motion
         when: "MONTAR o filme: vídeo em React (Remotion) com áudio, SFX, legenda e timing com precisão de frame. No pipeline de vídeo é o Remotion que faz a montagem final; o hyperframes só desenha as telas mudas (regra: HyperFrames desenha, Remotion monta — ver _shared/video-pipeline.md do módulo wizz)."
         rel:
-          after: [buttercut, ctc-align, get-brolls, hyperframes, wizz-motion-3d-director, wizz-video-effects, wizz-video-styles]
+          after: [buttercut, wizz-ctc-align, get-brolls, hyperframes, wizz-motion-3d-director, wizz-video-effects, wizz-video-styles]
       - id: wizz-canvas-design
         door: motion
         when: "Gerar PNG/PDF editável por código (carrossel, quote card, infográfico) com fonte/cor/logo sempre certos. Traz canvas-fonts."
@@ -182,10 +182,11 @@ areas:
         when: "Visual generativo por código (flow fields, ruído, partículas) para fundo/textura de hero, único a cada render, sem cara de banco de imagem."
         rel:
           pairs_with: [wizz-canvas-design]
-      - id: ctc-align
+      - id: wizz-ctc-align
         door: motion
         when: "Timing por forced alignment: timestamps palavra a palavra de narração TTS para sincronizar legenda, corte de cena e animação com a fala. Fonte única de timing no pipeline de vídeo; substitui Whisper e estimativa manual."
         rel:
+          pairs_with: [ctc-align]
           after: [voicebox, wizz-video-styles]
           before: [wizz-remotion-best-practices, wizz-video-effects]
       # Motor de decisão de efeitos (Python) portado do sistema de efeitos do
@@ -199,19 +200,20 @@ areas:
           - "Montar o filme em React (sequência de cenas, legenda, <Audio>): é wizz-remotion-best-practices; esta skill decide os efeitos que ele monta."
           - "Filme de lançamento de produto com trilha e direção visual: é wizz-huashu-design."
         rel:
-          after: [ctc-align, hyperframes, wizz-video-styles]
+          after: [wizz-ctc-align, hyperframes, wizz-video-styles]
           before: [wizz-remotion-best-practices]
           pairs_with: [wizz-ad-creative]
-      # Catálogo de estilos de vídeo curto medido em 104 shorts reais: decide QUAL
+      # Catálogo de estilos de vídeo curto medido em 110 vídeos reais: decide QUAL
       # estilo copiar antes de voz, timing, efeitos e montagem.
       - id: wizz-video-styles
         door: motion
-        when: "Decidir QUAL estilo de vídeo curto copiar a partir do inventário do material (pessoa real, só voz, b-roll, telas, produto) e entregar a receita medida em 104 shorts reais (ritmo de corte, legenda, áudio, zoom, gancho), para qualquer nicho, inclusive clipe com a letra da música e tipografia cinética (texto como imagem, cortes na batida). Gatilhos: 'estilo do vídeo', 'editar no estilo de', 'copiar a edição de', 'que estilo usar no reel', 'o vídeo ficou amador', 'clipe com a letra', 'tipografia cinética'."
+        when: "Decidir QUAL estilo de vídeo curto copiar a partir do inventário do material (pessoa real, só voz, b-roll, telas, produto) e entregar a receita medida em 110 vídeos reais (ritmo de corte, legenda, áudio, zoom, gancho), para qualquer nicho, inclusive clipe com a letra da música, tipografia cinética (texto como imagem, cortes na batida) e vídeo do app só com a interface (UI morph: uma forma vira cada tela, cursor conduz, estilo Dribbble). Gatilhos: 'estilo do vídeo', 'editar no estilo de', 'copiar a edição de', 'que estilo usar no reel', 'o vídeo ficou amador', 'clipe com a letra', 'tipografia cinética', 'vídeo do app mexendo', 'anima o app num vídeo', 'animação da interface tipo Dribbble'."
         not_when:
           - "Decidir efeitos e SFX por evento, volume, LUFS e portões de zona segura: é wizz-video-effects; esta skill escolhe o estilo que ele depois refina."
           - "Montar o filme em React (cenas, legenda, <Audio>): é wizz-remotion-best-practices."
+          - "Animar componente dentro do código do app (hover, transição de página, modal): é wizz-animate; aqui é vídeo para divulgar."
         rel:
-          before: [ctc-align, wizz-video-effects, wizz-remotion-best-practices]
+          before: [wizz-ctc-align, wizz-video-effects, wizz-remotion-best-practices]
           pairs_with: [wizz-social-content, get-brolls, hyperframes, wizz-hook-extractor]
     clis:
       - id: hyperframes
@@ -256,7 +258,7 @@ areas:
           - "Cortar/montar footage já captado: é buttercut (corte fino) ou wizz-remotion-best-practices (montagem final)."
           - "Gerar imagem/vídeo por IA: é wizz-ad-creative, que escreve o prompt para o usuário colar no Flow ou em outra IA. O get-brolls busca material REAL, não sintético."
           - "Desenhar uma tela/cena em HTML: é hyperframes."
-          - "Minerar/estudar criativo ou oferta de concorrente (Biblioteca de Anúncios, 'baixa esse anúncio pra eu ver'): é wizz-lowticket-minerador na área ads. O get-brolls capta insert para a SUA edição, com procedência registrada — não é ferramenta de inteligência competitiva, e o fato de saber baixar um Reel não o torna uma."
+          - "Minerar/estudar criativo ou oferta de concorrente (Biblioteca de Anúncios, 'baixa esse anúncio pra eu ver'): é wizz-lowticket-minerador na área growth. O get-brolls capta insert para a SUA edição, com procedência registrada — não é ferramenta de inteligência competitiva, e o fato de saber baixar um Reel não o torna uma."
         rel:
           after: [wizz-social-content]
           before: [buttercut, wizz-remotion-best-practices]
@@ -298,7 +300,7 @@ areas:
       - id: voicebox
         when: "Voz/TTS/clonagem de voz local para narração/VO de vídeo (7 engines TTS + Whisper STT). App desktop que expõe endpoint MCP local em runtime. Clone-and-run no projeto."
         rel:
-          before: [ctc-align]
+          before: [wizz-ctc-align]
         platform: [darwin, linux]
         # Clone-and-run: o próprio repo responde o SHA, então o check compara com o
         # pin. O install repara um clone existente em vez de falhar no git clone.
@@ -306,10 +308,9 @@ areas:
         # Pin de supply chain (2026-08-23): checkout de SHA fixo; atualizar conscientemente.
         install: "{ [ -d voicebox/.git ] || git clone https://github.com/jamiepine/voicebox.git voicebox; } && git -C voicebox fetch --tags origin && git -C voicebox checkout 2bcb98d1a8b6fe05e15fbc1559e3085669e4035d"
       - id: ctc-align
-        when: "Timestamps palavra a palavra CONFIÁVEIS de narração TTS (texto conhecido): sincronizar legenda, corte de cena, animação e elemento gráfico com a fala. Fonte única de timing em vídeo — substitui timestamps do Whisper e estimativa manual. Skill da lib: ctc-align (instalação + helper align.py + regras de âncora monotônica e duração mínima). Roda em CPU, sem CUDA."
+        when: "Timestamps palavra a palavra CONFIÁVEIS de narração TTS (texto conhecido): sincronizar legenda, corte de cena, animação e elemento gráfico com a fala. Fonte única de timing em vídeo — substitui timestamps do Whisper e estimativa manual. Skill da lib: wizz-ctc-align (instalação + helper align.py + regras de âncora monotônica e duração mínima). Roda em CPU, sem CUDA."
         rel:
-          after: [voicebox, wizz-video-styles]
-          before: [wizz-remotion-best-practices, wizz-video-effects]
+          pairs_with: [wizz-ctc-align]
         platform: [darwin, linux]
         # O pip grava o commit instalado no direct_url.json: o check compara com o pin.
         check: "test -x ./tools/ctc-align/.venv/bin/ctc-forced-aligner && grep -qs 64293cc6d711e57666c4a8b098e9fd93b381fd88 ./tools/ctc-align/.venv/lib/python*/site-packages/ctc_forced_aligner-*.dist-info/direct_url.json"
@@ -336,16 +337,18 @@ areas:
     agent: wizz-copy
     summary: "Copywriting: texto de venda, headlines, páginas, e-mails, sequências."
     skills:
-      # Módulo lowticket: as skills dele moram SÓ na área growth desde
-      # 2026-09-18 (decisão do dono: um dono por skill). A copy chega nelas
-      # pelo `rel` de wizz-copywriting — que é o caminho que o método usa pra
-      # tudo mais. Antes a mesma skill existia em copy, growth e ads, e o
+      # Módulo lowticket: um dono por skill desde 2026-09-18 (decisão do
+      # dono). Guia, metodologia, funil, minerador e página moram em growth;
+      # wizz-lowticket-trafego mora em ads (campanha Meta, bid cap, régua de
+      # corte é trabalho de ads; confirmado pelo dono em 2026-10-15). A copy
+      # chega nelas pelo `rel` de wizz-copywriting — que é o caminho que o
+      # método usa pra tudo mais. Antes a mesma skill existia em copy, growth e ads, e o
       # eval mostrava o custo: "qual prazo de garantia?" respondia copy,
       # growth ou ads em amostras diferentes, porque as três estavam certas.
       - id: wizz-copywriting
         when: "Escrever copy de venda/página/headline do zero ou reescrever. Na página de vendas completa, incluir wizz-offer-forge se faltar oferta aprovada e wizz-page-cro se faltar estrutura de conversão aprovada; headline/CTA isolado ou texto sobre oferta e estrutura já aprovadas não exige refazê-las."
         rel:
-          after: [pesquisa-de-publico-do-piva, wizz-offer-forge]
+          after: [wizz-pesquisa-de-publico-do-piva, wizz-offer-forge]
           before: [wizz-copy-editing]
           pairs_with:
             [
@@ -396,7 +399,7 @@ areas:
         when: "Implementar dados estruturados / structured data."
         rel:
           after: [wizz-seo-audit]
-          pairs_with: [site-launch-kit, wizz-ai-seo]
+          pairs_with: [wizz-site-launch-kit, wizz-ai-seo]
       - id: wizz-programmatic-seo
         when: "Gerar páginas em escala pra atacar muitas keywords."
         rel:
@@ -496,18 +499,18 @@ areas:
         when: "Setar/auditar tracking e medição (GA4, GTM, eventos, UTM, atribuição)."
         rel:
           pairs_with: [wizz-ab-test-setup, wizz-referral-program, wizz-tracking-audit]
-      - id: site-launch-kit
+      - id: wizz-site-launch-kit
         when: "Site pronto ou quase pronto pra ir ao ar: revisão de pré-lançamento em 15 rodadas corretivas (CTA acima da dobra, barra fixa mobile, tempo de resposta, prova social real, FAQ+FAQPage, imagens reais, endereço, titles, Open Graph, breadcrumbs, alt text, schema local, robots/sitemap, LGPD, medição), com regra anti-invenção e PENDÊNCIAS. Gatilhos: 'vamos subir o site', 'checklist de lançamento', 'revisa antes do deploy', pré-go-live, ou um item isolado (og:image, FAQ com schema, robots.txt). Roda DEPOIS do site construído, ANTES do deploy."
         rel:
           pairs_with: [wizz-launch-readiness, wizz-schema-markup]
-      - id: pesquisa-de-publico-do-piva
+      - id: wizz-pesquisa-de-publico-do-piva
         when: "Pesquisa profunda de público, VoC, níveis de consciência, matriz de ângulos e léxico nativo de oferta compilados em HTML (metodologia @soupiva)."
         rel:
           before: [wizz-copywriting, wizz-offer-forge]
       - id: wizz-offer-forge
         when: "Forjar oferta irresistível de resposta direta/infoproduto (mecanismo único, empilhamento de valor, garantia reversa, ponte de tráfego)."
         rel:
-          after: [pesquisa-de-publico-do-piva, wizz-lowticket-minerador]
+          after: [wizz-pesquisa-de-publico-do-piva, wizz-lowticket-minerador]
           before: [wizz-copywriting]
           pairs_with: [wizz-ig-profile-optimizer, wizz-pricing-strategy, wizz-lowticket-metodologia]
       # Módulo lowticket (src/modules/lowticket) — ver nota em ads.skills. Desde
@@ -682,7 +685,7 @@ areas:
       - id: wizz-web-security
         when: "Auditar segurança web, OWASP, XSS/CSRF/injeção/SQLi, IDOR, headers, rate limit (IP+conta), CORS, clickjacking, vazamento de PII na resposta, antes de deploy/PR."
         rel:
-          before: [security-audit-pentest]
+          before: [wizz-security-audit-pentest]
           pairs_with: [wizz-auth-and-secrets, wizz-database-and-deps, wizz-desktop-security]
       - id: wizz-auth-and-secrets
         when: "Auth (JWT/OAuth/SSO/Clerk), token no header vs URL, revogar no logout, enumeração de usuário, gestão de secrets, rotação de credenciais."
@@ -719,7 +722,7 @@ areas:
       - id: wizz-ai-product-design
         when: "Construir/melhorar um agente ou produto de IA: escrever/revisar system prompt, definir persona/tom, guardrails e recusas, few-shot, chain-of-thought, orquestração multi-agente, handoff, detecção de frustração, generative UI, avaliar qualidade de saída. Base para desenhar os próprios agentes do método. 44 padrões (Owl-Listener, MIT)."
         rel:
-          pairs_with: [enhance-prompt]
+          pairs_with: [wizz-enhance-prompt]
     mcps:
       - id: supabase
         when: "Operar Supabase de verdade: rodar SQL, migrations, inspecionar schema/RLS, logs. Default é READ-ONLY e escopado a um projeto (--read-only --project-id); para ESCREVER (migrations, mutações), o agente precisa remover conscientemente o --read-only desta entrada antes de usar — nunca por padrão silencioso."
@@ -771,19 +774,19 @@ areas:
         when: "Passe único adversarial, ad hoc, fora de workflow — 'tear this apart' num trecho colado, sem contexto de projeto. Não confundir com wizz-review-adversarial-general (persona do 'Blind Hunter'; o prompt operacional vive em review-prompts/blind-hunter.md e nenhum workflow invoca a skill) nem com wizz-code-review (orquestrador bmm: 3 camadas paralelas + triagem, para review real de diff/PR)."
         rel:
           instead_of: [wizz-code-review]
-      - id: security-audit-pentest
+      - id: wizz-security-audit-pentest
         when: "Auditoria/pentest de segurança do app inteiro — 'auditar segurança', 'pentest', 'encontrar vulnerabilidades', varredura antes de release. Só para teste de segurança AUTORIZADO (seus sistemas ou de clientes com permissão): ferramenta dual-use, nunca usar contra alvo sem autorização."
         rel:
           after: [wizz-web-security]
           pairs_with: [strix, wizz-launch-readiness]
       - id: wizz-launch-readiness
-        when: "Auditoria de prontidão pra lançamento (Pre-launch Audit), multi-área: técnico/build, segurança, SEO/descoberta, analytics/medição, conteúdo/copy/prova social, legal/LGPD, infra/deploy/rollback. Gatilhos: 'tá pronto pra lançar?', 'auditoria de pré-lançamento', 'checklist de release amplo', 'o que falta antes de ir pra produção'. Gate por estágio: só roda de verdade em mvp/production, e recusa educadamente em estágio de descoberta/ideação. Diagnostica e prioriza por severidade (bloqueia/alto/médio/ok), nunca corrige cego: aponta security-audit-pentest pra aprofundar segurança com prova de exploração e site-launch-kit pra executar a correção quando a superfície do achado é site. Resultado persiste numa seção datada do project-context.md."
+        when: "Auditoria de prontidão pra lançamento (Pre-launch Audit), multi-área: técnico/build, segurança, SEO/descoberta, analytics/medição, conteúdo/copy/prova social, legal/LGPD, infra/deploy/rollback. Gatilhos: 'tá pronto pra lançar?', 'auditoria de pré-lançamento', 'checklist de release amplo', 'o que falta antes de ir pra produção'. Gate por estágio: só roda de verdade em mvp/production, e recusa educadamente em estágio de descoberta/ideação. Diagnostica e prioriza por severidade (bloqueia/alto/médio/ok), nunca corrige cego: aponta wizz-security-audit-pentest pra aprofundar segurança com prova de exploração e wizz-site-launch-kit pra executar a correção quando a superfície do achado é site. Resultado persiste numa seção datada do project-context.md."
         not_when:
           - "Estágio de descoberta/ideação: projeto ainda sem superfície construída pra auditar (sem project-context.md, ou stage 'prototype' vazio)."
-          - "Correção de um achado isolado de site já identificado: nesse caso vá direto pra site-launch-kit."
+          - "Correção de um achado isolado de site já identificado: nesse caso vá direto pra wizz-site-launch-kit."
         rel:
-          pairs_with: [security-audit-pentest, site-launch-kit, wizz-database-and-deps]
-      - id: site-launch-kit
+          pairs_with: [wizz-security-audit-pentest, wizz-site-launch-kit, wizz-database-and-deps]
+      - id: wizz-site-launch-kit
         when: "Site pronto ou quase pronto pra ir ao ar: revisão de pré-lançamento em 15 rodadas corretivas (CTA acima da dobra, barra fixa mobile, tempo de resposta, prova social real, FAQ+FAQPage, imagens reais, endereço, titles, Open Graph, breadcrumbs, alt text, schema local, robots/sitemap, LGPD, medição), com regra anti-invenção e PENDÊNCIAS. Gatilhos: 'vamos subir o site', 'checklist de lançamento', 'revisa antes do deploy', pré-go-live, ou um item isolado (og:image, FAQ com schema, robots.txt). Roda DEPOIS do site construído, ANTES do deploy."
         rel:
           pairs_with: [wizz-launch-readiness, wizz-schema-markup]
@@ -800,10 +803,10 @@ areas:
         # Pin de supply chain (2026-08-23): versão fixa; atualizar conscientemente.
         install: "npm install -g agent-browser@0.38.1"
       - id: strix
-        when: "CONDICIONAL, nunca default — executor de pentest AUTÔNOMO e OFENSIVO (agentes de IA que rodam o app, exploram e VALIDAM vulnerabilidades com PoC real). Complementa security-audit-pentest: aquela skill é a metodologia/checklist humana; o Strix é o executor automatizado. Ferramenta dual-use: SÓ contra alvo próprio ou com AUTORIZAÇÃO ESCRITA do dono do sistema e ESCOPO definido — nunca contra alvo de terceiros sem permissão. Roda SEMPRE dentro do sandbox Docker isolado que a própria ferramenta provê (jamais direto no host). Gate condicional: ofereça apenas mediante confirmação explícita do usuário, com escopo e autorização declarados; jamais acione por padrão silencioso. RETORNO DEFENSIVO OBRIGATÓRIO: o executor (subagente) SEMPRE devolve o achado em formato defensivo — falha, severidade, evidência mínima e correção — nunca payload/exploit cru ou arma pronta; assim o revisor recebe conteúdo defensivo pra corrigir, não instrução de ataque. Precisa de Docker rodando e de uma LLM API key configurada."
+        when: "CONDICIONAL, nunca default — executor de pentest AUTÔNOMO e OFENSIVO (agentes de IA que rodam o app, exploram e VALIDAM vulnerabilidades com PoC real). Complementa wizz-security-audit-pentest: aquela skill é a metodologia/checklist humana; o Strix é o executor automatizado. Ferramenta dual-use: SÓ contra alvo próprio ou com AUTORIZAÇÃO ESCRITA do dono do sistema e ESCOPO definido — nunca contra alvo de terceiros sem permissão. Roda SEMPRE dentro do sandbox Docker isolado que a própria ferramenta provê (jamais direto no host). Gate condicional: ofereça apenas mediante confirmação explícita do usuário, com escopo e autorização declarados; jamais acione por padrão silencioso. RETORNO DEFENSIVO OBRIGATÓRIO: o executor (subagente) SEMPRE devolve o achado em formato defensivo — falha, severidade, evidência mínima e correção — nunca payload/exploit cru ou arma pronta; assim o revisor recebe conteúdo defensivo pra corrigir, não instrução de ataque. Precisa de Docker rodando e de uma LLM API key configurada."
         not_when: "Sem alvo próprio ou sem autorização escrita e escopo definido do dono do sistema; nunca acionar por padrão silencioso."
         rel:
-          pairs_with: [security-audit-pentest]
+          pairs_with: [wizz-security-audit-pentest]
         platform: [darwin, linux]
         check: "command -v strix"
         # Pin de supply chain (2026-08-25): versão fixa do pacote pip; o sandbox
@@ -845,6 +848,13 @@ areas:
         when: "DEV PONTUAL: ajuste, bug fix, feature única sem cerimônia de story. Fluxo unificado: clarificar → planejar → implementar → review → apresentar. É o destino padrão quando o router/maestro diz 'dev pontual'."
         rel:
           after: [wizz-implementation-planner, wizz-investigate]
+      # Também em designer, como porta de motion (2026-10-15): animar algo no
+      # código do app é do dev, e sem esta entrada o dev não enxergava o craft.
+      - id: wizz-animate
+        when: "Implementar micro-interação de um componente que já existe no app (hover, clique, toast, modal, popover) com o craft do Emil Kowalski: saída mais rápida que a entrada, só transform/opacity, reduced-motion."
+        not_when:
+          - "Animação de página inteira ou de entrada no scroll, em que o movimento ainda não foi decidido: é do designer (wizz-animate como porta de motion)."
+          - "Vídeo para divulgar o app: é wizz-video-styles."
       - id: wizz-dev-story
         module: bmm
         when: "Implementar UMA story específica com spec preenchida ('dev this story', 'implementa a próxima story do sprint')."
@@ -855,7 +865,7 @@ areas:
         module: bmm
         when: "Preparar story com todo o contexto de implementação ('cria a story', 'prepara a story'). Antes do dev, no gate de planejamento."
         rel:
-          after: [wizz-prd, wizz-set-feature, wizz-sprint-planning]
+          after: [wizz-prd, wizz-sprint-planning]
           before: [wizz-dev-story]
       - id: wizz-code-review
         module: bmm
@@ -894,7 +904,7 @@ areas:
         when: "Criar, atualizar ou validar PRD ('cria o PRD', 'documento de requisitos', 'define o escopo'). Consolida os antigos create/edit/validate-prd (removidos em v7)."
         rel:
           after: [wizz-product-brief]
-          before: [wizz-create-story, wizz-set-feature]
+          before: [wizz-create-story]
           pairs_with: [wizz-ux]
       - id: wizz-product-brief
         module: bmm
@@ -907,12 +917,14 @@ areas:
         when: "Desafio Working Backwards PRFAQ para forjar conceito de produto ('cria a PRFAQ', 'work backwards')."
         rel:
           before: [wizz-product-brief]
+      # Ajuste MANUAL da feature ativa. Desde a 2.16 a feature é definida sozinha
+      # (branch > config > primeiro pedido nomeado, via `wizz-feature.js definir`,
+      # regra em src/modules/wizz/_shared/organizacao.md), então esta entrada fica
+      # fora da cadeia PRD → story: sem `rel`, de propósito.
       - id: wizz-set-feature
         module: bmm
-        when: "Definir feature específica dentro do produto (análise de feature única)."
-        rel:
-          after: [wizz-prd]
-          before: [wizz-create-story]
+        when: "Trocar, renomear, limpar ou forçar a feature ativa de propósito, ou dizer qual está ativa ('muda a feature ativa', 'renomeia a feature', 'qual feature está ativa')."
+        not_when: "Começar, planejar ou especificar uma feature nova: o hook define a feature ativa sozinho."
 
   tech-writer:
     agent: wizz-agent-tech-writer
@@ -938,16 +950,16 @@ areas:
     agent: wizz-memoria
     summary: "Memória do projeto: o que foi decidido, salvar, ver estado."
     skills:
-      - id: cerebro
+      - id: wizz-cerebro
         when: "Recuperar/salvar decisões, contexto, aprendizados; ver estado do projeto (/ver, /salvar, /decisao, /dump); ler a auto-memória fora do Claude Code (/memoria)."
 
 # ─────────────────────────────────────────────────────────────────────────────
 # UTILITÁRIOS — cross-cutting, não pertencem a uma área só.
 # ─────────────────────────────────────────────────────────────────────────────
 utility:
-  - id: find-skills
+  - id: wizz-find-skills
     when: "Nenhuma skill cobre o pedido: buscar/instalar no marketplace (npx skills find)."
-  - id: enhance-prompt
+  - id: wizz-enhance-prompt
     when: "Empacotar um briefing mais completo/estruturado pra mandar a outro agente ou skill."
     rel:
       pairs_with: [wizz-ai-product-design]

package/src/bmm-skills/1-analysis/wizz-set-feature/SKILL.md

@@ -1,33 +1,33 @@
 ---
 name: wizz-set-feature
-description: 'Resolve, switch or clear the active feature context so planning artifacts, implementation artifacts and memory are organized under one named slug. Runs automatically from the git branch; only invoke it when the user says "set feature", "switch feature", "new feature", "clear feature", or asks "what feature is active".'
+description: 'Manual override for the active feature: rename, switch or clear it, or answer which feature is active. The feature is resolved automatically (git branch, config, the request itself) by the hooks and the `wizz-feature.js definir` CLI; invoke this skill only when the user says "set feature", "switch feature", "rename feature", "clear feature", or asks "what feature is active".'
 ---
 
 # Set Feature
 
 **Goal:** Keep `active_feature` correct so planning artifacts, implementation artifacts and memory entries all land under the same named slug.
 
-**Default mode is automatic, with or without git, on `main` or on a branch.** The hooks do the work and nobody invokes this skill in the normal case:
+**This skill is the manual override, not the way the feature gets set.** Setting the feature is automatic, with or without git, on `main` or on a branch: the hooks and the area agents do it with the CLI `node _wizz/hooks/wizz-feature.js definir <slug>`, and nobody invokes this skill in the normal case. Use it when the owner explicitly asks to rename, switch or clear the feature, or asks which one is active; the action itself is always `wizz-feature.js definir` (or `encerrar`), described below.
 
 - `session-rules.js` (SessionStart) resolves the feature from the git branch or the config and injects `FEATURE ATIVA: <slug>`. In a Wizz project with no feature it injects the reminder `NENHUMA FEATURE ATIVA: o primeiro pedido nomeado define uma`.
 - `wizz-router-enforce.js` (UserPromptSubmit) repeats the state on every non-trivial prompt: `Feature: <slug>` or `nenhuma ativa`.
 - The router, the maestro and the area agents then run the deterministic CLI `node _wizz/hooks/wizz-feature.js definir <slug>` BEFORE dispatching named work, and the handoff carries `feature:` (see the wizz module's `_shared/organizacao.md`).
-- `wizz-artifact-guard.js` (PostToolUse on Write) warns when an artifact lands outside the active feature's folder.
+- `wizz-artifact-guard.js` (PostToolUse on Write and Edit) warns when an artifact lands outside the active feature's folder.
 
-Invoke this skill only for the three explicit cases in "When this skill runs" below.
+Invoke this skill only for the explicit cases in "When this skill runs" below.
 
 ## Conventions
 
 - `{project-root}`-prefixed paths resolve from the project working directory.
 
-## Resolution order (never ask before exhausting it)
+## Resolution order (what `resolver` applies; never ask before exhausting it)
 
 1. **Git branch.** `feat/dashboard-financeiro` → `dashboard-financeiro`. Strip the type prefix (`feat/`, `feature/`, `fix/`, `bugfix/`, `hotfix/`, `chore/`, `refactor/`, `docs/`, `test/`, `perf/`, `ci/`, `build/`, `style/`), lowercase, kebab-case. Trunk branches (`main`, `master`, `develop`, `dev`, `staging`, `prod`, `production`, `release`) and release branches yield **no** feature, not a bad one.
 2. **`active_feature` in `{project-root}/_wizz/bmm/config.yaml`.** Used when the branch gives nothing.
 3. **The request itself.** When 1 and 2 are both empty and the request is named work (a feature, a batch, a screen, a page, a campaign, a bug with a scope: "vamos fazer o painel de assinaturas"). Derive the slug from the subject, 2 to 4 words, and run `node _wizz/hooks/wizz-feature.js definir <slug>` BEFORE dispatching; say so in **one line**. Do not ask. This step is mandatory for the router and the maestro, not a nice-to-have: skipping it is how a project spends its whole life with an empty `active_feature`.
 4. **Nothing.** Only for work that is not named (a question, a conversation, a one-line tweak with no artifact). Artifacts go to the roots and memory carries no feature tag.
 
-**Switch or keep.** With a feature active, a request about a different subject switches (`definir <new>`; the previous one stays open until closed) and a continuation keeps it. **Close** when the delivery closes (deploy or acceptance): `wizz-feature.js verificar` must pass, then `wizz-feature.js encerrar [--proxima <slug>]` marks the spec `no-ar`, clears or switches `active_feature`, and reminds you to record the Cérebro.
+**Switch or keep.** With a feature active, a request about a different subject switches (`definir <new>`; the previous one stays open until closed) and a continuation keeps it. **Close** when the delivery closes (deploy or acceptance): `wizz-feature.js verificar` must pass, then `wizz-feature.js encerrar --cerebro [--proxima <slug>]` marks the spec `no-ar`, clears or switches `active_feature`, and writes the Cérebro (state + one Sessions line; without a vault it prints the instruction instead).
 
 **Optional branch.** `feature_branches: auto` in `_wizz/bmm/config.yaml` makes `definir` (and the SessionStart hook) propose `git switch -c feat/<slug>` when you are on a trunk branch of a git repo. The default is `off`, for whoever works directly on `main`.
 
@@ -39,7 +39,7 @@ Invoke this skill only for the three explicit cases in "When this skill runs" be
 | `definir <slug or name>` | Normalizes, writes `active_feature`, creates both subfolders, prints one line. |
 | `artefato <tipo>` | Creates `<tipo>-<slug>.md` (spec, plano, auditoria, story, review, roteiro) in the right folder with valid frontmatter. |
 | `decidir "<texto>"` | Appends `D-NN` with the date to the feature's spec and to its `decisoes:` frontmatter. |
-| `status <status>` | `rascunho`, `aprovado`, `implementado` or `no-ar` in the spec. |
+| `status <status>` | Sets the spec's status: `rascunho`, `aprovado`, `implementado` or `no-ar` (it writes; to only read, use `resolver` or `listar`). |
 | `verificar` | Closing checklist; exit 1 while an item is pending. |
 | `encerrar` | Refuses with a pending item (unless `--forcar`); otherwise closes as above. |
 | `listar` | Features with a folder and the status of each spec. |
@@ -51,7 +51,7 @@ The branch wins over the config: it describes the work happening now, while the
 ## When this skill runs
 
 - **The user asks what is active** → answer from the resolution order and stop. Do not write anything.
-- **The user asks to set, switch or clear** → they already named it (or asked to clear); normalize, write, confirm in one line. Do not ask for a slug they just gave you.
+- **The user asks to rename, set, switch or clear** → this is the manual override. They already named it (or asked to clear): run `node _wizz/hooks/wizz-feature.js definir <slug>` (or clear, see Step 4), confirm in one line. Do not ask for a slug they just gave you. A rename keeps the old folders; `definir` creates the new ones.
 - **Genuine ambiguity** → two or more features are open and the request does not decide between them. This is the only case where you ask, and you ask once, offering the open features as options.
 
 ## Steps
@@ -68,7 +68,7 @@ Confirm with the user **only** in the ambiguity case. A slug that came from the
 
 ### Step 3: Write the config and create the subfolders
 
-Run `node _wizz/hooks/wizz-feature.js definir <slug>` from the project root. It sets `active_feature:` (adding the key if absent) and creates `{planning_artifacts}/{active_feature}/` and `{implementation_artifacts}/{active_feature}/`. Without the CLI (old install), edit the config and create the folders by hand.
+Run `node _wizz/hooks/wizz-feature.js definir <slug>` from the project root; this is the override itself. It sets `active_feature:` (adding the key if absent) and creates `{planning_artifacts}/{active_feature}/` and `{implementation_artifacts}/{active_feature}/`. Without the CLI (old install), edit the config and create the folders by hand.
 
 ### Step 4: Clearing
 

package/src/bmm-skills/4-implementation/wizz-create-story/SKILL.md

@@ -421,7 +421,7 @@ Activation is complete. If `activation_steps_prepend` or `activation_steps_appen
     1. Review the comprehensive story in {{story_file}}
     2. Run dev agents `dev-story` for optimized implementation
     3. Run `code-review` when complete (auto-marks done)
-    4. Optional: If Test Architect module installed, run `/wizz:tea:automate` after `dev-story` to generate guardrail tests
+    4. Optional: If Test Architect module installed, run the Test Architect `automate` workflow after `dev-story` to generate guardrail tests
 
     **The developer now has everything needed for flawless implementation!**
   </output>

package/src/bmm-skills/4-implementation/wizz-dev-story/SKILL.md

@@ -486,7 +486,7 @@ Activation is complete. If `activation_steps_prepend` or `activation_steps_appen
       - Verify all acceptance criteria are met
       - Ensure deployment readiness if applicable
       - Run `code-review` workflow for peer review
-      - Optional: If Test Architect module installed, run `/wizz:tea:automate` to expand guardrail tests
+      - Optional: If Test Architect module installed, run the Test Architect `automate` workflow to expand guardrail tests
     </action>
 
     <output>💡 **Tip:** For best results, run `code-review` using a **different** LLM than the one that implemented this story.</output>

package/src/bmm-skills/4-implementation/wizz-qa-generate-e2e-tests/SKILL.md

@@ -160,7 +160,7 @@ If the project needs:
 - Comprehensive coverage analysis
 - Advanced testing patterns and utilities
 
-> **Install Test Architect (TEA) module**: <https://bmad-code-org.github.io/bmad-method-test-architecture-enterprise/>
+> **Wizz Test Architect (TEA) module**: enable it in the Wizz installer (install, then select the module `tea`).
 
 ## Output
 

package/src/bmm-skills/4-implementation/wizz-qa-generate-e2e-tests/checklist.md

@@ -30,4 +30,4 @@ Run the tests using your project's test command.
 
 ---
 
-**Need more comprehensive testing?** Install [Test Architect (TEA)](https://bmad-code-org.github.io/bmad-method-test-architecture-enterprise/) for advanced workflows.
+**Need more comprehensive testing?** Enable the Wizz Test Architect (`tea`) module in the Wizz installer (install, then modules) for advanced workflows.

package/src/bmm-skills/4-implementation/wizz-quick-dev/SKILL.md

@@ -37,7 +37,7 @@ A specification should target a **single user-facing goal** within **900–1600
 
 You are the leaf: the maestro demotes here for pointed work (bug, tweak, single-goal feature). Re-check scope against the shared complexity signal (areas, steps, needs-planning?, artifact+memory?):
 
-**Dispatch rule:** IF 2+ areas → `wizz-maestro`, always. ELSE count the 3 remaining factors (multi-step, needs planning, produces a memorable artifact); 2+ factors → `wizz-maestro`. The area clause decides on its own, without summing with anything else.
+**Dispatch rule:** IF 2+ areas → `wizz-maestro`, always. OTHERWISE count the 3 remaining factors (multi-step, needs planning, produces a memorable artifact); 2+ factors → `wizz-maestro`. The area clause decides on its own, without combining with anything else.
 
 **Decision order — capabilities → required relations → areas → shortcuts.** Match the catalogue entries, inspect their `rel`, and include only capabilities needed for the requested deliverable and not already supplied in the context. Resolve their owning areas before applying ANY one-area shortcut. One artifact can require multiple areas; the word "copy" does not prove that only copy is needed. For full sales-page copy, if either the offer or the conversion structure is missing from the supplied context, include the missing capability: `wizz-offer-forge` for the offer and/or `wizz-page-cro` for conversion structure (growth), alongside `wizz-copywriting` (copy); route to maestro. Do not assume those inputs are ready merely because the user did not mention them. If both are already approved and the request is limited to text, keep copy-only work in copy. An isolated headline or CTA does not require redesigning the whole page. Optional neighbours and separate deliverables do not add areas; `pairs_with` alone never escalates.
 

package/src/bmm-skills/4-implementation/wizz-sprint-status/SKILL.md

@@ -93,7 +93,7 @@ Activation is complete. If `activation_steps_prepend` or `activation_steps_appen
   <action>Try {sprint_status_file}</action>
   <check if="file not found">
     <output>sprint-status.yaml not found.
-Run `/wizz:bmm:workflows:sprint-planning` to generate it, then rerun sprint-status.</output>
+Run `/wizz-sprint-planning` to generate it, then rerun sprint-status.</output>
     <action>Exit workflow</action>
   </check>
   <action>Continue to Step 2</action>
@@ -149,9 +149,9 @@ Enter corrections (e.g., "1=in-progress, 2=backlog") or "skip" to continue witho
 
 <action>Detect risks:</action>
 
-- IF any story has status "review": suggest `/wizz:bmm:workflows:code-review`
+- IF any story has status "review": suggest `/wizz-code-review`
 - IF any story has status "in-progress" AND no stories have status "ready-for-dev": recommend staying focused on active story
-- IF all epics have status "backlog" AND no stories have status "ready-for-dev": prompt `/wizz:bmm:workflows:create-story`
+- IF all epics have status "backlog" AND no stories have status "ready-for-dev": prompt `/wizz-create-story`
 - IF `last_updated` timestamp is more than 7 days old (or `last_updated` is missing, fall back to `generated`): warn "sprint-status.yaml may be stale"
 - IF any story key doesn't match an epic pattern (e.g., story "5-1-..." but no "epic-5"): warn "orphaned story detected"
 - IF any epic has status in-progress but has no associated stories: warn "in-progress epic has no stories"
@@ -181,7 +181,7 @@ Enter corrections (e.g., "1=in-progress, 2=backlog") or "skip" to continue witho
 
 **Epics:** backlog {{epic_backlog}}, in-progress {{epic_in_progress}}, done {{epic_done}}
 
-**Next Recommendation:** /wizz:bmm:workflows:{{next_workflow_id}} ({{next_story_id}})
+**Next Recommendation:** /wizz-{{next_workflow_id}} ({{next_story_id}})
 
 {{#if open_action_items}}
 **Open Action Items:**
@@ -211,7 +211,7 @@ Enter corrections (e.g., "1=in-progress, 2=backlog") or "skip" to continue witho
 Choice:</ask>
 
   <check if="choice == 1">
-    <output>Run `/wizz:bmm:workflows:{{next_workflow_id}}`.
+    <output>Run `/wizz-{{next_workflow_id}}`.
 If the command targets a story, set `story_key={{next_story_id}}` when prompted.</output>
   </check>
 

package/src/bmm-skills/module-help.csv

@@ -1,7 +1,7 @@
 module,skill,display-name,menu-code,description,action,args,phase,preceded-by,followed-by,required,output-location,outputs
 Wizz Method,_meta,,,,,,,,,false,https://docs.wizz-method.org/llms.txt,
 Wizz Method,wizz-document-project,Document Project,DP,Analyze an existing project to produce useful documentation.,,,anytime,,,false,project-knowledge,*
-Wizz Method,wizz-set-feature,Set Feature,SF,Set or switch the active feature context so planning and implementation artifacts are organized into a named subfolder.,,,anytime,,,false,,
+Wizz Method,wizz-set-feature,Set Feature,SF,Manual override: switch, rename or clear the active feature on purpose (it is normally set automatically by the first named request).,,,anytime,,,false,,
 Wizz Method,wizz-generate-project-context,Generate Project Context,GPC,Scan existing codebase to generate a lean LLM-optimized project-context.md. Essential for brownfield projects.,,,anytime,,,false,output_folder,project context
 Wizz Method,wizz-quick-dev,Quick Dev,QQ,Unified intent-in code-out workflow: clarify plan implement review and present.,,,anytime,,,false,implementation_artifacts,spec and project implementation
 Wizz Method,wizz-correct-course,Correct Course,CC,Navigate significant changes. May recommend start over update PRD redo architecture sprint planning or correct epics and stories.,,,anytime,,,false,planning_artifacts,change proposal

package/src/bmm-skills/module.yaml

@@ -40,7 +40,7 @@ project_knowledge: # Artifacts from research, document-project output, other lon
   default: "docs"
   result: "{project-root}/{value}"
 
-active_feature: # Current feature context. Used as a subfolder inside planning and implementation artifacts. Set or switch it with the wizz-set-feature skill.
+active_feature: # Current feature context. Used as a subfolder inside planning and implementation artifacts. Set automatically by the first named request (wizz-feature.js definir); the wizz-set-feature skill is the manual override to switch or rename it.
   prompt: "Active feature slug (e.g. admin-panel, auth-refactor). Used as a subfolder inside planning and implementation artifacts. Leave blank for none."
   default: ""
   result: "{value}"

package/src/core-skills/_shared/handoff-protocol.md

@@ -22,9 +22,9 @@ and pass along only the skill's entrypoint and the references actually needed
 - origin: who is delegating (e.g. wizz-router, wizz-maestro). Anti-loop
   rule: never invoke whoever is already in the origin chain. Forbidden
   example: router delegates to maestro, maestro hands it back to router.
-- cerebro already consulted: a summary of up to 3 lines of what `/cerebro ver` already
+- cerebro already consulted: a summary of up to 3 lines of what `/wizz-cerebro ver` already
   brought back (project state, recent decisions relevant to the area). If this
-  field is filled in, whoever receives the handoff does not run `/cerebro ver`
+  field is filled in, whoever receives the handoff does not run `/wizz-cerebro ver`
   again, and uses the summary received instead.
 - decisions already made in the chain: a short list of what was already decided before
   this handoff (e.g. approved palette, defined scope).

package/src/modules/lowticket/skills/wizz-lowticket-funil/SKILL.md

@@ -17,7 +17,7 @@ Every offer in the ladder exists because it answers that question for the step b
 
 ## Source of truth
 
-Read the Cérebro state first (via the `cerebro` skill). Then, if `wizz-lowticket-metodologia` is installed, read `knowledge/INDEX.md` + `knowledge/guardrails.md` and the shard `07-funil-upsell.md`, especially §7.4 (the conversion and ticket cascade) and §7.5-7.9 (pain per step, tone per page, copy rules, the technical block for post-checkout pages and the pre-build checklist). Its sibling shard `07a-copy-humanizacao.md` carries the humanization checklist used before delivering any page. Where a generic skill contradicts that shard, the shard wins and you say so.
+Read the Cérebro state first (via the `wizz-cerebro` skill). Then, if `wizz-lowticket-metodologia` is installed, read `knowledge/INDEX.md` + `knowledge/guardrails.md` and the shard `07-funil-upsell.md`, especially §7.4 (the conversion and ticket cascade) and §7.5-7.9 (pain per step, tone per page, copy rules, the technical block for post-checkout pages and the pre-build checklist). Its sibling shard `07a-copy-humanizacao.md` carries the humanization checklist used before delivering any page. Where a generic skill contradicts that shard, the shard wins and you say so.
 
 This skill has **no memory of its own**. What gets decided goes to the Cérebro; the artifact goes to a file.
 

package/src/modules/lowticket/skills/wizz-lowticket-guia/SKILL.md

@@ -11,7 +11,7 @@ The other low ticket skills are sharp and assume the user knows which one to cal
 
 ## Step 0: What is already known
 
-1. Read the project's Cérebro state (via the `cerebro` skill). If it already says which offer is live and at which step, skip the questions.
+1. Read the project's Cérebro state (via the `wizz-cerebro` skill). If it already says which offer is live and at which step, skip the questions.
 2. Read `wizz-lowticket-metodologia/knowledge/INDEX.md` and `guardrails.md` (the always-load of the base). Read `01-principios.md` too: its gates decide which steps cannot be skipped.
 
 ## Step 1: Place the user, in one message

package/src/modules/lowticket/skills/wizz-lowticket-metodologia/SKILL.md

@@ -31,7 +31,7 @@ The one thing that outranks a shard is `knowledge/guardrails.md`. Eight tactics
 
 ### Step 0: Read the state, then the index
 
-Read the project's Cérebro state block first (via the `cerebro` skill: current project state plus at most 3 decisions on the topic). This skill has **no memory of its own** and never writes one. What is decided lives in the Cérebro; what is known lives in the shards.
+Read the project's Cérebro state block first (via the `wizz-cerebro` skill: current project state plus at most 3 decisions on the topic). This skill has **no memory of its own** and never writes one. What is decided lives in the Cérebro; what is known lives in the shards.
 
 Then read `knowledge/INDEX.md` and `knowledge/guardrails.md`. That is the whole default load, around 800 tokens.
 

package/src/modules/lowticket/skills/wizz-lowticket-minerador/SKILL.md

@@ -15,7 +15,7 @@ Two kinds of person ask this. An operator who already runs traffic, reads metric
 
 ## Source of truth
 
-Read the Cérebro state first (via the `cerebro` skill). If `wizz-lowticket-metodologia` is installed, read `knowledge/INDEX.md` + `knowledge/guardrails.md`, then:
+Read the Cérebro state first (via the `wizz-cerebro` skill). If `wizz-lowticket-metodologia` is installed, read `knowledge/INDEX.md` + `knowledge/guardrails.md`, then:
 
 - **`12-mineracao-ofertas.md`**: the price trick, the Ad Library filter checklist and keyword taxonomy, the 0-10 rubric with a cut at 6, the three safety rules
 - **`12a-mineracao-veredito.md`**: §12.5, the scoring ruler and what disqualifies

package/src/modules/lowticket/skills/wizz-lowticket-pagina/SKILL.md

@@ -30,7 +30,7 @@ Speed fixes the leak between the click and the page. It does not fix a bad offer
 
 ## Source of truth
 
-Read the Cérebro state first (via the `cerebro` skill). If `wizz-lowticket-metodologia` is installed, read `knowledge/INDEX.md` + `knowledge/guardrails.md` and shard `06-pagina-vendas.md`, especially §6.3-6.4. Page structure and copy blocks for a pure low-ticket page live in `12c-anatomia-low-ticket.md` (the 11-block anatomy, not `12b` anymore); VSL player behavior (autoplay, progress bar, weight) is `06b-player-vsl.md`; conversion-side reasoning is `wizz-page-cro`. Where a generic skill contradicts the shard, the shard wins and you say so.
+Read the Cérebro state first (via the `wizz-cerebro` skill). If `wizz-lowticket-metodologia` is installed, read `knowledge/INDEX.md` + `knowledge/guardrails.md` and shard `06-pagina-vendas.md`, especially §6.3-6.4. Page structure and copy blocks for a pure low-ticket page live in `12c-anatomia-low-ticket.md` (the 11-block anatomy, not `12b` anymore); VSL player behavior (autoplay, progress bar, weight) is `06b-player-vsl.md`; conversion-side reasoning is `wizz-page-cro`. Where a generic skill contradicts the shard, the shard wins and you say so.
 
 **Open conflict, do not resolve it alone.** §6.3-6.4 (this skill's rule) fires the pixel direct, first in `<head>`, no tag manager. `17-rastreamento.md` installs that same pixel *inside* GTM, as part of the full GA4 + Meta + server-container stack. This is ponto 38 of `pontos-em-aberto.md` in `wizz-lowticket-metodologia`, and it is unresolved. If the page already runs tracking through GTM, do not rip the pixel out of the container to chase the speed target: ask which rule wins before touching it.
 

package/src/modules/lowticket/skills/wizz-lowticket-trafego/SKILL.md

@@ -18,7 +18,7 @@ The numbers live in `wizz-lowticket-metodologia`, not here. On activation, read
 
 Where a generic paid-media skill (`wizz-paid-ads`, `wizz-analytics-tracking`) contradicts those shards, the shard wins and you say so. If `wizz-lowticket-metodologia` is not installed, the rules in `references/reguas.md` here are the fallback, and you say that too.
 
-Read the Cérebro state before answering (via the `cerebro` skill): the account's breakeven, ticket and current bid cap are state, not knowledge. This skill has **no memory of its own** and writes none.
+Read the Cérebro state before answering (via the `wizz-cerebro` skill): the account's breakeven, ticket and current bid cap are state, not knowledge. This skill has **no memory of its own** and writes none.
 
 ## If the user is new to this