wizz-method 1.18.3 → 2.0.0

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

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