wizz-method 1.19.0 → 2.0.0

package/src/skills-lib/wizz-router/references/routing-table-flat.md

@@ -1,6 +1,6 @@
 # Tabela de Roteamento — Modo Flat
 
-Use esta tabela pra mapear skills/CLIs/MCPs direto **fora de projeto Wizz** (sem `_wizz/`) — aí o router dispara a skill sozinho. **Dentro de projeto Wizz** ela também pode ser consultada como ÍNDICE DE CAPACIDADES, pra descobrir uma capacidade relevante que o usuário não nomeou (ex.: "quero um carrossel" → `canvas-design`); mas a delegação continua sendo feita pelo dispatch normal do SKILL.md (agente da área / maestro) — a tabela nunca dispara a skill direto dentro de projeto Wizz.
+Use esta tabela pra mapear skills/CLIs/MCPs direto **fora de projeto Wizz** (sem `_wizz/`) — aí o router dispara a skill sozinho. **Dentro de projeto Wizz** ela também pode ser consultada como ÍNDICE DE CAPACIDADES, pra descobrir uma capacidade relevante que o usuário não nomeou (ex.: "quero um carrossel" → `wizz-canvas-design`); mas a delegação continua sendo feita pelo dispatch normal do SKILL.md (agente da área / maestro) — a tabela nunca dispara a skill direto dentro de projeto Wizz.
 
 **Verificação de existência:** antes de oferecer qualquer skill, confirme que ela existe no ambiente (catálogo de skills da sessão ou `ls ~/.claude/skills`); se não existir, não ofereça: use o protocolo de skill faltante (`find-skills`).
 
