wizz-method 1.18.3 → 2.0.0

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: