wizz-method 1.19.0 → 2.1.0

package/src/scripts/resolve_customization.py

@@ -46,6 +46,20 @@ Optional `include` (aditivo, opcional):
   include files warn to stderr and are skipped (fail-open, matching the
   rest of this resolver); they never abort resolution. A toml with no
   `include` key resolves exactly as before this feature existed.
+
+  `_shared/` fallback: after `wizz install` the skill directory is moved
+  out of `_wizz/` into the IDE folder (`.claude/skills/<skill>/`), so a
+  shipped `include = ["../../_shared/x.md"]` no longer resolves. When the
+  base-relative path is missing AND the include mentions `_shared/`, the
+  segment after the LAST `_shared/` is looked up under
+  `<project-root>/_wizz/<module>/_shared/` for every module that has one,
+  modules sorted by name, first hit wins.
+
+  Containment: when a project root is known, an include whose base-relative
+  path escapes that root (`../../../../outside.md`) is refused with a warning
+  before it is read. The `_shared/` fallback candidates live under
+  `<project-root>/_wizz/` by construction, so they always pass. A standalone
+  skill with no resolvable project root keeps the unrestricted behaviour.
 """
 
 import argparse
@@ -67,6 +81,8 @@ except ImportError:
 
 _MISSING = object()
 _KEYED_MERGE_FIELDS = ("code", "id")
+_WIZZ_FOLDER_NAME = "_wizz"
+_SHARED_DIR_NAME = "_shared"
 
 
 def find_project_root(start: Path):
@@ -114,19 +130,90 @@ _INCLUDE_TARGET_FIELD = "activation_steps_append"
 
 def _read_include_file(path: Path):
     """Read an include file's raw text. Returns None (and warns to stderr)
-    when the file is missing or unreadable, so a broken/renamed include
-    never aborts resolution — same fail-open philosophy as the optional
-    team/user layers above."""
-    if not path.is_file():
-        sys.stderr.write(f"warning: include not found, skipping: {path}\n")
-        return None
+    when the file is unreadable, so a broken include never aborts
+    resolution — same fail-open philosophy as the optional team/user layers
+    above. Existence (and the `_shared/` fallback) is `_find_include_file`'s
+    job."""
     try:
         return path.read_text(encoding="utf-8")
     except OSError as error:
-        sys.stderr.write(f"warning: failed to read include {path}: {error}\n")
+        sys.stderr.write(f"warning: include not readable, skipping: {path}: {error}\n")
         return None
 
 
+def _shared_fallback_candidates(rel_path: str, project_root):
+    """Absolute candidates for an include whose base-relative path is missing.
+
+    The verbatim install pipeline moves each skill directory OUT of `_wizz/`
+    into the IDE folder (`.claude/skills/<skill>/customize.toml`) while the
+    file keeps its shipped `include = ["../../_shared/x.md"]`. From there that
+    resolves to `.claude/_shared/x.md`, which does not exist, and every
+    included paragraph was dropped silently. The real shared files live at
+    `<project-root>/_wizz/<module>/_shared/`. So: take the segment after the
+    LAST `_shared/` in the include and look for it under every module directly
+    under `_wizz/` that has a `_shared/` folder, modules sorted by name (first
+    hit wins upstream). Nothing else is guessed: an include without `_shared/`
+    gets no fallback. Mirror of `sharedFallbackCandidates` in
+    tools/installer/core/resolved-includes.js."""
+    if project_root is None or not isinstance(rel_path, str):
+        return []
+    posix = rel_path.replace("\\", "/")
+    marker = _SHARED_DIR_NAME + "/"
+    index = posix.rfind(marker)
+    if index == -1:
+        return []
+    segment = posix[index + len(marker):]
+    parts = segment.split("/")
+    if not segment or any(part in ("", "..", ".") for part in parts):
+        return []
+
+    wizz_root = project_root / _WIZZ_FOLDER_NAME
+    try:
+        modules = sorted(entry.name for entry in wizz_root.iterdir() if entry.is_dir())
+    except OSError:
+        return []
+    candidates = []
+    for name in modules:
+        shared_dir = wizz_root / name / _SHARED_DIR_NAME
+        if not shared_dir.is_dir():
+            continue
+        candidates.append(shared_dir.joinpath(*parts))
+    return candidates
+
+
+def _is_outside_project_root(base_dir: Path, rel_path: str, project_root):
+    """True when the base-relative include escapes the project root.
+
+    Hardening (2026-09-11): a customize.toml must not pull arbitrary files
+    from the user's home or from a sibling checkout into an agent's
+    activation steps, so `include = ["../../../../outside.md"]` is refused
+    before it is ever read. The `_shared/` fallback candidates are built
+    under `<project-root>/_wizz/` by construction and always pass. When no
+    project root is resolvable (standalone skill) there is nothing to be
+    outside of and the old unrestricted behaviour stands. Mirror of
+    `isOutsideProjectRoot` in tools/installer/core/resolved-includes.js."""
+    if project_root is None:
+        return False
+    primary = (base_dir / rel_path).resolve()
+    try:
+        primary.relative_to(Path(project_root).resolve())
+    except ValueError:
+        return True
+    return False
+
+
+def _find_include_file(base_dir: Path, rel_path: str, project_root):
+    """Absolute path the include actually points at, or None. Base-relative
+    first, then the `_shared/` fallback above."""
+    primary = (base_dir / rel_path).resolve()
+    if primary.is_file():
+        return primary
+    for candidate in _shared_fallback_candidates(rel_path, project_root):
+        if candidate.is_file():
+            return candidate
+    return None
+
+
 def _split_include_paragraphs(text: str):
     """Split an included markdown file into instruction strings.
 
@@ -144,7 +231,7 @@ def _split_include_paragraphs(text: str):
     return paragraphs
 
 
-def resolve_includes(data, base_dir: Path):
+def resolve_includes(data, base_dir: Path, project_root=None, skill_name: str = ""):
     """Expand `include = [...]` keys found in any table of `data`.
 
     Purely additive: a table without `include` comes back unchanged. When
@@ -163,7 +250,22 @@ def resolve_includes(data, base_dir: Path):
             if not isinstance(rel_path, str):
                 sys.stderr.write(f"warning: include entries must be strings, got: {rel_path!r}\n")
                 continue
-            text = _read_include_file((base_dir / rel_path).resolve())
+            if _is_outside_project_root(base_dir, rel_path, project_root):
+                sys.stderr.write(
+                    f'warning: include outside the project root, skipping: "{rel_path}" '
+                    f"(skill: {skill_name or '?'})\n"
+                )
+                continue
+            target = _find_include_file(base_dir, rel_path, project_root)
+            if target is None:
+                primary = (base_dir / rel_path).resolve()
+                sys.stderr.write(
+                    f'warning: include not found, skipping: "{rel_path}" '
+                    f"(skill: {skill_name or '?'}; tried {primary} and every "
+                    f"{_WIZZ_FOLDER_NAME}/*/{_SHARED_DIR_NAME}/)\n"
+                )
+                continue
+            text = _read_include_file(target)
             if text is not None:
                 included_paragraphs.extend(_split_include_paragraphs(text))
     elif "include" in data:
@@ -173,7 +275,9 @@ def resolve_includes(data, base_dir: Path):
     for key, value in data.items():
         if key == "include":
             continue
-        result[key] = resolve_includes(value, base_dir) if isinstance(value, dict) else value
+        result[key] = (
+            resolve_includes(value, base_dir, project_root, skill_name) if isinstance(value, dict) else value
+        )
 
     if included_paragraphs:
         existing = result.get(_INCLUDE_TARGET_FIELD, [])
@@ -294,20 +398,25 @@ def main():
     skill_name = skill_dir.name
     defaults_path = skill_dir / "customize.toml"
 
-    defaults = resolve_includes(load_toml(defaults_path, required=True), defaults_path.parent)
-
     # Prefer the project that contains this skill. Only fall back to cwd if
     # the skill isn't inside a recognizable project tree (unusual but possible
     # for standalone skills invoked directly). Using cwd first is unsafe when
     # an ancestor of cwd happens to have a stray _wizz/ from another project.