@@ -8,76 +8,76 @@ Use esta tabela pra mapear skills/CLIs/MCPs direto **fora de projeto Wizz** (sem
 
 | Intenção / palavras-chave | Skills a oferecer | Prioridade |
 |---|---|---|
-| Banco lento, queries, índices, N+1, sharding, connection pool | `database-scaling` + `supabase-postgres-best-practices` | 1 |
-| Cache, Redis, filas, BullMQ, SQS, Kafka, job assíncrono | `caching-and-queues` | 1 |
-| Kubernetes, auto-scaling, CDN, capacidade, SLO, load test | `infrastructure` | 1 |
-| Cloud spend, custo de infra, right-sizing, AWS/GCP billing | `cloud-and-infra` | 1 |
-| Auth, secrets, tokens, OAuth, JWT, Clerk, permissões | `auth-and-secrets` + `web-security` | 1 |
-| Dependências, packages, vulnerabilidades, npm audit | `database-and-deps` | 2 |
-| Segurança, XSS, CSRF, SQLi, IDOR, OWASP, rate limit, CORS, clickjacking, PII na resposta, enumeração de usuário, headers | `web-security` + `auth-and-secrets` | 1 |
+| Banco lento, queries, índices, N+1, sharding, connection pool | `wizz-database-scaling` + `wizz-supabase-postgres-best-practices` | 1 |
+| Cache, Redis, filas, BullMQ, SQS, Kafka, job assíncrono | `wizz-caching-and-queues` | 1 |
+| Kubernetes, auto-scaling, CDN, capacidade, SLO, load test | `wizz-infrastructure` | 1 |
+| Cloud spend, custo de infra, right-sizing, AWS/GCP billing | `wizz-cloud-and-infra` | 1 |
+| Auth, secrets, tokens, OAuth, JWT, Clerk, permissões | `wizz-auth-and-secrets` + `wizz-web-security` | 1 |
+| Dependências, packages, vulnerabilidades, npm audit | `wizz-database-and-deps` | 2 |
+| Segurança, XSS, CSRF, SQLi, IDOR, OWASP, rate limit, CORS, clickjacking, PII na resposta, enumeração de usuário, headers | `wizz-web-security` + `wizz-auth-and-secrets` | 1 |
 | Auditoria/pentest de segurança do app inteiro, "auditar segurança", "pentest", "encontrar vulnerabilidades", varredura antes de release | `security-audit-pentest` | 1 |
-| Auditoria de prontidão pra lançamento, "tá pronto pra lançar?", checklist de release amplo (técnico, segurança, SEO, analytics, conteúdo, legal, infra), "o que falta antes de ir pra produção" | `launch-readiness` | 1 |
-| Desktop, Electron, contextIsolation, code signing | `desktop-security` | 2 |
+| Auditoria de prontidão pra lançamento, "tá pronto pra lançar?", checklist de release amplo (técnico, segurança, SEO, analytics, conteúdo, legal, infra), "o que falta antes de ir pra produção" | `wizz-launch-readiness` | 1 |
+| Desktop, Electron, contextIsolation, code signing | `wizz-desktop-security` | 2 |
 
 ## Área Técnica — Código e Qualidade
 
 | Intenção / palavras-chave | Skills a oferecer | Prioridade |
 |---|---|---|
-| Revisar código, code review, qualidade, segunda opinião adversarial | `adversarial-reviewer` | 1 |
+| Revisar código, code review, qualidade, segunda opinião adversarial | `wizz-adversarial-reviewer` | 1 |
 | Novo feature, bug fix, TDD, testes, cobertura | execução direta com TDD (rules globais) e verificação end-to-end ao final | 1 |
 | Build quebrado, erros de TypeScript, lint, CI | execução direta (fix mínimo até build verde) | 2 |
-| Arquitetura, design de sistema, decisão técnica, plano técnico, breakdown, handoff | `implementation-planner` | 1 |
-| Fluxo crítico, E2E, verificação visual no browser | `agent-browser` | 2 |
-| SQL, schema, migrations, Supabase, RLS, performance de queries | `supabase-postgres-best-practices` + `database-scaling` | 1 |
-| Dead code, limpeza, refactoring | execução direta + `adversarial-reviewer` na revisão | 2 |
-| Novo projeto, iniciar app, ponto de partida, onboarding dev | `inicio-de-projeto` | 1 |
-| Construir/melhorar agente ou produto de IA, system prompt, tool definitions | `ai-product-design` | 1 |
+| Arquitetura, design de sistema, decisão técnica, plano técnico, breakdown, handoff | `wizz-implementation-planner` | 1 |
+| Fluxo crítico, E2E, verificação visual no browser | `wizz-agent-browser` | 2 |
+| SQL, schema, migrations, Supabase, RLS, performance de queries | `wizz-supabase-postgres-best-practices` + `wizz-database-scaling` | 1 |
+| Dead code, limpeza, refactoring | execução direta + `wizz-adversarial-reviewer` na revisão | 2 |
+| Novo projeto, iniciar app, ponto de partida, onboarding dev | `wizz-inicio-de-projeto` | 1 |
+| Construir/melhorar agente ou produto de IA, system prompt, tool definitions | `wizz-ai-product-design` | 1 |
 
 ## Área de Design e UI
 
 | Intenção / palavras-chave | Skills a oferecer | Prioridade |
 |---|---|---|
-| Design, UI, visual, componente, estilo, paleta, tipografia, sistema de design | `ui-ux-pro-max` + `ui-component-curator` | 1 |
-| Landing page, hero, motion, animação 3D, conversão, CRO visual | `premium-landing-ui-researcher` | 1 |
-| Qualidade de design, anti-slop, gosto visual, estética, olhar crítico | `taste-skill` (se instalada) | 1 |
-| Regras de frontend, código UI determinístico, 44 regras, audit de frontend | `impeccable` (se instalada) | 2 |
-| Design system HTML-native, filosofia visual, review 5-dim, export MP4 | `huashu-design` (se instalada) | 2 |
-| Animação, motion, vídeo programático em código, Remotion, Three.js, 3D, WebGL | `motion-3d-director` + `remotion-best-practices` | 1 |
-| Craft de animação/micro-interação, easing, timing, reduced-motion, "essa animação travou/tá ruim" | `animate` + `design-motion-principles` | 2 |
-| Gerar imagem por código: carrossel, quote card, infográfico (PNG/PDF editável), fundo/textura generativa de hero | `canvas-design` + `algorithmic-art` | 2 |
-| **Vídeo com áudio, narração, SFX ou legenda sincronizada** (montagem do filme) | `remotion-best-practices` (Remotion monta; timing de frame). Regra do pipeline: HyperFrames desenha as telas mudas, Remotion monta o filme — não usar hyperframes para posicionar áudio/legenda (drift de ~2,76s e CSS vazando entre telas em produção) | 1 |
+| Design, UI, visual, componente, estilo, paleta, tipografia, sistema de design | `wizz-ui-ux-pro-max` + `wizz-ui-component-curator` | 1 |
+| Landing page, hero, motion, animação 3D, conversão, CRO visual | `wizz-premium-landing-ui-researcher` | 1 |
+| Qualidade de design, anti-slop, gosto visual, estética, olhar crítico | `wizz-taste-skill` (se instalada) | 1 |
+| Regras de frontend, código UI determinístico, 44 regras, audit de frontend | `wizz-impeccable` (se instalada) | 2 |
+| Design system HTML-native, filosofia visual, review 5-dim, export MP4 | `wizz-huashu-design` (se instalada) | 2 |
+| Animação, motion, vídeo programático em código, Remotion, Three.js, 3D, WebGL | `wizz-motion-3d-director` + `wizz-remotion-best-practices` | 1 |
+| Craft de animação/micro-interação, easing, timing, reduced-motion, "essa animação travou/tá ruim" | `wizz-animate` + `wizz-design-motion-principles` | 2 |
+| Gerar imagem por código: carrossel, quote card, infográfico (PNG/PDF editável), fundo/textura generativa de hero | `wizz-canvas-design` + `wizz-algorithmic-art` | 2 |
+| **Vídeo com áudio, narração, SFX ou legenda sincronizada** (montagem do filme) | `wizz-remotion-best-practices` (Remotion monta; timing de frame). Regra do pipeline: HyperFrames desenha as telas mudas, Remotion monta o filme — não usar hyperframes para posicionar áudio/legenda (drift de ~2,76s e CSS vazando entre telas em produção) | 1 |
 | Desenhar TELA/cena de vídeo em HTML/CSS, visual mudo (maqueta de app, gráfico animado, título, loop; HTML→MP4) | CLI `hyperframes` (registry designer; `npx skills add heygen-com/hyperframes`) — só telas mudas; montagem com áudio vai pro Remotion (linha acima) | 2 |
 | Timestamps palavra a palavra de narração TTS (sincronizar legenda/corte/animação com a fala) | `ctc-align` (registry designer; fonte única de timing, substitui Whisper) | 2 |
 | **Editar/cortar vídeo** (cortes, selects, roughcut) | CLI `buttercut` (registry designer; **só Apple Silicon**, clone-and-run no projeto, deps pesadas) | 1 |
 | Gerar vídeo-ad/imagem por IA (Sora/Veo/Kling) + publicar Meta | CLI `arcads` (registry `ads`; git clone + Arcads API key) | 1 |
 | Analisar/entender vídeo existente (frames + transcrição) | CLI `claude-video` (registry designer; `npx skills add bradautomates/claude-video`) | 2 |
 | Narração / voz / TTS / clonagem de voz para vídeo | CLI `voicebox` (registry designer; app local com endpoint MCP) | 2 |
-| Pesquisar componentes compatíveis com o projeto | `ui-component-curator` (demos, código e registries públicos com evidências) | 1 |
+| Pesquisar componentes compatíveis com o projeto | `wizz-ui-component-curator` (demos, código e registries públicos com evidências) | 1 |
 
 ## Área de Marketing / Growth
 
 | Intenção / palavras-chave | Skills a oferecer | Prioridade |
 |---|---|---|
-| Ideias de marketing, estratégia de marketing, posicionamento | `marketing-ideas` + `marketing-psychology` + `product-marketing-context` | 1 |
-| Paid ads, anúncios, Google Ads, Meta Ads, TikTok Ads, mídia paga | `paid-ads` + `ad-creative` + `analytics-tracking` | 1 |
-| Pixel/UTM/atribuição erradas, "a venda não bate com o gerenciador", "onde está furando o funil", tráfego orgânico inflado, conferir tracking antes de subir campanha | `tracking-audit` (+ `analytics-tracking` se for SaaS/produto) | 1 |
-| Lançamento de feature, lançamento de produto, go-to-market | `launch-strategy` + `social-content` + `email-sequence` | 1 |
+| Ideias de marketing, estratégia de marketing, posicionamento | `wizz-marketing-ideas` + `wizz-marketing-psychology` + `wizz-product-marketing-context` | 1 |
+| Paid ads, anúncios, Google Ads, Meta Ads, TikTok Ads, mídia paga | `wizz-paid-ads` + `wizz-ad-creative` + `wizz-analytics-tracking` | 1 |
+| Pixel/UTM/atribuição erradas, "a venda não bate com o gerenciador", "onde está furando o funil", tráfego orgânico inflado, conferir tracking antes de subir campanha | `wizz-tracking-audit` (+ `wizz-analytics-tracking` se for SaaS/produto) | 1 |
+| Lançamento de feature, lançamento de produto, go-to-market | `wizz-launch-strategy` + `wizz-social-content` + `wizz-email-sequence` | 1 |
 | Site pronto pra subir, pré-lançamento de SITE, "revisa antes do deploy", checklist de go-live, ou item pontual pré-lançamento (og:image/prévia de link, FAQ com schema, robots.txt, LGPD, alt text) | `site-launch-kit` | 1 |
-| Preço, planos, pricing, monetização | `pricing-strategy` + `paywall-upgrade-cro` | 1 |
-| Churn, retenção, cancelamento, NPS | `churn-prevention` + `revops` | 1 |
-| Conversão de página, CRO, otimização de funil | `page-cro` + `copywriting` + `form-cro` | 1 |
-| Signup, onboarding, ativação de usuário | `signup-flow-cro` + `onboarding-cro` | 1 |
-| SEO, Google, busca, AI search, LLM SEO | `seo-audit` + `ai-seo` + `schema-markup` + `programmatic-seo` + `site-architecture` | 1 |
-| Comparativo vs concorrente, alternatives page, war room | `competitor-alternatives` | 2 |
-| Conteúdo, social media, newsletter, threads | `content-strategy` + `social-content` + `copy-editing` | 2 |
-| Cold email, outbound B2B, prospecção | `cold-email` | 2 |
-| Referral, indicação, programa de afiliados | `referral-program` | 2 |
-| Material de vendas, pitch, deck, proposta | `sales-enablement` | 2 |
-| Ferramenta grátis de captação de leads | `free-tool-strategy` | 2 |
-| A/B test, variações, experimentos de conversão | `ab-test-setup` + `analytics-tracking` | 2 |
-| Copywriting, copy, persuasão, texto de venda | `copywriting` + `humanizer` | 1 |
+| Preço, planos, pricing, monetização | `wizz-pricing-strategy` + `wizz-paywall-upgrade-cro` | 1 |
+| Churn, retenção, cancelamento, NPS | `wizz-churn-prevention` + `wizz-revops` | 1 |
+| Conversão de página, CRO, otimização de funil | `wizz-page-cro` + `wizz-copywriting` + `wizz-form-cro` | 1 |
+| Signup, onboarding, ativação de usuário | `wizz-signup-flow-cro` + `wizz-onboarding-cro` | 1 |
+| SEO, Google, busca, AI search, LLM SEO | `wizz-seo-audit` + `wizz-ai-seo` + `wizz-schema-markup` + `wizz-programmatic-seo` + `wizz-site-architecture` | 1 |
+| Comparativo vs concorrente, alternatives page, war room | `wizz-competitor-alternatives` | 2 |
+| Conteúdo, social media, newsletter, threads | `wizz-content-strategy` + `wizz-social-content` + `wizz-copy-editing` | 2 |
+| Cold email, outbound B2B, prospecção | `wizz-cold-email` | 2 |
+| Referral, indicação, programa de afiliados | `wizz-referral-program` | 2 |
+| Material de vendas, pitch, deck, proposta | `wizz-sales-enablement` | 2 |
+| Ferramenta grátis de captação de leads | `wizz-free-tool-strategy` | 2 |
+| A/B test, variações, experimentos de conversão | `wizz-ab-test-setup` + `wizz-analytics-tracking` | 2 |
+| Copywriting, copy, persuasão, texto de venda | `wizz-copywriting` + `wizz-humanizer` | 1 |
 | Pesquisa de público de oferta, VoC, matriz de ângulos, léxico de infoproduto | `pesquisa-de-publico-do-piva` | 1 |
-| Forjar oferta, criar oferta irresistível, mecanismo único, bônus, garantia | `wizz-offer-forge` + `pricing-strategy` | 1 |
+| Forjar oferta, criar oferta irresistível, mecanismo único, bônus, garantia | `wizz-offer-forge` + `wizz-pricing-strategy` | 1 |
 | Pesquisa de mercado, inteligência competitiva | `deep-research` (plugin externo — só se instalado) | 2 |
 
 ## Contexto e Memória
@@ -96,4 +96,4 @@ Quando nenhuma skill/MCP instalado cobrir o pedido, **classifique o que falta**
 
 **Falta um MCP:** informe → `claude mcp list` → consulte `skills-registry.yaml` (`mcps:`/`mcp_utility:`, com `server` pronto) → proponha `claude mcp add <id> [-e VAR=$VAR] -- <command> [args]`. Secrets sempre via env/placeholder, nunca token real.
 
-MCPs comuns: context7 (docs de libs), supabase (Postgres), exa (pesquisa). Browser/E2E é sempre via CLI `agent-browser`, nunca via MCP Playwright.
+MCPs comuns: context7 (docs de libs), supabase (Postgres), exa (pesquisa). Browser/E2E é sempre via CLI `wizz-agent-browser`, nunca via MCP Playwright.

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

@@ -1,6 +1,6 @@
 ---
-name: sales-enablement
-description: "When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps.' Use this for any document or asset that helps a sales team close deals. For competitor comparison pages and battle cards, see competitor-alternatives. For marketing website copy, see copywriting. For cold outreach emails, see cold-email."
+name: wizz-sales-enablement
+description: "When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps.' Use this for any document or asset that helps a sales team close deals. For competitor comparison pages and battle cards, see wizz-competitor-alternatives. For marketing website copy, see wizz-copywriting. For cold outreach emails, see wizz-cold-email."
 metadata:
   version: 1.1.0
 ---
@@ -341,9 +341,9 @@ If context is missing, ask:
 
 ## Related Skills
 
-- **competitor-alternatives**: For public-facing comparison and alternative pages
-- **copywriting**: For marketing website copy
-- **cold-email**: For outbound prospecting emails
-- **revops**: For lead lifecycle, scoring, routing, and pipeline management
-- **pricing-strategy**: For pricing decisions and packaging
-- **product-marketing-context**: For foundational positioning and messaging
+- **wizz-competitor-alternatives**: For public-facing comparison and alternative pages
+- **wizz-copywriting**: For marketing website copy
+- **wizz-cold-email**: For outbound prospecting emails
+- **wizz-revops**: For lead lifecycle, scoring, routing, and pipeline management
+- **wizz-pricing-strategy**: For pricing decisions and packaging
+- **wizz-product-marketing-context**: For foundational positioning and messaging

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

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

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

@@ -1,6 +1,6 @@
 ---
-name: schema-markup
-description: When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," "breadcrumb schema," "Google rich results," "knowledge panel," "star ratings in search," or "add structured data." Use this whenever someone wants their pages to show enhanced results in Google. For broader SEO issues, see seo-audit. For AI search optimization, see ai-seo.
+name: wizz-schema-markup
+description: When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," "breadcrumb schema," "Google rich results," "knowledge panel," "star ratings in search," or "add structured data." Use this whenever someone wants their pages to show enhanced results in Google. For broader SEO issues, see wizz-seo-audit. For AI search optimization, see wizz-ai-seo.
 metadata:
   version: 1.1.0
 ---
@@ -173,7 +173,7 @@ You can combine multiple schema types on one page using `@graph`:
 
 ## Related Skills
 
-- **seo-audit**: For overall SEO including schema review
-- **ai-seo**: For AI search optimization (schema helps AI understand content)
-- **programmatic-seo**: For templated schema at scale
-- **site-architecture**: For breadcrumb structure and navigation schema planning
+- **wizz-seo-audit**: For overall SEO including schema review
+- **wizz-ai-seo**: For AI search optimization (schema helps AI understand content)
+- **wizz-programmatic-seo**: For templated schema at scale
+- **wizz-site-architecture**: For breadcrumb structure and navigation schema planning

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

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

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

@@ -1,6 +1,6 @@
 ---
-name: seo-audit
-description: When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup. For AI search optimization, see ai-seo.
+name: wizz-seo-audit
+description: When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see wizz-programmatic-seo. For adding structured data, see wizz-schema-markup. For AI search optimization, see wizz-ai-seo.
 metadata:
   version: 1.1.0
 ---
@@ -368,7 +368,7 @@ Same format as above
 ## References
 
 - [AI Writing Detection](references/ai-writing-detection.md): Common AI writing patterns to avoid (em dashes, overused phrases, filler words)
-- For AI search optimization (AEO, GEO, LLMO, AI Overviews), see the **ai-seo** skill
+- For AI search optimization (AEO, GEO, LLMO, AI Overviews), see the **wizz-ai-seo** skill
 
 ---
 
@@ -404,9 +404,9 @@ Same format as above
 
 ## Related Skills
 
-- **ai-seo**: For optimizing content for AI search engines (AEO, GEO, LLMO)
-- **programmatic-seo**: For building SEO pages at scale
-- **site-architecture**: For page hierarchy, navigation design, and URL structure
-- **schema-markup**: For implementing structured data
-- **page-cro**: For optimizing pages for conversion (not just ranking)
-- **analytics-tracking**: For measuring SEO performance
+- **wizz-ai-seo**: For optimizing content for AI search engines (AEO, GEO, LLMO)
+- **wizz-programmatic-seo**: For building SEO pages at scale
+- **wizz-site-architecture**: For page hierarchy, navigation design, and URL structure
+- **wizz-schema-markup**: For implementing structured data
+- **wizz-page-cro**: For optimizing pages for conversion (not just ranking)
+- **wizz-analytics-tracking**: For measuring SEO performance

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

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

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

@@ -1,6 +1,6 @@
 ---
-name: signup-flow-cro
-description: When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions "signup conversions," "registration friction," "signup form optimization," "free trial signup," "reduce signup dropoff," "account creation flow," "people aren't signing up," "signup abandonment," "trial conversion rate," "nobody completes registration," "too many steps to sign up," or "simplify our signup." Use this whenever the user has a signup or registration flow that isn't performing. For post-signup onboarding, see onboarding-cro. For lead capture forms (not account creation), see form-cro.
+name: wizz-signup-flow-cro
+description: When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions "signup conversions," "registration friction," "signup form optimization," "free trial signup," "reduce signup dropoff," "account creation flow," "people aren't signing up," "signup abandonment," "trial conversion rate," "nobody completes registration," "too many steps to sign up," or "simplify our signup." Use this whenever the user has a signup or registration flow that isn't performing. For post-signup onboarding, see wizz-onboarding-cro. For lead capture forms (not account creation), see wizz-form-cro.
 metadata:
   version: 1.1.0
 ---
@@ -45,7 +45,7 @@ Before providing recommendations, understand:
 
 ## Related Skills
 
-- **onboarding-cro**: For optimizing what happens after signup
-- **form-cro**: For non-signup forms (lead capture, contact)
-- **page-cro**: For the landing page leading to signup
-- **ab-test-setup**: For testing signup flow changes
+- **wizz-onboarding-cro**: For optimizing what happens after signup
+- **wizz-form-cro**: For non-signup forms (lead capture, contact)
+- **wizz-page-cro**: For the landing page leading to signup
+- **wizz-ab-test-setup**: For testing signup flow changes

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

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

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

@@ -1,6 +1,6 @@
 ---
-name: site-architecture
-description: When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what pages a website should have and how they connect. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema-markup.
+name: wizz-site-architecture
+description: When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what pages a website should have and how they connect. NOT for XML sitemaps (that's technical SEO — see wizz-seo-audit). For SEO audits, see wizz-seo-audit. For structured data, see wizz-schema-markup.
 metadata:
   version: 1.1.0
 ---
@@ -349,9 +349,9 @@ Mermaid diagram showing page relationships and navigation zones. Use `graph TD`
 
 ## Related Skills
 
-- **content-strategy**: For planning what content to create and topic clusters
-- **programmatic-seo**: For building SEO pages at scale with templates and data
-- **seo-audit**: For technical SEO, on-page optimization, and indexation issues
-- **page-cro**: For optimizing individual pages for conversion
-- **schema-markup**: For implementing breadcrumb and site navigation structured data
-- **competitor-alternatives**: For comparison page frameworks and URL patterns
+- **wizz-content-strategy**: For planning what content to create and topic clusters
+- **wizz-programmatic-seo**: For building SEO pages at scale with templates and data
+- **wizz-seo-audit**: For technical SEO, on-page optimization, and indexation issues
+- **wizz-page-cro**: For optimizing individual pages for conversion
+- **wizz-schema-markup**: For implementing breadcrumb and site navigation structured data
+- **wizz-competitor-alternatives**: For comparison page frameworks and URL patterns

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

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

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

@@ -1,6 +1,6 @@
 ---
-name: social-content
-description: "When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' 'viral content,' 'what should I post,' 'repurpose this content,' 'tweet ideas,' 'LinkedIn carousel,' 'social media strategy,' or 'grow my following.' Use this for any social media content creation, repurposing, or scheduling task. For broader content strategy, see content-strategy."
+name: wizz-social-content
+description: "When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' 'viral content,' 'what should I post,' 'repurpose this content,' 'tweet ideas,' 'LinkedIn carousel,' 'social media strategy,' or 'grow my following.' Use this for any social media content creation, repurposing, or scheduling task. For broader content strategy, see wizz-content-strategy."
 metadata:
   version: 1.1.0
 ---
@@ -272,7 +272,7 @@ Instead of guessing, analyze what's working for top creators in your niche:
 
 ## Related Skills
 
-- **copywriting**: For longer-form content that feeds social
-- **launch-strategy**: For coordinating social with launches
-- **email-sequence**: For nurturing social audience via email
-- **marketing-psychology**: For understanding what drives engagement
+- **wizz-copywriting**: For longer-form content that feeds social
+- **wizz-launch-strategy**: For coordinating social with launches
+- **wizz-email-sequence**: For nurturing social audience via email
+- **wizz-marketing-psychology**: For understanding what drives engagement

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

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

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

@@ -1,5 +1,5 @@
 ---
-name: supabase-postgres-best-practices
+name: wizz-supabase-postgres-best-practices
 description: Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations. Use when the user asks about missing indexes, connection pooling, RLS performance, N+1 queries, or Postgres/Supabase schema design.
 license: MIT
 metadata:

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

@@ -1,5 +1,5 @@
 ---
-name: taste-skill
+name: wizz-taste-skill
 description: Anti-slop frontend skill for landing pages, portfolios, and redesigns or audits of existing sites and apps. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. On an existing project it audits the current design first, identifies generic AI patterns, lists every problem found, and prioritizes fixes without breaking functionality, working with any CSS framework or vanilla CSS. Real design systems when applicable, audit-first on redesigns, strict pre-flight check. Use when building, redesigning, or auditing a landing page, portfolio, or marketing site, or when upgrading an existing site or app that looks generic or AI-generated. Detailed rules live in references/, loaded on demand.
 ---
 

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

@@ -1,6 +1,6 @@
 ---
-name: tracking-audit
-description: Auditoria e diagnóstico de rastreamento de resposta direta em dois modos. Modo implantação valida pixel, CAPI, domínio verificado, eventos priorizados, template de UTM com ID, repasse do parâmetro nativo pelo checkout, higiene de nomenclatura e compra-teste por caminho. Modo diagnóstico lê as transições do funil contra a régua, separa problema de medição de problema de conversão e diz qual transição está furando. Use quando alguém perguntar "por que a venda não bate com o gerenciador", "onde está furando o funil", "meu pixel está certo?", "as UTMs estão corretas?", "o tráfego orgânico está inflado", "qual dado falta pra eu decidir", ou antes de subir campanha nova. NÃO use para desenhar plano de medição de SaaS/produto (use analytics-tracking), para decidir bid e orçamento (use paid-ads) nem para criar a oferta (use wizz-offer-forge).
+name: wizz-tracking-audit
+description: Auditoria e diagnóstico de rastreamento de resposta direta em dois modos. Modo implantação valida pixel, CAPI, domínio verificado, eventos priorizados, template de UTM com ID, repasse do parâmetro nativo pelo checkout, higiene de nomenclatura e compra-teste por caminho. Modo diagnóstico lê as transições do funil contra a régua, separa problema de medição de problema de conversão e diz qual transição está furando. Use quando alguém perguntar "por que a venda não bate com o gerenciador", "onde está furando o funil", "meu pixel está certo?", "as UTMs estão corretas?", "o tráfego orgânico está inflado", "qual dado falta pra eu decidir", ou antes de subir campanha nova. NÃO use para desenhar plano de medição de SaaS/produto (use wizz-analytics-tracking), para decidir bid e orçamento (use wizz-paid-ads) nem para criar a oferta (use wizz-offer-forge).
 ---
 
 # Tracking Audit
@@ -64,15 +64,15 @@ Feche com **PENDÊNCIAS**: o que não deu para verificar e o que precisa de aces
 
 ## Ferramentas
 
-- Inspeção de página: CLI `agent-browser`. Nunca Playwright.
+- Inspeção de página: CLI `wizz-agent-browser`. Nunca Playwright.
 - Nada mais é obrigatório. A auditoria funciona lendo print e página.
 
 ## Quando delegar
 
 | Situação | Vai para |
 |---|---|
-| O furo é a página (LCP, mobile, blocos) | `page-cro` |
-| O furo é o criativo | `ad-creative` |
-| O furo é bid, orçamento ou estrutura de campanha | `paid-ads` |
-| Precisa desenhar medição de produto ou SaaS | `analytics-tracking` |
+| O furo é a página (LCP, mobile, blocos) | `wizz-page-cro` |
+| O furo é o criativo | `wizz-ad-creative` |
+| O furo é bid, orçamento ou estrutura de campanha | `wizz-paid-ads` |
+| Precisa desenhar medição de produto ou SaaS | `wizz-analytics-tracking` |
 | A oferta em si não fecha | `wizz-offer-forge` |

package/src/skills-lib/{tracking-audit → wizz-tracking-audit}/references/modo-implantacao.md

@@ -8,7 +8,7 @@ Régua: leia o Passo 0 do `SKILL.md` antes. Sem régua declarada, o relatório s
 
 | Verificar | Como | Reprova quando |
 |---|---|---|
-| Página abre no mobile real | `agent-browser` em viewport de celular | Layout quebra ou bloco some |
+| Página abre no mobile real | `wizz-agent-browser` em viewport de celular | Layout quebra ou bloco some |
 | Tempo até o conteúdo principal | PageSpeed Insights, aba mobile | Fora da meta declarada pela régua do projeto |
 | Redirect | Abrir o link do anúncio sem encurtador no meio | Qualquer salto extra ou loop |
 | SSL | Cadeado e certificado válido no domínio final | Aviso do navegador |

package/src/skills-lib/{ui-component-curator → wizz-ui-component-curator}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: ui-component-curator
+name: wizz-ui-component-curator
 description: analyze an existing frontend project, infer its visual style and product tone, then research and recommend compatible UI components and effects from public component catalogs, registries and source repositories. use when the user wants help choosing components, effects, sections, or visual patterns that fit an existing project — especially hero effects, cards, buttons, testimonials, pricing sections, navigation, or any interactive pattern. trigger whenever the user wants to add a UI element and wants Claude to study the project first before suggesting options. always inspect the codebase and exact component sources, provide evidence and plan before editing.
 ---
 

package/src/skills-lib/{ui-ux-pro-max → wizz-ui-ux-pro-max}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: ui-ux-pro-max
+name: wizz-ui-ux-pro-max
 description: "UI/UX design intelligence. 67 styles, 96 palettes, 57 font pairings, 25 charts, 13 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples. Use when the user asks to design, build, or review UI/UX, pick a color palette or font pairing, or style a component like a button, modal, navbar, or card."
 ---
 # UI/UX Pro Max - Design Intelligence
@@ -21,10 +21,10 @@ Reference these guidelines when:
 
 Before producing UI code, inspect the existing project and choose the research skill:
 
-- New landing page or a full page composition: invoke `skill:premium-landing-ui-researcher` for source research and section planning.
-- A component or effect in an existing project: invoke `skill:ui-component-curator` to inspect compatible candidates.
-- Existing UI polish only: invoke `skill:impeccable`; invoke `skill:taste-skill` when a redesign direction is needed.
-- HTML prototype/visual variants: invoke `skill:huashu-design`. Stitch-to-React conversion: invoke `skill:react-components`.
+- New landing page or a full page composition: invoke `skill:wizz-premium-landing-ui-researcher` for source research and section planning.
+- A component or effect in an existing project: invoke `skill:wizz-ui-component-curator` to inspect compatible candidates.
+- Existing UI polish only: invoke `skill:wizz-impeccable`; invoke `skill:wizz-taste-skill` when a redesign direction is needed.
+- HTML prototype/visual variants: invoke `skill:wizz-huashu-design`. Stitch-to-React conversion: invoke `skill:wizz-react-components`.
 
 The local Python database below recommends design tokens and patterns; it does **not** search the web, inspect component source code, or prove that a component exists. For component research, require exact demo/source URLs, inspected files or registry items, revision/date, license, dependencies and a fit decision. Continue with an available public source if one fails; state any unverified result. Do not claim research based only on the database output.
 

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

@@ -1,5 +1,5 @@
 ---
-name: web-security
+name: wizz-web-security
 description: >
   Revisar segurança de apps web. Usar quando: auditar vulnerabilidades, antes de deploy/PR, implementar auth,
   adicionar endpoint de API, lidar com input de usuário, configurar headers, CSP, rate limiting, CORS, clickjacking,
@@ -26,8 +26,8 @@ As que mais aparecem numa auditoria, com a correção direta. Use como triagem r
 | 8 | Extração por paginação (base inteira registro a registro) | 🟠 Alta | Filtrar por dono na query + limite de página + detecção de varredura | `references/headers-rate-limit-cors.md` |
 | 9 | CORS refletindo o `Origin` | 🟠 Alta | Allowlist de origens, nunca ecoar o `Origin` recebido | `references/headers-rate-limit-cors.md` |
 | 10 | PII/dado demais na resposta (até hash de senha) | 🟠 Alta | Retornar só os campos necessários (allowlist de saída) | `references/headers-rate-limit-cors.md` |
-| 11 | JWT na URL / token vivo pós-logout | 🟠 Alta | Token no header `Authorization` + revogar no logout | skill `auth-and-secrets` |
-| 12 | Enumeração de usuário (erro revela se e-mail existe) | 🟡 Média | Mensagem genérica + resposta em tempo constante | skill `auth-and-secrets` |
+| 11 | JWT na URL / token vivo pós-logout | 🟠 Alta | Token no header `Authorization` + revogar no logout | skill `wizz-auth-and-secrets` |
+| 12 | Enumeração de usuário (erro revela se e-mail existe) | 🟡 Média | Mensagem genérica + resposta em tempo constante | skill `wizz-auth-and-secrets` |
 | 13 | Clickjacking (sem header) | 🟡 Média (1 min) | `X-Frame-Options: DENY` + CSP `frame-ancestors 'none'` | `references/headers-rate-limit-cors.md` |
 
 > As quatro primeiras (SQLi, IDOR, mass assignment e RLS permissiva) são **parada de linha**: apareceu, corrige antes de qualquer coisa.

package/src/skills-lib/{web-security → wizz-web-security}/references/headers-rate-limit-cors.md

@@ -53,7 +53,7 @@ async headers() {
 - Endpoints de cobrança (checkout, portal): sempre com rate limit
 - Next.js: `@upstash/ratelimit` no route handler, ou WAF da Vercel para regras por rota
 - Fail closed: se o backend do rate limit cair (ex: Redis fora), rotas de escrita devem negar a request, não deixar passar
-- Comparações de token/secret: `crypto.timingSafeEqual`, nunca `!==` (detalhe em auth-and-secrets)
+- Comparações de token/secret: `crypto.timingSafeEqual`, nunca `!==` (detalhe em wizz-auth-and-secrets)
 - Sem rate limit = brute force de graça. Somar lockout/CAPTCHA após N falhas no login
 
 ### Origem do IP atrás de proxy/CDN

package/tools/fetch-assets.mjs

@@ -45,14 +45,14 @@ export const BUNDLES = {
   'huashu-audio': {
     url: `${RELEASE_BASE}/huashu-audio.tar.gz`,
     sha256: 'd20ddaefb7fd560837dec8d57ae8698ee51ef553d61a1367f0491183c613129f',
-    dest: 'src/skills-lib/huashu-design/assets',
+    dest: 'src/skills-lib/wizz-huashu-design/assets',
     marker: 'bgm-ad.mp3',
     description: '6 trilhas BGM + SFX (huashu-design/assets/**/*.mp3, ~27MB)',
   },
   'canvas-fonts': {
     url: `${RELEASE_BASE}/canvas-fonts.tar.gz`,
     sha256: '7ac839f1dee2883b8e9a7022f246cfece4e203a2fd6ea23c81a5ffa49b812396',
-    dest: 'src/skills-lib/canvas-design/canvas-fonts',
+    dest: 'src/skills-lib/wizz-canvas-design/canvas-fonts',
     marker: 'Outfit-Regular.ttf',
     description: '~54 variantes de fonte (canvas-design/canvas-fonts/*.ttf, ~2.5MB)',
   },

package/tools/installer/commands/fetch-assets.js

@@ -11,7 +11,7 @@
 // mesma convenção do resto do CLI em vez de mexer no loader compartilhado.
 //
 // Por que uma flag --dest é essencial: uma skill instalada globalmente
-// (~/.claude/skills/huashu-design/) ou num projeto (.claude/skills/...) é uma
+// (~/.claude/skills/wizz-huashu-design/) ou num projeto (.claude/skills/...) é uma
 // CÓPIA separada do pacote npm de origem — baixar só no pacote de origem não
 // ajuda a cópia já instalada. `npx wizz-method fetch-assets --bundle
 // huashu-audio --dest <pasta-da-skill>/assets`, rodado de dentro da skill

package/tools/installer/modules/cli-config.js

@@ -2,7 +2,7 @@
 //
 // Sibling of modules/mcp-config.js. Where MCPs are *servers* merged into the
 // project's .mcp.json, CLIs are *binaries* the agents call directly (e.g.
-// `agent-browser` for browser verification, `rtk` for token economy). The
+// `wizz-agent-browser` for browser verification, `rtk` for token economy). The
 // skills-registry.yaml is the single source of truth for both: each AREA may
 // declare a `clis:` list, plus a top-level `cli_utility:` for cross-cutting
 // tools. Each entry has: