wizz-method 1.19.0 → 2.0.0

package/src/skills-lib/{motion-3d-director → wizz-motion-3d-director}/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: motion-3d-director
-description: Direction system for premium motion, 3D, image-to-video, WebGL, shader, scroll animation, cinematic hero, React Three Fiber, Spline, Unicorn Studio. Use when a site needs 3D hero, video hero, image-to-video, WebGL, particles, shaders, advanced scroll, Signature 3D Experience, or when premium-landing-ui-researcher classifies the project as 3D High-End or Signature 3D. The skill decides between real-time 3D, image-to-video, hybrid motion, or premium 2D motion BEFORE implementation, then outputs prompts and a handoff for implementation-planner.
+name: wizz-motion-3d-director
+description: Direction system for premium motion, 3D, image-to-video, WebGL, shader, scroll animation, cinematic hero, React Three Fiber, Spline, Unicorn Studio. Use when a site needs 3D hero, video hero, image-to-video, WebGL, particles, shaders, advanced scroll, Signature 3D Experience, or when wizz-premium-landing-ui-researcher classifies the project as 3D High-End or Signature 3D. The skill decides between real-time 3D, image-to-video, hybrid motion, or premium 2D motion BEFORE implementation, then outputs prompts and a handoff for implementation-planner.
 ---
 
 # Motion / 3D Director
@@ -38,7 +38,7 @@ Acionar quando o usuário disser ou o projeto indicar:
 - "quero transformar imagem em vídeo" / "quero usar minha logo como hero";
 - "não tenho imagem, mas quero algo 3D".
 
-Também usar automaticamente quando `premium-landing-ui-researcher` classificar o projeto como:
+Também usar automaticamente quando `wizz-premium-landing-ui-researcher` classificar o projeto como:
 
 - **3D High-End Site**;
 - **3D High-End Site — modo Signature 3D Experience**.
@@ -47,9 +47,9 @@ Também usar automaticamente quando `premium-landing-ui-researcher` classificar
 
 Pular esta skill quando:
 
-- O nível do projeto for **Basic Site** ou **Intermediate Site** — não há decisão de motion path a fazer; `premium-landing-ui-researcher` resolve sozinho com motion 2D leve.
+- O nível do projeto for **Basic Site** ou **Intermediate Site** — não há decisão de motion path a fazer; `wizz-premium-landing-ui-researcher` resolve sozinho com motion 2D leve.
 - O nível for **Advanced Site** e o usuário não pediu nenhum elemento 3D/vídeo — Advanced opera bem com motion 2D premium e a decisão de path é trivial.
-- O usuário ainda não tem brief (rodar `decision-maker` primeiro — sem feeling, hero object e three-second memory, qualquer direção de motion vira chute).
+- O usuário ainda não tem brief (rodar `wizz-decision-maker` primeiro — sem feeling, hero object e three-second memory, qualquer direção de motion vira chute).
 
 ---
 
@@ -57,7 +57,7 @@ Pular esta skill quando:
 
 Antes de recomendar qualquer implementação, decidir entre os quatro paths considerando:
 
-- objetivo do site; público; nível visual (do `premium-landing-ui-researcher`); hero object (do brief); feeling (do brief); three-second memory (do brief);
+- objetivo do site; público; nível visual (do `wizz-premium-landing-ui-researcher`); hero object (do brief); feeling (do brief); three-second memory (do brief);
 - se existe logo; se existe imagem; se existe mockup; se existe produto;
 - se precisa de interação real; performance mobile; tempo de implementação; impacto desejado; custo de manutenção.
 
@@ -75,7 +75,7 @@ Objetivo:
 
 Deve parecer: autoral; raro; cinematográfico; técnico; premium; sofisticado; memorável; impossível de confundir com template.
 
-**Motion Budget e Signature Motion Checklist (Hero / Scroll / Background / Components) vivem em `premium-landing-ui-researcher`** — seção `## Motion & Interaction Complexity Ladder`. Não duplicar aqui. Consultar lá ao montar o plano do site e usar como entrada para a decisão de path desta skill.
+**Motion Budget e Signature Motion Checklist (Hero / Scroll / Background / Components) vivem em `wizz-premium-landing-ui-researcher`** — seção `## Motion & Interaction Complexity Ladder`. Não duplicar aqui. Consultar lá ao montar o plano do site e usar como entrada para a decisão de path desta skill.
 
 O que **esta skill** decide para Signature 3D:
 
@@ -83,13 +83,13 @@ O que **esta skill** decide para Signature 3D:
 - qual o asset base (logo? objeto signature abstrato? cena atmosférica?);
 - prompts de imagem e vídeo — ver `references/image-to-video-workflow.md`;
 - performance plan completo;
-- handoff para `implementation-planner`.
+- handoff para `wizz-implementation-planner`.
 
 ---
 
 ## Performance Requirements + Handoff
 