+    # Resolved BEFORE the base layer: the `_shared/` include fallback needs it.
     project_root = find_project_root(skill_dir) or find_project_root(Path.cwd())
 
+    defaults = resolve_includes(
+        load_toml(defaults_path, required=True), defaults_path.parent, project_root, skill_name
+    )
+
     team = {}
     user = {}
     if project_root:
-        custom_dir = project_root / "_wizz" / "custom"
-        team = resolve_includes(load_toml(custom_dir / f"{skill_name}.toml"), custom_dir)
-        user = resolve_includes(load_toml(custom_dir / f"{skill_name}.user.toml"), custom_dir)
+        custom_dir = project_root / _WIZZ_FOLDER_NAME / "custom"
+        team = resolve_includes(load_toml(custom_dir / f"{skill_name}.toml"), custom_dir, project_root, skill_name)
+        user = resolve_includes(
+            load_toml(custom_dir / f"{skill_name}.user.toml"), custom_dir, project_root, skill_name
+        )
 
     merged = deep_merge(defaults, team)
     merged = deep_merge(merged, user)

package/src/skills-lib/_shared/complexity-signal.md

@@ -0,0 +1,14 @@
+# Sinal de complexidade (fonte única)
+#
+# Lido por wizz-router (SKILL.md), wizz-maestro (SKILL.md) e wizz-quick-dev
+# (SKILL.md) como a FONTE CANÔNICA do parágrafo de regra abaixo. As SKILL.md
+# não fazem include automático dele (skills são pastas autocontidas copiadas
+# verbatim), então editar aqui NÃO propaga sozinho — quem editar este
+# parágrafo precisa replicar a mudança manualmente nas 3 SKILL.md (PT-BR
+# idêntico (após a normalização do teste: backticks, prefixo wizz-, "(você)") em wizz-router/wizz-maestro; tradução em inglês em
+# wizz-quick-dev). `test/test-dispatch-rule-consistency.js` compara o texto
+# do bloco (não só os números) contra as 3 cópias e falha em qualquer
+# divergência de wording, não só de limiar.
+# ---
+
+Regra de dispatch: SE 2+ áreas → maestro, sempre. SENÃO conte os 3 fatores restantes (multi-passo, precisa planejar, gera artefato memorável); 2+ fatores → maestro. A cláusula de área decide sozinha, sem somar com mais nada.

package/src/skills-lib/find-skills/SKILL.md

@@ -166,7 +166,7 @@ claude mcp add context7 -- npx -y @upstash/context7-mcp@3.2.2
 claude mcp add exa -e EXA_API_KEY=$EXA_API_KEY -- npx -y exa-mcp-server@3.2.1
 claude mcp add supabase -e SUPABASE_ACCESS_TOKEN=$SUPABASE_ACCESS_TOKEN -- npx -y @supabase/mcp-server-supabase@0.8.2 --read-only
 ```
-Versões acima são as pinadas hoje em `skills-registry.yaml` — confira lá antes de copiar, pode ter mudado. Não sugira o MCP do Playwright: browser é sempre via CLI `agent-browser` neste framework, nunca Playwright.
+Versões acima são as pinadas hoje em `skills-registry.yaml` — confira lá antes de copiar, pode ter mudado. Não sugira o MCP do Playwright: browser é sempre via CLI `wizz-agent-browser` neste framework, nunca Playwright.
 
 Ou edite o `.mcp.json` do projeto (merge aditivo, nunca apague servers existentes):
 
@@ -180,4 +180,4 @@ NUNCA escreva token real em arquivo commitado. Use variável de ambiente (`-e VA
 
 ### Quando não há MCP pronto
 
-Diga que não existe MCP conhecido pra isso e ofereça resolver com as ferramentas atuais (ex: `agent-browser` no lugar do MCP playwright, ou chamadas diretas de API).
+Diga que não existe MCP conhecido pra isso e ofereça resolver com as ferramentas atuais (ex: `wizz-agent-browser` no lugar do MCP playwright, ou chamadas diretas de API).

