wizz-method 1.19.0 → 2.1.0

package/src/skills-lib/wizz-react-components/LICENSE.txt

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Anthropic, PBC.
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

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

@@ -32,13 +32,13 @@ Descubra o contexto: **existe `{project-root}/_wizz/`?**
 
 ### A) Dentro de projeto Wizz — você DELEGA, nunca executa
 
-Avalie a **Área**: quantas áreas o pedido toca (design, dev, copy, seo, growth, ads, qa, memória)? Se for só 1, avalie também os **3 fatores restantes** (sinal compartilhado com `wizz-maestro` e `wizz-quick-dev`):
+Avalie a **Área**: quantas áreas o pedido toca? A lista canônica de áreas é o próprio `skills-registry.yaml` (`areas:`; hoje: designer, copy, seo, growth, social, ads, architect, qa, analyst, dev, pm, tech-writer, ux-designer, memoria). Para a contagem da regra abaixo, os 3 exemplos citados com frequência são design, dev e memória. Se for só 1, avalie também os **3 fatores restantes** (sinal compartilhado com `wizz-maestro` e `wizz-quick-dev`):
 
 1. **Passos**: pontual ou multi-passo?
 2. **Planejamento**: direto, ou precisa planejar antes?
 3. **Artefato + memória**: gera entregável que merece registro no cerebro?
 
-**Regra de dispatch:** SE 2+ áreas → `wizz-maestro`, sempre. SENÃO conte os 3 fatores restantes (multi-passo, precisa planejar, gera artefato memorável); 2+ fatores → `wizz-maestro`.
+**Regra de dispatch:** SE 2+ áreas → `wizz-maestro`, sempre. SENÃO conte os 3 fatores restantes (multi-passo, precisa planejar, gera artefato memorável); 2+ fatores → `wizz-maestro`. A cláusula de área decide sozinha, sem somar com mais nada.
 
 - **2+ áreas → `wizz-maestro`, sempre.** Ele é o Gerente: coordena agentes entre áreas, monta a sequência, mantém o dever de memória. Invoque via `Skill` e **pare aqui**.
 - **1 área e 0–1 dos 3 fatores → o AGENTE daquela área.** Ache a área no `skills-registry.yaml` e invoque o `agent:` do bloco (ex: `designer → wizz-designer`, `seo → wizz-seo`, dev pontual → `wizz-quick-dev`). **Pare aqui**: o agente puxa as skills/clis/mcps. Você **não** dispara skills soltas.
@@ -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

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