-Todo plano 3D, vídeo ou motion avançado precisa de fallback mobile, poster image, `prefers-reduced-motion`, lazy load e respeitar Core Web Vitals. Ao final, sempre entregar o bloco de handoff para `implementation-planner` (motion path, assets, arquivos esperados, stack, notas). Lista completa de requisitos + targets (LCP/CLS/INP) + template exato do handoff em `references/performance-and-handoff.md`.
+Todo plano 3D, vídeo ou motion avançado precisa de fallback mobile, poster image, `prefers-reduced-motion`, lazy load e respeitar Core Web Vitals. Ao final, sempre entregar o bloco de handoff para `wizz-implementation-planner` (motion path, assets, arquivos esperados, stack, notas). Lista completa de requisitos + targets (LCP/CLS/INP) + template exato do handoff em `references/performance-and-handoff.md`.
 
 ---
 
@@ -110,7 +110,7 @@ Quando esta skill for acionada, entregar:
 11. **Fallback mobile**.
 12. **Performance notes** (Core Web Vitals, lazy load, reduced motion).
 13. **O que evitar** (web3 template, neon, sci-fi barato, 3D gratuito).
-14. **Handoff para `implementation-planner`** (template em `references/performance-and-handoff.md`).
+14. **Handoff para `wizz-implementation-planner`** (template em `references/performance-and-handoff.md`).
 
 ---
 

package/src/skills-lib/{motion-3d-director → wizz-motion-3d-director}/references/performance-and-handoff.md

@@ -1,6 +1,6 @@
 # Performance requirements + handoff template
 
-Carregar ao fechar o output desta skill: a lista completa de requisitos de performance (fallback mobile, lazy load, Core Web Vitals) e o template exato do bloco de handoff para implementation-planner.
+Carregar ao fechar o output desta skill: a lista completa de requisitos de performance (fallback mobile, lazy load, Core Web Vitals) e o template exato do bloco de handoff para wizz-implementation-planner.
 
 ## Performance Requirements
 
@@ -10,12 +10,12 @@ Todo plano 3D, vídeo ou motion avançado deve incluir:
 
 **Targets sugeridos:** LCP < 2.5s desktop; LCP < 3.5s mobile 4G; CLS < 0.1; INP < 200ms; bundle inicial controlado; 3D/vídeo fora do critical path quando possível.
 
-## Handoff para implementation-planner
+## Handoff para wizz-implementation-planner
 
 Ao final, sempre entregar um bloco assim:
 
 ```
-## Handoff para implementation-planner
+## Handoff para wizz-implementation-planner
 
 Motion path escolhido:
 [3D real / image-to-video / hybrid motion / motion 2D premium]

package/src/skills-lib/wizz-offer-forge/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wizz-offer-forge
-description: Forja ofertas irresistíveis de resposta direta e infoprodutos integrando mecanismo único, tese da oferta, empilhamento de valor, garantia reversa, ancoragem de preço e matriz de criativos para tráfego pago. Use quando o usuário quiser criar uma nova oferta do zero, reestruturar oferta existente que não converte, empilhar bônus de alta percepção, definir garantia agressiva ou traduzir pesquisa de público (Piva/VoC) em uma máquina de vendas. NÃO use para pesquisa bruta de público (use pesquisa-de-publico-do-piva) nem redação final de copy de página (use copywriting).
+description: Forja ofertas irresistíveis de resposta direta e infoprodutos integrando mecanismo único, tese da oferta, empilhamento de valor, garantia reversa, ancoragem de preço e matriz de criativos para tráfego pago. Use quando o usuário quiser criar uma nova oferta do zero, reestruturar oferta existente que não converte, empilhar bônus de alta percepção, definir garantia agressiva ou traduzir pesquisa de público (Piva/VoC) em uma máquina de vendas. NÃO use para pesquisa bruta de público (use pesquisa-de-publico-do-piva) nem redação final de copy de página (use wizz-copywriting).
 ---
 
 # Wizz Offer Forge
@@ -75,7 +75,7 @@ Consulte `references/garantia-reversa.md`:
 ### Passo 5 — Ponte de Tráfego & Ângulos de Anúncios
 
 Consulte `references/ponte-trafego.md`:
-- Mapeie 3 a 5 ganchos diretos para alimentar `ad-creative` e `paid-ads` no `traffic-masters` (Pedro Sobral / Molly Pittman / Ad Midas):
+- Mapeie 3 a 5 ganchos diretos para alimentar `wizz-ad-creative` e `wizz-paid-ads` no `traffic-masters` (Pedro Sobral / Molly Pittman / Ad Midas):
   1. *Gancho da Quebra de Padrão / Vilão Revelado*
   2. *Gancho do Erro Comum / Teste Rápido*
   3. *Gancho da Demonstração do Mecanismo*
@@ -93,7 +93,7 @@ Derive da própria oferta, sem inventar número:
 - **Metas por transição do funil**, calibradas para este ticket, com a fonte da régua declarada.
 - **A hipótese principal** em uma frase, e o **número que reprova a oferta**.
 
-Se a skill `tracking-audit` estiver instalada, delegue a implantação e a conferência para ela: aqui se declara o que precisa ser verdade, lá se prova que é.
+Se a skill `wizz-tracking-audit` estiver instalada, delegue a implantação e a conferência para ela: aqui se declara o que precisa ser verdade, lá se prova que é.
 
 ### Passo 7 — Compilação e Entrega
 

package/src/skills-lib/wizz-offer-forge/references/plano-de-medicao.md

@@ -36,7 +36,7 @@ story      utm_source=instagram&utm_medium=story&utm_campaign=<oferta>
 e-mail     utm_source=email&utm_medium=<sequência>&utm_campaign=<oferta>
 ```
 