package/src/skills-lib/pesquisa-de-publico-do-piva/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: pesquisa-de-publico-do-piva
-description: Gera arsenal completo de pesquisa de público para oferta de infoproduto e tráfego pago a partir de uma oferta (.docx/.md/.txt/.pdf). Produz seis relatórios encadeados — VoC, Perfil Psicográfico Schwartz, Níveis de Consciência, Trend Report, Matriz de Ângulos e Léxico — compilados em dashboard HTML navegável por abas. Use quando o usuário enviar uma oferta e pedir pesquisa de público, VoC, voz do cliente, matriz de ângulos, léxico do público, dores de persona ou arsenal de copy para tráfego direto. NÃO use para pesquisa técnica de libs/código (use context7), pesquisa de mercado B2B ampla (use deep-research) nem pesquisa visual de UI (use premium-landing-ui-researcher). Metodologia de @soupiva.
+description: Gera arsenal completo de pesquisa de público para oferta de infoproduto e tráfego pago a partir de uma oferta (.docx/.md/.txt/.pdf). Produz seis relatórios encadeados — VoC, Perfil Psicográfico Schwartz, Níveis de Consciência, Trend Report, Matriz de Ângulos e Léxico — compilados em dashboard HTML navegável por abas. Use quando o usuário enviar uma oferta e pedir pesquisa de público, VoC, voz do cliente, matriz de ângulos, léxico do público, dores de persona ou arsenal de copy para tráfego direto. NÃO use para pesquisa técnica de libs/código (use context7), pesquisa de mercado B2B ampla (use deep-research) nem pesquisa visual de UI (use wizz-premium-landing-ui-researcher). Metodologia de @soupiva.
 ---
 
 # Pesquisa de Público do Piva

package/src/skills-lib/references/premium-agency-rules.md

@@ -1,8 +1,8 @@
 # Premium Agency Design Rules (referência)
 
-> **O que é isto:** documento de referência (não é uma skill acionável). Reúne as regras de design "$150k agency-tier" que antes viviam na skill `taste-soft` / `high-end-visual-design`. Foi rebaixado a referência porque é redundante com `impeccable` como skill invocável — o conteúdo continua útil como *fonte de regras*, não como ponto de entrada.
+> **O que é isto:** documento de referência (não é uma skill acionável). Reúne as regras de design "$150k agency-tier" que antes viviam na skill `taste-soft` / `high-end-visual-design`. Foi rebaixado a referência porque é redundante com `wizz-impeccable` como skill invocável — o conteúdo continua útil como *fonte de regras*, não como ponto de entrada.
 >
-> **Quem usa:** `impeccable` e `huashu-design` importam estas regras quando entram em modo "high-end / Awwwards-tier". O agente `wizz-designer` aponta pra cá quando o pedido exige acabamento premium.
+> **Quem usa:** `wizz-impeccable` e `wizz-huashu-design` importam estas regras quando entram em modo "high-end / Awwwards-tier". O agente `wizz-designer` aponta pra cá quando o pedido exige acabamento premium.
 
 ## 1. Diretriz central
 - **Persona:** Vanguard UI Architect.

package/src/skills-lib/security-audit-pentest/SKILL.md

@@ -5,9 +5,9 @@ description: >
   payload concreto por achado). Use quando o pedido for auditar/pentestar um app inteiro, revisar segurança
   antes de release, "auditoria de segurança", "pentest", "encontrar vulnerabilidades", ou rodar uma varredura
   completa de mass assignment, IDOR/RLS, injeção, rate limit/abuso por volume, e vazamento por resposta.
-  Diferente de web-security/auth-and-secrets (que corrigem): esta CAÇA, com prova de exploração, e no fim funde
+  Diferente de wizz-web-security/wizz-auth-and-secrets (que corrigem): esta CAÇA, com prova de exploração, e no fim funde
   os achados num plano priorizado ("as três de hoje"). Para corrigir uma falha isolada, use as skills
-  web-security e auth-and-secrets.
+  wizz-web-security e wizz-auth-and-secrets.
 ---
 
 # Security Audit (Pentest adversarial)
@@ -50,4 +50,4 @@ Gravidade: CRÍTICO, ALTO, MÉDIO.
 ## Relação com as outras skills de segurança
 
 - **Esta skill CAÇA** (encontra + prova). Saída = lista de achados + plano.