-Rota sem UTM cai no balde do orgânico e some da análise. Se a skill `tracking-audit` estiver instalada, ela é a dona da implantação e da conferência disso.
+Rota sem UTM cai no balde do orgânico e some da análise. Se a skill `wizz-tracking-audit` estiver instalada, ela é a dona da implantação e da conferência disso.
 
 ## 3. Metas por transição
 
@@ -70,5 +70,5 @@ O volume mínimo importa tanto quanto o número. "Não converteu" com 40 visitas
 
 Este bloco **declara** o que precisa ser verdade. Ele não instala nada e não confere nada.
 
-- Com `tracking-audit` instalada: o passo seguinte é rodar o modo implantação dela usando este bloco como entrada.
+- Com `wizz-tracking-audit` instalada: o passo seguinte é rodar o modo implantação dela usando este bloco como entrada.
 - Sem ela: entregue o bloco como checklist manual e diga que a conferência não foi feita.

package/src/skills-lib/{onboarding-cro → wizz-onboarding-cro}/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: onboarding-cro
-description: When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," "new user experience," "users aren't activating," "nobody completes setup," "low activation rate," "users sign up but don't use the product," "time to value," or "first session experience." Use this whenever users are signing up but not sticking around. For signup/registration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.
+name: wizz-onboarding-cro
+description: When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," "new user experience," "users aren't activating," "nobody completes setup," "low activation rate," "users sign up but don't use the product," "time to value," or "first session experience." Use this whenever users are signing up but not sticking around. For signup/registration optimization, see wizz-signup-flow-cro. For ongoing email sequences, see wizz-email-sequence.
 metadata:
   version: 1.1.0
 ---
@@ -214,7 +214,7 @@ When recommending experiments, consider tests for:
 
 ## Related Skills
 
-- **signup-flow-cro**: For optimizing the signup before onboarding
-- **email-sequence**: For onboarding email series
-- **paywall-upgrade-cro**: For converting to paid during/after onboarding
-- **ab-test-setup**: For testing onboarding changes
+- **wizz-signup-flow-cro**: For optimizing the signup before onboarding
+- **wizz-email-sequence**: For onboarding email series
+- **wizz-paywall-upgrade-cro**: For converting to paid during/after onboarding
+- **wizz-ab-test-setup**: For testing onboarding changes

package/src/skills-lib/{onboarding-cro → wizz-onboarding-cro}/evals/evals.json