-- **`web-security` e `auth-and-secrets` CORRIGEM** (padrão certo + exemplo de código). Ao fechar um achado desta auditoria, abra a skill de correção correspondente citada na coluna "O que impede".
+- **`wizz-web-security` e `wizz-auth-and-secrets` CORRIGEM** (padrão certo + exemplo de código). Ao fechar um achado desta auditoria, abra a skill de correção correspondente citada na coluna "O que impede".

package/src/skills-lib/site-launch-kit/SKILL.md

@@ -5,7 +5,7 @@ description: "Checklist operacional de pré-lançamento de site em 15 rodadas co
 
 # Site Launch Kit · Revisão de Pré-Lançamento
 
-15 rodadas corretivas para rodar **depois que o site está construído e antes do deploy**. Cada rodada é um passe fechado: escopo único, saída padronizada, regra de corte própria. Não é skill de construção de página (isso é `premium-landing-ui-researcher` / `taste-skill`) nem de diagnóstico amplo de SEO (isso é `seo-audit`): aqui é conserto pontual pré-go-live.
+15 rodadas corretivas para rodar **depois que o site está construído e antes do deploy**. Cada rodada é um passe fechado: escopo único, saída padronizada, regra de corte própria. Não é skill de construção de página (isso é `wizz-premium-landing-ui-researcher` / `wizz-taste-skill`) nem de diagnóstico amplo de SEO (isso é `wizz-seo-audit`): aqui é conserto pontual pré-go-live.
 
 ## Contrato comum (vale para TODAS as rodadas)
 
@@ -46,7 +46,7 @@ description: "Checklist operacional de pré-lançamento de site em 15 rodadas co
 
 ## O que esta skill NÃO faz
 
-- Não redesenha layout, paleta ou conteúdo de seções (use `taste-skill` / `impeccable`).
-- Não cria a página do zero (use `premium-landing-ui-researcher`).
-- Não faz diagnóstico amplo de ranking/tráfego (use `seo-audit`).
-- Não escreve copy de venda nova (use `copywriting`); aqui só se ajusta rótulo e microcopy de atrito com material que já existe no site.
+- Não redesenha layout, paleta ou conteúdo de seções (use `wizz-taste-skill` / `wizz-impeccable`).
+- Não cria a página do zero (use `wizz-premium-landing-ui-researcher`).
+- Não faz diagnóstico amplo de ranking/tráfego (use `wizz-seo-audit`).
+- Não escreve copy de venda nova (use `wizz-copywriting`); aqui só se ajusta rótulo e microcopy de atrito com material que já existe no site.

package/src/skills-lib/{ab-test-setup → wizz-ab-test-setup}/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: ab-test-setup
-description: When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," or "how long should I run this test." Use this whenever someone is comparing two approaches and wants to measure which performs better. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.
+name: wizz-ab-test-setup
+description: When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," or "how long should I run this test." Use this whenever someone is comparing two approaches and wants to measure which performs better. For tracking implementation, see wizz-analytics-tracking. For page-level conversion optimization, see wizz-page-cro.
 metadata:
   version: 1.1.0
 ---
@@ -261,6 +261,6 @@ Document every test with:
 
 ## Related Skills
 
-- **page-cro**: For generating test ideas based on CRO principles
-- **analytics-tracking**: For setting up test measurement
-- **copywriting**: For creating variant copy
+- **wizz-page-cro**: For generating test ideas based on CRO principles
+- **wizz-analytics-tracking**: For setting up test measurement
+- **wizz-copywriting**: For creating variant copy

package/src/skills-lib/{ab-test-setup → wizz-ab-test-setup}/evals/evals.json

@@ -1,5 +1,5 @@
 {
-  "skill_name": "ab-test-setup",
+  "skill_name": "wizz-ab-test-setup",
   "evals": [
     {
       "id": 1,

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

@@ -1,6 +1,6 @@
 ---
-name: ad-creative
-description: "When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'ad performance optimization,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' or 'I need more ad variations.' Use this whenever someone needs to produce ad copy at scale or iterate on existing ads. For campaign strategy and targeting, see paid-ads. For landing page copy, see copywriting."
+name: wizz-ad-creative
+description: "When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'ad performance optimization,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' or 'I need more ad variations.' Use this whenever someone needs to produce ad copy at scale or iterate on existing ads. For campaign strategy and targeting, see wizz-paid-ads. For landing page copy, see wizz-copywriting."
 metadata:
   version: 1.1.0
 ---
@@ -355,8 +355,8 @@ node tools/clis/google-ads.js reports get --type ad_performance --date-range las
 
 ## Related Skills
 
-- **paid-ads**: For campaign strategy, targeting, budgets, and optimization
-- **copywriting**: For landing page copy (where ad traffic lands)
-- **ab-test-setup**: For structuring creative tests with statistical rigor
-- **marketing-psychology**: For psychological principles behind high-performing creative
-- **copy-editing**: For polishing ad copy before launch
+- **wizz-paid-ads**: For campaign strategy, targeting, budgets, and optimization
+- **wizz-copywriting**: For landing page copy (where ad traffic lands)
+- **wizz-ab-test-setup**: For structuring creative tests with statistical rigor
+- **wizz-marketing-psychology**: For psychological principles behind high-performing creative
+- **wizz-copy-editing**: For polishing ad copy before launch

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

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

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

@@ -1,5 +1,5 @@
 ---
-name: adversarial-reviewer
+name: wizz-adversarial-reviewer
 description: Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.
 ---
 

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

@@ -1,5 +1,5 @@
 ---
-name: agent-browser
+name: wizz-agent-browser
 description: Browser automation for testing and verification. Use when you need to interact with web UIs, verify visual changes, fill forms, or capture screenshots.
 ---
 

package/src/skills-lib/{ai-product-design → wizz-ai-product-design}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: ai-product-design
+name: wizz-ai-product-design
 description: >
   Design de produtos e agentes de IA: como o agente se comporta, como escrever o prompt/system prompt,
   guardrails e trust/safety, orquestração multi-agente e avaliação. Usar quando: criar ou melhorar um

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

@@ -1,6 +1,6 @@
 ---
-name: ai-seo
-description: "When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' or 'optimize for Claude/Gemini.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema-markup."
+name: wizz-ai-seo
+description: "When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' or 'optimize for Claude/Gemini.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see wizz-seo-audit. For structured data implementation, see wizz-schema-markup."
 metadata:
   version: 1.1.0
 ---
@@ -240,7 +240,7 @@ Structured data helps AI systems understand your content. Key schemas:
 | Reviews | `Review`, `AggregateRating` | Trust signals |
 | Organization | `Organization` | Entity recognition |
 
-Content with proper schema shows 30-40% higher AI visibility. For implementation, use the **schema-markup** skill.
+Content with proper schema shows 30-40% higher AI visibility. For implementation, use the **wizz-schema-markup** skill.
 
 ---
 
@@ -333,7 +333,7 @@ Monthly manual check:
 - Fair and balanced (AI penalizes obviously biased comparisons)
 - Specific criteria with ratings or scores
 - Updated pricing and feature data
-- Cite the competitor-alternatives skill for building these pages
+- Cite the wizz-competitor-alternatives skill for building these pages
 
 ### Documentation / Help Content
 
@@ -390,9 +390,9 @@ For implementation, see the [tools registry](../../tools/REGISTRY.md).
 
 ## Related Skills
 
-- **seo-audit**: For traditional technical and on-page SEO audits
-- **schema-markup**: For implementing structured data that helps AI understand your content
-- **content-strategy**: For planning what content to create
-- **competitor-alternatives**: For building comparison pages that get cited
-- **programmatic-seo**: For building SEO pages at scale
-- **copywriting**: For writing content that's both human-readable and AI-extractable
+- **wizz-seo-audit**: For traditional technical and on-page SEO audits
+- **wizz-schema-markup**: For implementing structured data that helps AI understand your content
+- **wizz-content-strategy**: For planning what content to create
+- **wizz-competitor-alternatives**: For building comparison pages that get cited
+- **wizz-programmatic-seo**: For building SEO pages at scale
+- **wizz-copywriting**: For writing content that's both human-readable and AI-extractable

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

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

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

@@ -1,5 +1,5 @@
 ---
-name: algorithmic-art
+name: wizz-algorithmic-art
 description: Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations. Use when the user asks for generative art, code art, p5.js sketches, flow fields, particle systems, or an interactive algorithmic-art artifact.
 license: Complete terms in LICENSE.txt
 ---

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

@@ -1,6 +1,6 @@
 ---
-name: analytics-tracking
-description: When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "attribution," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For A/B test measurement, see ab-test-setup.
+name: wizz-analytics-tracking
+description: When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "attribution," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For A/B test measurement, see wizz-ab-test-setup.
 metadata:
   version: 1.1.0
 ---
@@ -305,7 +305,7 @@ For implementation, see the [tools registry](../../tools/REGISTRY.md). Key analy
 
 ## Related Skills
 
-- **ab-test-setup**: For experiment tracking
-- **seo-audit**: For organic traffic analysis
-- **page-cro**: For conversion optimization (uses this data)
-- **revops**: For pipeline metrics, CRM tracking, and revenue attribution
+- **wizz-ab-test-setup**: For experiment tracking
+- **wizz-seo-audit**: For organic traffic analysis
+- **wizz-page-cro**: For conversion optimization (uses this data)
+- **wizz-revops**: For pipeline metrics, CRM tracking, and revenue attribution

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

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

package/src/skills-lib/{analytics-tracking → wizz-analytics-tracking}/references/utm-taxonomy.md

@@ -2,7 +2,7 @@
 
 A UTM scheme is only worth what its weakest tag is worth. One free-text `utm_source` per person and the channel report is fiction within a month. This reference is the governance layer: the allowed values, the naming standard, and who owns it.
 
-For auditing a direct-response funnel (pixel, CAPI, checkout passthrough, test purchase per route), use the `tracking-audit` skill instead. This file defines the taxonomy; that skill proves it is installed correctly.
+For auditing a direct-response funnel (pixel, CAPI, checkout passthrough, test purchase per route), use the `wizz-tracking-audit` skill instead. This file defines the taxonomy; that skill proves it is installed correctly.
 
 ## The one rule
 

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

@@ -1,5 +1,5 @@
 ---
-name: animate
+name: wizz-animate
 description: Animation patterns and best practices for Next.js/React applications. Use this skill when implementing animations, transitions, hover effects, page transitions, modals, or any motion in React components. Based on Emil Kowalski's "Animations on the Web" course. Use when the user asks to add hover effects, transitions, page transitions, modals, or any motion to a Next.js or React component.
 ---
 

package/src/skills-lib/{animate → wizz-animate}/references/framer-motion.md

@@ -32,7 +32,7 @@ import { motion } from "framer-motion"
 | Prop | Description |
 |------|-------------|
 | `initial` | Starting state (or `false` to disable) |
-| `animate` | Target state |
+| `wizz-animate` | Target state |
 | `exit` | Exit state (requires AnimatePresence) |
 | `transition` | Animation configuration |
 | `whileHover` | State while hovered |

package/src/skills-lib/{auth-and-secrets → wizz-auth-and-secrets}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: auth-and-secrets
+name: wizz-auth-and-secrets
 description: >
   Segurança de autenticação e gestão de secrets. Usar quando: implementar auth, lidar com JWT/OAuth/SSO,
   token no header vs URL, revogação de token no logout, enumeração de usuário/mensagem genérica,
@@ -32,7 +32,7 @@ Evita que um atacante descubra quais e-mails existem na base (login, signup, res
 - Resposta idêntica para e-mail existente e inexistente: "Se o e-mail existir, enviamos um link"
 - No login use mensagem genérica ("credenciais inválidas"), nunca "e-mail não cadastrado" vs "senha incorreta"
 - Responda em **tempo constante**: rode o hash da senha mesmo quando o usuário não existe (senão o tempo de resposta denuncia quem existe)
-- Reforce com rate limit por IP **e** por conta (ver web-security) para barrar varredura de e-mails
+- Reforce com rate limit por IP **e** por conta (ver wizz-web-security) para barrar varredura de e-mails
 
 ### OAuth / SSO
 - Use biblioteca estabelecida, não implemente o flow manualmente

package/src/skills-lib/{caching-and-queues → wizz-caching-and-queues}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: caching-and-queues
+name: wizz-caching-and-queues
 description: Caching e filas assíncronas — Redis cache-aside/write-through, TTL, rate limiting, BullMQ, SQS, Kafka. Use quando o pedido envolver cache, sessões, filas de job, processamento assíncrono.
 ---
 

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

@@ -1,5 +1,5 @@
 ---
-name: canvas-design
+name: wizz-canvas-design
 description: Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations. Use when the user asks for a poster, art piece, print design, or other static visual output as a .png or .pdf.
 license: Complete terms in LICENSE.txt
 ---

package/src/skills-lib/wizz-canvas-design/canvas-fonts/InstrumentSerif-OFL.txt

@@ -0,0 +1,93 @@
+Copyright 2022 The Instrument Serif Project Authors (https://github.com/Instrument/instrument-serif)
+
+This Font Software is licensed under the SIL Open Font License, Version 1.1.
+This license is copied below, and is also available with a FAQ at:
+https://openfontlicense.org
+
+
+-----------------------------------------------------------
+SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007
+-----------------------------------------------------------
+
+PREAMBLE
+The goals of the Open Font License (OFL) are to stimulate worldwide
+development of collaborative font projects, to support the font creation
+efforts of academic and linguistic communities, and to provide a free and
+open framework in which fonts may be shared and improved in partnership
+with others.
+
+The OFL allows the licensed fonts to be used, studied, modified and
+redistributed freely as long as they are not sold by themselves. The
+fonts, including any derivative works, can be bundled, embedded, 
+redistributed and/or sold with any software provided that any reserved
+names are not used by derivative works. The fonts and derivatives,
+however, cannot be released under any other type of license. The
+requirement for fonts to remain under this license does not apply
+to any document created using the fonts or their derivatives.
+
+DEFINITIONS
+"Font Software" refers to the set of files released by the Copyright
+Holder(s) under this license and clearly marked as such. This may
+include source files, build scripts and documentation.
+
+"Reserved Font Name" refers to any names specified as such after the
+copyright statement(s).
+
+"Original Version" refers to the collection of Font Software components as
+distributed by the Copyright Holder(s).
+
+"Modified Version" refers to any derivative made by adding to, deleting,
+or substituting -- in part or in whole -- any of the components of the
+Original Version, by changing formats or by porting the Font Software to a
+new environment.
+
+"Author" refers to any designer, engineer, programmer, technical
+writer or other person who contributed to the Font Software.
+
+PERMISSION & CONDITIONS
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of the Font Software, to use, study, copy, merge, embed, modify,
+redistribute, and sell modified and unmodified copies of the Font
+Software, subject to the following conditions:
+
+1) Neither the Font Software nor any of its individual components,
+in Original or Modified Versions, may be sold by itself.
+
+2) Original or Modified Versions of the Font Software may be bundled,
+redistributed and/or sold with any software, provided that each copy
+contains the above copyright notice and this license. These can be
+included either as stand-alone text files, human-readable headers or
+in the appropriate machine-readable metadata fields within text or
+binary files as long as those fields can be easily viewed by the user.
+
+3) No Modified Version of the Font Software may use the Reserved Font
+Name(s) unless explicit written permission is granted by the corresponding
+Copyright Holder. This restriction only applies to the primary font name as
+presented to the users.
+
+4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
+Software shall not be used to promote, endorse or advertise any
+Modified Version, except to acknowledge the contribution(s) of the
+Copyright Holder(s) and the Author(s) or with their explicit written
+permission.
+
+5) The Font Software, modified or unmodified, in part or in whole,
+must be distributed entirely under this license, and must not be
+distributed under any other license. The requirement for fonts to
+remain under this license does not apply to any document created
+using the Font Software.
+
+TERMINATION
+This license becomes null and void if any of the above conditions are
+not met.
+
+DISCLAIMER
+THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
+OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
+COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
+DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
+OTHER DEALINGS IN THE FONT SOFTWARE.