@@ -1,5 +1,5 @@
 {
-  "skill_name": "onboarding-cro",
+  "skill_name": "wizz-onboarding-cro",
   "evals": [
     {
       "id": 1,

package/src/skills-lib/{page-cro → wizz-page-cro}/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: page-cro
-description: When the user wants to optimize, improve, or increase conversions on any marketing page — including homepage, landing pages, pricing pages, feature pages, or blog posts. Also use when the user says "CRO," "conversion rate optimization," "this page isn't converting," "improve conversions," "why isn't this page working," "my landing page sucks," "nobody's converting," "low conversion rate," "bounce rate is too high," "people leave without signing up," or "this page needs work." Use this even if the user just shares a URL and asks for feedback — they probably want conversion help. For signup/registration flows, see signup-flow-cro. For post-signup activation, see onboarding-cro. For forms outside of signup, see form-cro. For popups/modals, see popup-cro.
+name: wizz-page-cro
+description: When the user wants to optimize, improve, or increase conversions on any marketing page — including homepage, landing pages, pricing pages, feature pages, or blog posts. Also use when the user says "CRO," "conversion rate optimization," "this page isn't converting," "improve conversions," "why isn't this page working," "my landing page sucks," "nobody's converting," "low conversion rate," "bounce rate is too high," "people leave without signing up," or "this page needs work." Use this even if the user just shares a URL and asks for feedback — they probably want conversion help. For signup/registration flows, see wizz-signup-flow-cro. For post-signup activation, see wizz-onboarding-cro. For forms outside of signup, see wizz-form-cro. For popups/modals, see wizz-popup-cro.
 metadata:
   version: 1.1.0
 ---
@@ -175,8 +175,8 @@ When recommending experiments, consider tests for:
 
 ## Related Skills
 
-- **signup-flow-cro**: If the issue is in the signup process itself
-- **form-cro**: If forms on the page need optimization
-- **popup-cro**: If considering popups as part of the strategy
-- **copywriting**: If the page needs a complete copy rewrite
-- **ab-test-setup**: To properly test recommended changes
+- **wizz-signup-flow-cro**: If the issue is in the signup process itself
+- **wizz-form-cro**: If forms on the page need optimization
+- **wizz-popup-cro**: If considering popups as part of the strategy
+- **wizz-copywriting**: If the page needs a complete copy rewrite
+- **wizz-ab-test-setup**: To properly test recommended changes

package/src/skills-lib/{page-cro → wizz-page-cro}/evals/evals.json

@@ -1,5 +1,5 @@
 {
-  "skill_name": "page-cro",
+  "skill_name": "wizz-page-cro",
   "evals": [
     {
       "id": 1,

package/src/skills-lib/{paid-ads → wizz-paid-ads}/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: paid-ads
-description: "When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' 'audience targeting,' 'Google Ads,' 'Facebook ads,' 'LinkedIn ads,' 'ad budget,' 'cost per click,' 'ad spend,' or 'should I run ads.' Use this for campaign strategy, audience targeting, bidding, and optimization. For bulk ad creative generation and iteration, see ad-creative. For landing page optimization, see page-cro."
+name: wizz-paid-ads
+description: "When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' 'audience targeting,' 'Google Ads,' 'Facebook ads,' 'LinkedIn ads,' 'ad budget,' 'cost per click,' 'ad spend,' or 'should I run ads.' Use this for campaign strategy, audience targeting, bidding, and optimization. For bulk ad creative generation and iteration, see wizz-ad-creative. For landing page optimization, see wizz-page-cro."
 metadata:
   version: 1.1.0
 ---
@@ -308,8 +308,8 @@ For tracking, see also: [ga4.md](../../tools/integrations/ga4.md), [segment.md](
 
 ## Related Skills
 
-- **ad-creative**: For generating and iterating ad headlines, descriptions, and creative at scale
-- **copywriting**: For landing page copy that converts ad traffic
-- **analytics-tracking**: For proper conversion tracking setup
-- **ab-test-setup**: For landing page testing to improve ROAS
-- **page-cro**: For optimizing post-click conversion rates
+- **wizz-ad-creative**: For generating and iterating ad headlines, descriptions, and creative at scale
+- **wizz-copywriting**: For landing page copy that converts ad traffic
+- **wizz-analytics-tracking**: For proper conversion tracking setup
+- **wizz-ab-test-setup**: For landing page testing to improve ROAS
+- **wizz-page-cro**: For optimizing post-click conversion rates

package/src/skills-lib/{paid-ads → wizz-paid-ads}/evals/evals.json

@@ -1,5 +1,5 @@
 {
-  "skill_name": "paid-ads",
+  "skill_name": "wizz-paid-ads",
   "evals": [
     {
       "id": 1,

package/src/skills-lib/{paywall-upgrade-cro → wizz-paywall-upgrade-cro}/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: paywall-upgrade-cro
-description: When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see page-cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing-strategy.
+name: wizz-paywall-upgrade-cro
+description: When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see wizz-page-cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see wizz-pricing-strategy.
 metadata:
   version: 1.1.0
 ---
@@ -221,7 +221,7 @@ What you've accomplished:
 
 ## Related Skills
 
-- **churn-prevention**: For cancel flows, save offers, and reducing churn post-upgrade
-- **page-cro**: For public pricing page optimization
-- **onboarding-cro**: For driving to aha moment before upgrade
-- **ab-test-setup**: For testing paywall variations
+- **wizz-churn-prevention**: For cancel flows, save offers, and reducing churn post-upgrade
+- **wizz-page-cro**: For public pricing page optimization
+- **wizz-onboarding-cro**: For driving to aha moment before upgrade
+- **wizz-ab-test-setup**: For testing paywall variations

package/src/skills-lib/{paywall-upgrade-cro → wizz-paywall-upgrade-cro}/evals/evals.json

@@ -1,5 +1,5 @@
 {
-  "skill_name": "paywall-upgrade-cro",
+  "skill_name": "wizz-paywall-upgrade-cro",
   "evals": [
     {
       "id": 1,

package/src/skills-lib/{popup-cro → wizz-popup-cro}/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: popup-cro
-description: When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," "overlay," "collect emails with a popup," "exit popup," "scroll trigger," "sticky bar," or "notification bar." Use this for any overlay or interrupt-style conversion element. For forms outside of popups, see form-cro. For general page conversion optimization, see page-cro.
+name: wizz-popup-cro
+description: When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," "overlay," "collect emails with a popup," "exit popup," "scroll trigger," "sticky bar," or "notification bar." Use this for any overlay or interrupt-style conversion element. For forms outside of popups, see wizz-form-cro. For general page conversion optimization, see wizz-page-cro.
 metadata:
   version: 1.1.0
 ---
@@ -44,7 +44,7 @@ Before providing recommendations, understand:
 
 ## Related Skills
 
-- **form-cro**: For optimizing the form inside the popup
-- **page-cro**: For the page context around popups
-- **email-sequence**: For what happens after popup conversion
-- **ab-test-setup**: For testing popup variations
+- **wizz-form-cro**: For optimizing the form inside the popup
+- **wizz-page-cro**: For the page context around popups
+- **wizz-email-sequence**: For what happens after popup conversion
+- **wizz-ab-test-setup**: For testing popup variations

package/src/skills-lib/{popup-cro → wizz-popup-cro}/evals/evals.json

@@ -1,5 +1,5 @@
 {
-  "skill_name": "popup-cro",
+  "skill_name": "wizz-popup-cro",
   "evals": [
     {
       "id": 1,

package/src/skills-lib/{premium-landing-ui-researcher → wizz-premium-landing-ui-researcher}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: premium-landing-ui-researcher
+name: wizz-premium-landing-ui-researcher
 description: Pesquisar animações, componentes, referências visuais e padrões de conversão para criar landing pages premium em React, Next.js, Tailwind, shadcn/ui, Framer Motion, Three.js e React Three Fiber. Use quando o pedido envolver analisar projeto existente; classificar nível de complexidade do site (básico a 3D high-end/Signature); escolher componentes/animações; melhorar UI genérica; criar landing page completa, transformar oferta em página estratégica, dashboard SaaS, site de autoridade/portfolio (agência, estúdio, consultoria, marca pessoal, lead passivo), case studies/selected work editoriais, ou experiência 3D cinematográfica para marcas premium; buscar referências em fontes premium (React Bits, Cult UI, Watermelon UI, Skiper UI, Componentry, outras em references/component-sources.md); ou escolher motion engine (GSAP, anime.js, Framer Motion, Three.js/R3F) para scroll storytelling.
 ---
 
@@ -32,9 +32,9 @@ Classificar o projeto em um dos 5 níveis (regras, motion permitido/proibido e b
 3. Definir direção visual e stack.
 4. Decidir modos extras: dashboard SaaS e/ou Portfolio / Authority Mode.
 5. Checkpoints de fontes: inventário interno, Source-First Protocol completo e escolha das fontes dentro do escopo autorizado (Gate 1). Nunca pular silenciosamente.
-6. Se nível 4 ou 5: handoff pro `motion-3d-director` antes de implementar.
+6. Se nível 4 ou 5: handoff pro `wizz-motion-3d-director` antes de implementar.
 7. Escrever copy completa e estrutura da página.
-8. Plano de implementação (handoff pro `implementation-planner` quando aplicável).
+8. Plano de implementação (handoff pro `wizz-implementation-planner` quando aplicável).
 9. Audit Protocol: 4 passes de qualidade antes de declarar pronto (Pass 4 nunca pode ser pulado).
 10. Entregar no formato de resposta final e rodar o self-check.
 
@@ -44,7 +44,7 @@ Classificar o projeto em um dos 5 níveis (regras, motion permitido/proibido e b
 |---|---|
 | Papel completo da skill, regra de autonomia, Project Intelligence Mode | [core-goal](references/core-goal.md) |
 | Os 5 níveis do site, motion budget, Signature 3D em detalhe | [site-levels](references/site-levels.md) |
-| Handoffs pro motion-3d-director e implementation-planner, regra final do ladder | [handoffs](references/handoffs.md) |
+| Handoffs pro wizz-motion-3d-director e wizz-implementation-planner, regra final do ladder | [handoffs](references/handoffs.md) |
 | SaaS Dashboard Mode e Portfolio / Authority Site Mode | [dashboard-and-portfolio-modes](references/dashboard-and-portfolio-modes.md) |
 | Processo obrigatório de 12 passos e checkpoint de honestidade | [mandatory-process](references/mandatory-process.md) |
 | Protocolo em 5 fases (inventário, busca pública, cache, evidências, adaptação) | [source-first-protocol](references/source-first-protocol.md) |

package/src/skills-lib/{premium-landing-ui-researcher → wizz-premium-landing-ui-researcher}/references/handoffs.md

@@ -1,6 +1,6 @@
-## Handoff para motion-3d-director
+## Handoff para wizz-motion-3d-director
 
-Quando o nível for **3D High-End** ou **Signature 3D Experience**, a landing strategist (esta skill) deve enviar para o `motion-3d-director`:
+Quando o nível for **3D High-End** ou **Signature 3D Experience**, a landing strategist (esta skill) deve enviar para o `wizz-motion-3d-director`:
 
 - brief visual;
 - feeling;
@@ -20,7 +20,7 @@ Quando o nível for **3D High-End** ou **Signature 3D Experience**, a landing st
 - restrições de performance;
 - caminho esperado (3D real, image-to-video, hybrid ou motion 2D).
 
-O `motion-3d-director` deve retornar:
+O `wizz-motion-3d-director` deve retornar:
 
 - diagnóstico de motion;
 - caminho recomendado;
@@ -32,24 +32,24 @@ O `motion-3d-director` deve retornar:
 - performance notes;
 - o que evitar.
 
-Os termos `feeling`, `hero object`, `three-second memory`, `color logic`, `typography logic` e `spatial logic` vêm do brief produzido pela skill `decision-maker` (seis decisões + três lógicas). Se o usuário ainda não tem brief, sugerir rodar `decision-maker` primeiro: handoffs para 3D sem brief produzem genérico.
+Os termos `feeling`, `hero object`, `three-second memory`, `color logic`, `typography logic` e `spatial logic` vêm do brief produzido pela skill `wizz-decision-maker` (seis decisões + três lógicas). Se o usuário ainda não tem brief, sugerir rodar `wizz-decision-maker` primeiro: handoffs para 3D sem brief produzem genérico.
 
 ---
 
-## Handoff para implementation-planner
+## Handoff para wizz-implementation-planner
 
-A `implementation-planner` deve receber:
+A `wizz-implementation-planner` deve receber:
 
 - nível de motion (1–5);
 - motion budget correspondente;
 - componentes a usar;
 - animações a implementar;
-- plano 3D/video (vindo do motion-3d-director, se aplicável);
+- plano 3D/video (vindo do wizz-motion-3d-director, se aplicável);
 - assets;
 - stack (Next.js, Tailwind, shadcn/ui, Framer Motion, GSAP, R3F, etc.);
 - performance constraints (Core Web Vitals, mobile fallback, reduced-motion).
 
-Regra crítica: **não implementar R3F/Three.js se o `motion-3d-director` decidir image-to-video ou hybrid sem 3D real.** A escolha de caminho do diretor de motion é decisiva: o planner executa, não re-decide.
+Regra crítica: **não implementar R3F/Three.js se o `wizz-motion-3d-director` decidir image-to-video ou hybrid sem 3D real.** A escolha de caminho do diretor de motion é decisiva: o planner executa, não re-decide.
 
 ---
 

package/src/skills-lib/{premium-landing-ui-researcher → wizz-premium-landing-ui-researcher}/references/site-levels.md

@@ -365,7 +365,7 @@ Quando este modo estiver ativo, considerar todos os elementos abaixo e escolher
 
 #### Signature 3D: 3D / Video Path
 
-O `motion-3d-director` decide entre quatro caminhos:
+O `wizz-motion-3d-director` decide entre quatro caminhos:
 
 1. 3D real no navegador (R3F/Three.js);
 2. image-to-video;

package/src/skills-lib/{pricing-strategy → wizz-pricing-strategy}/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: pricing-strategy
-description: "When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywall-upgrade-cro."
+name: wizz-pricing-strategy
+description: "When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see wizz-paywall-upgrade-cro."
 metadata:
   version: 1.1.0
 ---
@@ -222,10 +222,10 @@ Identifies which features customers value most:
 
 ## Related Skills
 
-- **churn-prevention**: For cancel flows, save offers, and reducing revenue churn
-- **page-cro**: For optimizing pricing page conversion
-- **copywriting**: For pricing page copy
-- **marketing-psychology**: For pricing psychology principles
-- **ab-test-setup**: For testing pricing changes
-- **revops**: For deal desk processes and pipeline pricing
-- **sales-enablement**: For proposal templates and pricing presentations
+- **wizz-churn-prevention**: For cancel flows, save offers, and reducing revenue churn
+- **wizz-page-cro**: For optimizing pricing page conversion
+- **wizz-copywriting**: For pricing page copy
+- **wizz-marketing-psychology**: For pricing psychology principles
+- **wizz-ab-test-setup**: For testing pricing changes
+- **wizz-revops**: For deal desk processes and pipeline pricing
+- **wizz-sales-enablement**: For proposal templates and pricing presentations

package/src/skills-lib/{pricing-strategy → wizz-pricing-strategy}/evals/evals.json

@@ -1,5 +1,5 @@
 {
-  "skill_name": "pricing-strategy",
+  "skill_name": "wizz-pricing-strategy",
   "evals": [
     {
       "id": 1,

package/src/skills-lib/{product-marketing-context → wizz-product-marketing-context}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: product-marketing-context
+name: wizz-product-marketing-context
 description: "When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing-context.md` that all other skills reference for product, audience, and positioning context."
 metadata:
   version: 1.1.0

package/src/skills-lib/{product-marketing-context → wizz-product-marketing-context}/evals/evals.json

@@ -1,5 +1,5 @@
 {
-  "skill_name": "product-marketing-context",
+  "skill_name": "wizz-product-marketing-context",
   "evals": [
     {
       "id": 1,

package/src/skills-lib/{programmatic-seo → wizz-programmatic-seo}/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: programmatic-seo
-description: When the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pages," "[keyword] + [city] pages," "comparison pages," "integration pages," "building many pages for SEO," "pSEO," "generate 100 pages," "data-driven pages," or "templated landing pages." Use this whenever someone wants to create many similar pages targeting different keywords or locations. For auditing existing SEO issues, see seo-audit. For content strategy planning, see content-strategy.
+name: wizz-programmatic-seo
+description: When the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pages," "[keyword] + [city] pages," "comparison pages," "integration pages," "building many pages for SEO," "pSEO," "generate 100 pages," "data-driven pages," or "templated landing pages." Use this whenever someone wants to create many similar pages targeting different keywords or locations. For auditing existing SEO issues, see wizz-seo-audit. For content strategy planning, see wizz-content-strategy.
 metadata:
   version: 1.1.0
 ---
@@ -232,7 +232,7 @@ Watch for: Thin content warnings, Ranking drops, Manual actions, Crawl errors
 
 ## Related Skills
 
-- **seo-audit**: For auditing programmatic pages after launch
-- **schema-markup**: For adding structured data
-- **site-architecture**: For page hierarchy, URL structure, and internal linking
-- **competitor-alternatives**: For comparison page frameworks
+- **wizz-seo-audit**: For auditing programmatic pages after launch
+- **wizz-schema-markup**: For adding structured data
+- **wizz-site-architecture**: For page hierarchy, URL structure, and internal linking
+- **wizz-competitor-alternatives**: For comparison page frameworks

package/src/skills-lib/{programmatic-seo → wizz-programmatic-seo}/evals/evals.json

@@ -1,5 +1,5 @@
 {
-  "skill_name": "programmatic-seo",
+  "skill_name": "wizz-programmatic-seo",
   "evals": [
     {
       "id": 1,

package/src/skills-lib/{react-components → wizz-react-components}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: react-components
+name: wizz-react-components
 description: Converts Stitch designs into modular Vite and React components using system-level networking and AST-based validation. Use when the user wants to turn a Stitch design/screen into React components, or mentions the Stitch MCP, Vite scaffolding, or AST-based component validation.
 allowed-tools:
   - "stitch*:*"

package/src/skills-lib/{react-components → wizz-react-components}/package.json

@@ -1,5 +1,5 @@
 {
-  "name": "react-components",
+  "name": "wizz-react-components",
   "version": "1.0.0",
   "description": "Design-to-code prompt to React components for Stitch MCP",
   "type": "module",

package/src/skills-lib/{referral-program → wizz-referral-program}/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: referral-program
-description: "When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. Also use when the user mentions 'referral,' 'affiliate,' 'ambassador,' 'word of mouth,' 'viral loop,' 'refer a friend,' 'partner program,' 'referral incentive,' 'how to get referrals,' 'customers referring customers,' or 'affiliate payout.' Use this whenever someone wants existing users or partners to bring in new customers. For launch-specific virality, see launch-strategy."
+name: wizz-referral-program
+description: "When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. Also use when the user mentions 'referral,' 'affiliate,' 'ambassador,' 'word of mouth,' 'viral loop,' 'refer a friend,' 'partner program,' 'referral incentive,' 'how to get referrals,' 'customers referring customers,' or 'affiliate payout.' Use this whenever someone wants existing users or partners to bring in new customers. For launch-specific virality, see wizz-launch-strategy."
 metadata:
   version: 1.1.0
 ---
@@ -249,7 +249,7 @@ For implementation, see the [tools registry](../../tools/REGISTRY.md). Key tools
 
 ## Related Skills
 
-- **launch-strategy**: For launching referral program effectively
-- **email-sequence**: For referral nurture campaigns
-- **marketing-psychology**: For understanding referral motivation
-- **analytics-tracking**: For tracking referral attribution
+- **wizz-launch-strategy**: For launching referral program effectively
+- **wizz-email-sequence**: For referral nurture campaigns
+- **wizz-marketing-psychology**: For understanding referral motivation
+- **wizz-analytics-tracking**: For tracking referral attribution

package/src/skills-lib/{referral-program → wizz-referral-program}/evals/evals.json

@@ -1,5 +1,5 @@
 {
-  "skill_name": "referral-program",
+  "skill_name": "wizz-referral-program",
   "evals": [
     {
       "id": 1,

package/src/skills-lib/{remotion-best-practices → wizz-remotion-best-practices}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: remotion-best-practices
+name: wizz-remotion-best-practices
 description: Best practices for Remotion - Video creation in React. Use when assembling the final video with audio, SFX, captions, or frame-accurate timing, or for any Remotion (React) code.
 metadata:
   tags: remotion, video, react, animation, composition

package/src/skills-lib/{revops → wizz-revops}/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: revops
-description: "When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see email-sequence. For pricing decisions, see pricing-strategy."
+name: wizz-revops
+description: "When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see wizz-cold-email. For email drip campaigns, see wizz-email-sequence. For pricing decisions, see wizz-pricing-strategy."
 metadata:
   version: 1.1.0
 ---
@@ -335,9 +335,9 @@ For implementation, see the [tools registry](../../tools/REGISTRY.md). Key RevOp
 
 ## Related Skills
 
-- **cold-email**: For outbound prospecting emails
-- **email-sequence**: For lifecycle and nurture email flows
-- **pricing-strategy**: For pricing decisions and packaging
-- **analytics-tracking**: For tracking pipeline metrics and attribution
-- **launch-strategy**: For go-to-market launch planning
-- **sales-enablement**: For sales collateral, decks, and objection handling
+- **wizz-cold-email**: For outbound prospecting emails
+- **wizz-email-sequence**: For lifecycle and nurture email flows
+- **wizz-pricing-strategy**: For pricing decisions and packaging
+- **wizz-analytics-tracking**: For tracking pipeline metrics and attribution
+- **wizz-launch-strategy**: For go-to-market launch planning
+- **wizz-sales-enablement**: For sales collateral, decks, and objection handling

package/src/skills-lib/{revops → wizz-revops}/evals/evals.json

@@ -1,5 +1,5 @@
 {
-  "skill_name": "revops",
+  "skill_name": "wizz-revops",
   "evals": [
     {
       "id": 1,

package/src/skills-lib/wizz-router/SKILL.md

@@ -46,7 +46,7 @@ Avalie a **Área**: quantas áreas o pedido toca (design, dev, copy, seo, growth
 
 > Um agente de área só cobre a área dele. 2+ áreas exigem coordenação = trabalho do maestro; a cláusula de área decide sozinha, sem somar com mais nada.
 
-**Descoberta de capacidade (índice, não atalho de delegação):** a [tabela de roteamento flat](references/routing-table-flat.md) também pode ser consultada aqui, dentro de projeto Wizz, quando o pedido não nomeia a capacidade certa (ex.: "quero um carrossel" → índice aponta `canvas-design`). Ela só serve pra achar o nome da capacidade; a entrega continua pelo dispatch normal acima (agente da área / maestro) — nunca dispare a skill direto a partir da tabela dentro de projeto Wizz.
+**Descoberta de capacidade (índice, não atalho de delegação):** a [tabela de roteamento flat](references/routing-table-flat.md) também pode ser consultada aqui, dentro de projeto Wizz, quando o pedido não nomeia a capacidade certa (ex.: "quero um carrossel" → índice aponta `wizz-canvas-design`). Ela só serve pra achar o nome da capacidade; a entrega continua pelo dispatch normal acima (agente da área / maestro) — nunca dispare a skill direto a partir da tabela dentro de projeto Wizz.
 
 **Exemplos calibrados de borda** (do dataset de evals, `evals/routing/dataset.json`):
 

package/src/skills-lib/wizz-router/references/auditoria-360.md

@@ -8,11 +8,11 @@ Ao detectar o gatilho, apresente o menu de áreas via `AskUserQuestion`:
 Vou fazer uma Auditoria 360° do projeto. Escolha as áreas:
 
 [ ] 🔧 Código e Arquitetura — wizz-code-review + wizz-agent-architect
-[ ] 🔒 Segurança — web-security + auth-and-secrets
-[ ] 🗄️ Banco de Dados — supabase-postgres-best-practices + database-scaling + database-and-deps
-[ ] 🎨 Design e UX — ui-ux-pro-max + premium-landing-ui-researcher
-[ ] 📈 Growth e SEO — seo-audit + page-cro + analytics-tracking
-[ ] ⚡ Performance — database-scaling + caching-and-queues + infrastructure
+[ ] 🔒 Segurança — wizz-web-security + wizz-auth-and-secrets
+[ ] 🗄️ Banco de Dados — wizz-supabase-postgres-best-practices + wizz-database-scaling + wizz-database-and-deps
+[ ] 🎨 Design e UX — wizz-ui-ux-pro-max + wizz-premium-landing-ui-researcher
+[ ] 📈 Growth e SEO — wizz-seo-audit + wizz-page-cro + wizz-analytics-tracking
+[ ] ⚡ Performance — wizz-database-scaling + wizz-caching-and-queues + wizz-infrastructure
 [ ] 🧠 Contexto e Decisões — cerebro (aprendizados registrados)
 
 [ ] Selecionar todas as áreas