wizz-method 1.18.3 → 2.0.0

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/{churn-prevention → wizz-churn-prevention}/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: churn-prevention
-description: "When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers or wants to build systems to prevent it. For post-cancel win-back email sequences, see email-sequence. For in-app upgrade paywalls, see paywall-upgrade-cro."
+name: wizz-churn-prevention
+description: "When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers or wants to build systems to prevent it. For post-cancel win-back email sequences, see wizz-email-sequence. For in-app upgrade paywalls, see wizz-paywall-upgrade-cro."
 metadata:
   version: 1.1.0
 ---
@@ -252,7 +252,7 @@ Health Score = (
 | Trigger | Intervention |
 |---------|-------------|
 | Usage drop >50% for 2 weeks | "We noticed you haven't used [feature]. Need help?" email |
-| Approaching plan limit | Upgrade nudge (not a wall — paywall-upgrade-cro handles this) |
+| Approaching plan limit | Upgrade nudge (not a wall — wizz-paywall-upgrade-cro handles this) |
 | No login for 14 days | Re-engagement email with recent product updates |
 | NPS detractor (0-6) | Personal follow-up within 24 hours |
 | Support ticket unresolved >48h | Escalation + proactive status update |
@@ -360,7 +360,7 @@ Test one variable at a time:
 | Offer presentation (modal vs full page) | Full page gets more attention | Save rate |
 | Copy tone (empathetic vs direct) | Empathetic reduces friction | Save rate |
 
-**How to run cancel flow experiments:** Use the **ab-test-setup** skill to design statistically rigorous tests. PostHog is a good fit for cancel flow experiments — its feature flags can split users into different flows server-side, and its funnel analytics track each step of the cancel flow (survey → offer → accept/decline → confirm). See the [PostHog integration guide](../../tools/integrations/posthog.md) for setup.
+**How to run cancel flow experiments:** Use the **wizz-ab-test-setup** skill to design statistically rigorous tests. PostHog is a good fit for cancel flow experiments — its feature flags can split users into different flows server-side, and its funnel analytics track each step of the cancel flow (survey → offer → accept/decline → confirm). See the [PostHog integration guide](../../tools/integrations/posthog.md) for setup.
 
 ---
 
@@ -416,9 +416,9 @@ For implementation, see the [tools registry](../../tools/REGISTRY.md).
 
 ## Related Skills
 
-- **email-sequence**: For win-back email sequences after cancellation
-- **paywall-upgrade-cro**: For in-app upgrade moments and trial expiration
-- **pricing-strategy**: For plan structure and annual discount strategy
-- **onboarding-cro**: For activation to prevent early churn
-- **analytics-tracking**: For setting up churn signal events
-- **ab-test-setup**: For testing cancel flow variations with statistical rigor
+- **wizz-email-sequence**: For win-back email sequences after cancellation
+- **wizz-paywall-upgrade-cro**: For in-app upgrade moments and trial expiration
+- **wizz-pricing-strategy**: For plan structure and annual discount strategy
+- **wizz-onboarding-cro**: For activation to prevent early churn
+- **wizz-analytics-tracking**: For setting up churn signal events
+- **wizz-ab-test-setup**: For testing cancel flow variations with statistical rigor

package/src/skills-lib/{churn-prevention → wizz-churn-prevention}/evals/evals.json

@@ -1,5 +1,5 @@
 {
-  "skill_name": "churn-prevention",
+  "skill_name": "wizz-churn-prevention",
   "evals": [
     {
       "id": 1,

package/src/skills-lib/{cloud-and-infra → wizz-cloud-and-infra}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: cloud-and-infra
+name: wizz-cloud-and-infra
 description: Otimização de custo de cloud — right-sizing, spot instances, reserved instances, S3 lifecycle, auto-scaling, auditoria de custo AWS/GCP. Use quando o pedido envolver redução de custo de infra, cloud spend, billing de cloud.
 ---
 

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

@@ -1,6 +1,6 @@
 ---
-name: cold-email
-description: Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions "cold outreach," "prospecting email," "outbound email," "email to leads," "reach out to prospects," "sales email," "follow-up email sequence," "nobody's replying to my emails," or "how do I write a cold email." Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences. For warm/lifecycle email sequences, see email-sequence. For sales collateral beyond emails, see sales-enablement.
+name: wizz-cold-email
+description: Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions "cold outreach," "prospecting email," "outbound email," "email to leads," "reach out to prospects," "sales email," "follow-up email sequence," "nobody's replying to my emails," or "how do I write a cold email." Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences. For warm/lifecycle email sequences, see wizz-email-sequence. For sales collateral beyond emails, see wizz-sales-enablement.
 metadata:
   version: 1.1.0
 ---
@@ -151,8 +151,8 @@ Use this data to inform your writing — not as a checklist to satisfy.
 
 ## Related Skills
 
-- **copywriting**: For landing pages and web copy
-- **email-sequence**: For lifecycle/nurture email sequences (not cold outreach)
-- **social-content**: For LinkedIn and social posts
-- **product-marketing-context**: For establishing foundational positioning
-- **revops**: For lead scoring, routing, and pipeline management
+- **wizz-copywriting**: For landing pages and web copy
+- **wizz-email-sequence**: For lifecycle/nurture email sequences (not cold outreach)
+- **wizz-social-content**: For LinkedIn and social posts
+- **wizz-product-marketing-context**: For establishing foundational positioning
+- **wizz-revops**: For lead scoring, routing, and pipeline management

package/src/skills-lib/{cold-email → wizz-cold-email}/evals/evals.json

@@ -1,5 +1,5 @@
 {
-  "skill_name": "cold-email",
+  "skill_name": "wizz-cold-email",
   "evals": [
     {
       "id": 1,

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

@@ -1,6 +1,6 @@
 ---
-name: competitor-alternatives
-description: "When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'battle card,' or 'competitor teardown.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For sales-specific competitor docs, see sales-enablement."
+name: wizz-competitor-alternatives
+description: "When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'battle card,' or 'competitor teardown.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For sales-specific competitor docs, see wizz-sales-enablement."
 metadata:
   version: 1.1.0
 ---
@@ -249,8 +249,8 @@ Recommended pages to create with priority order based on search volume.
 
 ## Related Skills
 
-- **programmatic-seo**: For building competitor pages at scale
-- **copywriting**: For writing compelling comparison copy
-- **seo-audit**: For optimizing competitor pages
-- **schema-markup**: For FAQ and comparison schema
-- **sales-enablement**: For internal sales collateral, decks, and objection docs
+- **wizz-programmatic-seo**: For building competitor pages at scale
+- **wizz-copywriting**: For writing compelling comparison copy
+- **wizz-seo-audit**: For optimizing competitor pages
+- **wizz-schema-markup**: For FAQ and comparison schema
+- **wizz-sales-enablement**: For internal sales collateral, decks, and objection docs

package/src/skills-lib/{competitor-alternatives → wizz-competitor-alternatives}/evals/evals.json

@@ -1,5 +1,5 @@
 {
-  "skill_name": "competitor-alternatives",
+  "skill_name": "wizz-competitor-alternatives",
   "evals": [
     {
       "id": 1,

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

@@ -1,6 +1,6 @@
 ---
-name: content-strategy
-description: When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social-content.
+name: wizz-content-strategy
+description: When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see wizz-copywriting. For SEO-specific audits, see wizz-seo-audit. For social media content specifically, see wizz-social-content.
 metadata:
   version: 1.1.0
 ---
@@ -46,10 +46,10 @@ Every piece of content must be searchable, shareable, or both. Prioritize in tha
 
 ## Related Skills
 
-- **copywriting**: For writing individual content pieces
-- **seo-audit**: For technical SEO and on-page optimization
-- **ai-seo**: For optimizing content for AI search engines and getting cited by LLMs
-- **programmatic-seo**: For scaled content generation
-- **site-architecture**: For page hierarchy, navigation design, and URL structure
-- **email-sequence**: For email-based content
-- **social-content**: For social media content
+- **wizz-copywriting**: For writing individual content pieces
+- **wizz-seo-audit**: For technical SEO and on-page optimization
+- **wizz-ai-seo**: For optimizing content for AI search engines and getting cited by LLMs
+- **wizz-programmatic-seo**: For scaled content generation
+- **wizz-site-architecture**: For page hierarchy, navigation design, and URL structure
+- **wizz-email-sequence**: For email-based content
+- **wizz-social-content**: For social media content

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

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

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

@@ -1,6 +1,6 @@
 ---
-name: copy-editing
-description: "When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' 'copy sweep,' 'tighten this up,' 'this reads awkwardly,' 'clean up this text,' 'too wordy,' or 'sharpen the messaging.' Use this when the user already has copy and wants it improved rather than rewritten from scratch. For writing new copy, see copywriting."
+name: wizz-copy-editing
+description: "When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' 'copy sweep,' 'tighten this up,' 'this reads awkwardly,' 'clean up this text,' 'too wordy,' or 'sharpen the messaging.' Use this when the user already has copy and wants it improved rather than rewritten from scratch. For writing new copy, see wizz-copywriting."
 metadata:
   version: 1.1.0
 ---
@@ -430,10 +430,10 @@ This iterative process ensures each edit doesn't create new problems while respe
 
 ## Related Skills
 
-- **copywriting**: For writing new copy from scratch (use this skill to edit after your first draft is complete)
-- **page-cro**: For broader page optimization beyond copy
-- **marketing-psychology**: For understanding why certain edits improve conversion
-- **ab-test-setup**: For testing copy variations
+- **wizz-copywriting**: For writing new copy from scratch (use this skill to edit after your first draft is complete)
+- **wizz-page-cro**: For broader page optimization beyond copy
+- **wizz-marketing-psychology**: For understanding why certain edits improve conversion
+- **wizz-ab-test-setup**: For testing copy variations
 
 ---
 
@@ -441,7 +441,7 @@ This iterative process ensures each edit doesn't create new problems while respe
 
 | Task | Skill to Use |
 |------|--------------|
-| Writing new page copy from scratch | copywriting |
-| Reviewing and improving existing copy | copy-editing (this skill) |
-| Editing copy you just wrote | copy-editing (this skill) |
-| Structural or strategic page changes | page-cro |
+| Writing new page copy from scratch | wizz-copywriting |
+| Reviewing and improving existing copy | wizz-copy-editing (this skill) |
+| Editing copy you just wrote | wizz-copy-editing (this skill) |
+| Structural or strategic page changes | wizz-page-cro |

package/src/skills-lib/{copy-editing → wizz-copy-editing}/evals/evals.json

@@ -1,5 +1,5 @@
 {
-  "skill_name": "copy-editing",
+  "skill_name": "wizz-copy-editing",
   "evals": [
     {
       "id": 1,

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

@@ -1,6 +1,6 @@
 ---
-name: copywriting
-description: When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value proposition," "tagline," "subheadline," "hero section copy," "above the fold," "this copy is weak," "make this more compelling," or "help me describe my product." Use this whenever someone is working on website text that needs to persuade or convert. For email copy, see email-sequence. For popup copy, see popup-cro. For editing existing copy, see copy-editing.
+name: wizz-copywriting
+description: When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value proposition," "tagline," "subheadline," "hero section copy," "above the fold," "this copy is weak," "make this more compelling," or "help me describe my product." Use this whenever someone is working on website text that needs to persuade or convert. For email copy, see wizz-email-sequence. For popup copy, see wizz-popup-cro. For editing existing copy, see wizz-copy-editing.
 metadata:
   version: 1.1.0
 ---
@@ -77,7 +77,7 @@ Each section should advance one argument. Build a logical flow down the page.
 - Exclamation points? (remove them)
 - Marketing buzzwords without substance?
 
-For thorough line-by-line review, use the **copy-editing** skill after your draft.
+For thorough line-by-line review, use the **wizz-copy-editing** skill after your draft.
 
 ---
 
@@ -245,8 +245,8 @@ For headlines and CTAs, provide 2-3 options:
 
 ## Related Skills
 
-- **copy-editing**: For polishing existing copy (use after your draft)
-- **page-cro**: If page structure/strategy needs work, not just copy
-- **email-sequence**: For email copywriting
-- **popup-cro**: For popup and modal copy
-- **ab-test-setup**: To test copy variations
+- **wizz-copy-editing**: For polishing existing copy (use after your draft)
+- **wizz-page-cro**: If page structure/strategy needs work, not just copy
+- **wizz-email-sequence**: For email copywriting
+- **wizz-popup-cro**: For popup and modal copy
+- **wizz-ab-test-setup**: To test copy variations

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

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

package/src/skills-lib/{database-and-deps → wizz-database-and-deps}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: database-and-deps
+name: wizz-database-and-deps
 description: >
   Segurança de banco de dados e dependências. Usar quando: revisar queries de banco, checar SQL injection,
   auditar permissões de banco, criptografar PII, revisar pacotes vulneráveis, configurar Dependabot/Renovate,

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

@@ -1,5 +1,5 @@
 ---
-name: database-scaling
+name: wizz-database-scaling
 description: Escalar banco de dados — sharding, réplicas de leitura, connection pooling, índices, N+1, particionamento. Use quando o pedido envolver banco lento, performance de queries, escala de dados.
 ---
 

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

@@ -1,5 +1,5 @@
 ---
-name: decision-maker
+name: wizz-decision-maker
 description: Walk a founder or designer through building a sharp visual brief for a website project, then output four ready-to-use prompts for downstream AI tools (Copywriter, 3D/Illustration, Design, Developer) plus GitHub + Vercel launch instructions. Use this skill whenever a user wants to brief a website, build a landing page with AI, create a visual direction, define a brand brief, or says anything like "I want to build a site with Claude," "help me write a brief," "I want to make a premium website," "guide me through a website project," or starts a slash command like `/start`, `/decision`, `/references`, `/extract`, or `/output`. Trigger even when the user just describes a project they want to build without explicitly asking for a brief — the skill turns vague intent into a structured, executable visual direction. Use when the user wants to brief a website, define a visual direction, or plan a landing page before building it with AI.
 ---
 

package/src/skills-lib/{decision-maker → wizz-decision-maker}/references/wizz-method-handoff.md

@@ -9,14 +9,14 @@ If this skill is running inside a Wizz Method project (a `_wizz/` folder exists,
 | Brief section | Hand off to | Via |
 |---|---|---|
 | Section 1 — Copywriter | `wizz-copy` | the `Skill` tool, passing the copy prompt as the brief |
-| Section 2 — 3D / Illustration | `wizz-designer` | routes onward to `motion-3d-director` |
-| Section 3 — Design (layout spec) | `wizz-designer` | routes onward to `ui-ux-pro-max` / `premium-landing-ui-researcher` |
+| Section 2 — 3D / Illustration | `wizz-designer` | routes onward to `wizz-motion-3d-director` |
+| Section 3 — Design (layout spec) | `wizz-designer` | routes onward to `wizz-ui-ux-pro-max` / `wizz-premium-landing-ui-researcher` |
 | Section 4 — Developer | `wizz-agent-dev` (`wizz-quick-dev` for small builds) | builds from the dev prompt + assets |
 
 Recommended close inside the method:
 > Brief locked. Want me to dispatch it? I can send the copy to **wizz-copy**, the visual direction to **wizz-designer**, and the build to **wizz-agent-dev** — or **wizz-quick-dev** for a small build — in that order. Or run the launch guide yourself.
 >
-> For the engineering setup (folder structure, stack, patterns, dev checklist), run **`/inicio-de-projeto`** — this brief is the visual direction; that one is the technical foundation.
+> For the engineering setup (folder structure, stack, patterns, dev checklist), run **`/wizz-inicio-de-projeto`** — this brief is the visual direction; that one is the technical foundation.
 
 Outside the method (standalone), keep the original behavior: emit the five copy-paste sections and the launch guide.
 

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

@@ -1,5 +1,5 @@
 ---
-name: design-motion-principles
+name: wizz-design-motion-principles
 description: "Motion and interaction design expert based on Emil Kowalski, Jakub Krehel, and Jhey Tompkins' techniques. Two modes — build interactive components with purposeful motion, or audit existing animations to catch AI-slop motion patterns (audit emits a branded HTML report with looping demos). Use when creating, adding, animating, or reviewing UI motion: transitions, hover states, micro-interactions, enter/exit animations, or any motion design work in React, Framer Motion, CSS, or HTML. Provides per-designer perspectives with context-aware weighting."
 ---
 

package/src/skills-lib/{design-motion-principles → wizz-design-motion-principles}/references/anti-checklist.md

@@ -93,7 +93,7 @@ Glowing dots, breathing CTAs, throbbing rings, "live"/"online"/"recording"/"AI a
 Identical `opacity + translateY` (with or without blur) enter animations applied to every section, card, paragraph, and heading. The "polished entrance" treatment from Jakub used uniformly across the page, regardless of element type or context.
 
 **Flag when you see:**
-- Multiple components sharing identical `initial`/`animate` opacity+translateY values
+- Multiple components sharing identical `initial`/`wizz-animate` opacity+translateY values
 - `whileInView` with identical viewport options applied to every block on a page
 - CSS keyframes with generic names (`fadeInUp`, `enter`, `reveal`) attached to many selectors
 
@@ -108,7 +108,7 @@ Identical `opacity + translateY` (with or without blur) enter animations applied
 Entrance animations on headings, body paragraphs, navigation links, and other content that should appear instantly. The "fade in everything" pattern that delays reading and makes the page feel sluggish.
 
 **Flag when you see:**
-- `initial`/`animate` on `<h1>`, `<h2>`, `<p>`, `<nav>` elements
+- `initial`/`wizz-animate` on `<h1>`, `<h2>`, `<p>`, `<nav>` elements
 - `whileInView` on body copy (paragraphs, articles, prose)
 - `animation` rules on text-only components without functional reason
 

package/src/skills-lib/{design-motion-principles → wizz-design-motion-principles}/workflows/audit.md

@@ -23,7 +23,7 @@ Before auditing any code, understand the project context.
 Check these sources:
 1. **CLAUDE.md** — Any explicit context about the project's purpose or design intent
 2. **package.json** — What type of app? (Next.js marketing site vs Electron productivity app vs mobile PWA)
-3. **Existing animations** — Grep for `motion`, `animate`, `transition`, `@keyframes`. What durations are used? What patterns exist?
+3. **Existing animations** — Grep for `motion`, `wizz-animate`, `transition`, `@keyframes`. What durations are used? What patterns exist?
 4. **Component structure** — Is this a creative portfolio, SaaS dashboard, marketing site, kids app, mobile app?
 
 ### Motion Gap Analysis (CRITICAL - Don't Skip)

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

@@ -1,5 +1,5 @@
 ---
-name: desktop-security
+name: wizz-desktop-security
 description: >
   Segurança para apps desktop e Electron. Usar quando: desenvolver app Electron, configurar contextIsolation/IPC,
   implementar code signing, armazenar tokens/credenciais localmente, configurar auto-update seguro,

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

@@ -1,6 +1,6 @@
 ---
-name: email-sequence
-description: When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro.
+name: wizz-email-sequence
+description: When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see wizz-cold-email. For in-app onboarding, see wizz-onboarding-cro.
 metadata:
   version: 1.1.0
 ---
@@ -301,9 +301,9 @@ For implementation, see the [tools registry](../../tools/REGISTRY.md). Key email
 
 ## Related Skills
 
-- **churn-prevention**: For cancel flows, save offers, and dunning strategy (email supports this)
-- **onboarding-cro**: For in-app onboarding (email supports this)
-- **copywriting**: For landing pages emails link to
-- **ab-test-setup**: For testing email elements
-- **popup-cro**: For email capture popups
-- **revops**: For lifecycle stages that trigger email sequences
+- **wizz-churn-prevention**: For cancel flows, save offers, and dunning strategy (email supports this)
+- **wizz-onboarding-cro**: For in-app onboarding (email supports this)
+- **wizz-copywriting**: For landing pages emails link to
+- **wizz-ab-test-setup**: For testing email elements
+- **wizz-popup-cro**: For email capture popups
+- **wizz-revops**: For lifecycle stages that trigger email sequences

package/src/skills-lib/{email-sequence → wizz-email-sequence}/evals/evals.json

@@ -1,5 +1,5 @@
 {
-  "skill_name": "email-sequence",
+  "skill_name": "wizz-email-sequence",
   "evals": [
     {
       "id": 1,

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

@@ -1,6 +1,6 @@
 ---
-name: form-cro
-description: When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms. Also use when the user mentions "form optimization," "lead form conversions," "form friction," "form fields," "form completion rate," "contact form," "nobody fills out our form," "form abandonment," "too many fields," "demo request form," or "lead form isn't converting." Use this for any non-signup form that captures information. For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.
+name: wizz-form-cro
+description: When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms. Also use when the user mentions "form optimization," "lead form conversions," "form friction," "form fields," "form completion rate," "contact form," "nobody fills out our form," "form abandonment," "too many fields," "demo request form," or "lead form isn't converting." Use this for any non-signup form that captures information. For signup/registration forms, see wizz-signup-flow-cro. For popups containing forms, see wizz-popup-cro.
 metadata:
   version: 1.1.0
 ---
@@ -45,7 +45,7 @@ Before providing recommendations, identify:
 
 ## Related Skills
 
-- **signup-flow-cro**: For account creation forms
-- **popup-cro**: For forms inside popups/modals
-- **page-cro**: For the page containing the form
-- **ab-test-setup**: For testing form changes
+- **wizz-signup-flow-cro**: For account creation forms
+- **wizz-popup-cro**: For forms inside popups/modals
+- **wizz-page-cro**: For the page containing the form
+- **wizz-ab-test-setup**: For testing form changes

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

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

package/src/skills-lib/{free-tool-strategy → wizz-free-tool-strategy}/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: free-tool-strategy
-description: When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. Also use when the user mentions "engineering as marketing," "free tool," "marketing tool," "calculator," "generator," "interactive tool," "lead gen tool," "build a tool for leads," "free resource," "ROI calculator," "grader tool," "audit tool," "should I build a free tool," or "tools for lead gen." Use this whenever someone wants to build something useful and give it away to attract leads or earn links. For content-based lead generation, see content-strategy.
+name: wizz-free-tool-strategy
+description: When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. Also use when the user mentions "engineering as marketing," "free tool," "marketing tool," "calculator," "generator," "interactive tool," "lead gen tool," "build a tool for leads," "free resource," "ROI calculator," "grader tool," "audit tool," "should I build a free tool," or "tools for lead gen." Use this whenever someone wants to build something useful and give it away to attract leads or earn links. For content-based lead generation, see wizz-content-strategy.
 metadata:
   version: 1.1.0
 ---
@@ -172,7 +172,7 @@ Rate each factor 1-5:
 
 ## Related Skills
 
-- **page-cro**: For optimizing the tool's landing page
-- **seo-audit**: For SEO-optimizing the tool
-- **analytics-tracking**: For measuring tool usage
-- **email-sequence**: For nurturing leads from the tool
+- **wizz-page-cro**: For optimizing the tool's landing page
+- **wizz-seo-audit**: For SEO-optimizing the tool
+- **wizz-analytics-tracking**: For measuring tool usage
+- **wizz-email-sequence**: For nurturing leads from the tool

package/src/skills-lib/{free-tool-strategy → wizz-free-tool-strategy}/evals/evals.json

@@ -1,5 +1,5 @@
 {
-  "skill_name": "free-tool-strategy",
+  "skill_name": "wizz-free-tool-strategy",
   "evals": [
     {
       "id": 1,

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

@@ -1,5 +1,5 @@
 ---
-name: huashu-design
+name: wizz-huashu-design
 description: 花叔Design——用HTML做高保真原型、交互Demo、幻灯片、动画、设计变体探索+设计方向顾问+专家评审。根据任务embody对应专家（UX/动画师/幻灯片设计师/原型师），避免web design tropes。触发词：做原型、交互原型、HTML演示、动画Demo、设计变体、hi-fi设计、UI mockup、prototype、做个HTML页面、做个可视化、app原型、iOS原型、导出MP4/GIF、60fps视频、设计风格、设计方向、配色方案、推荐风格、选个风格、做个好看的、评审、好不好看、review this design、带解说的动画、解说视频、长视频科普、voiceover、narration、5分钟讲清楚什么是XX。需求模糊时进设计方向顾问（三套逻辑并行出3版真实视觉，HTML原生40种风格库网页20+PPT20为弹药）；另含品牌资产协议、反AI slop、Junior工作流、Tweaks变体、动画→MP4/GIF导出、带解说长视频pipeline、5维评审。Use when 用户提到做HTML原型、交互Demo、幻灯片设计、动画Demo、设计变体探索或设计评审。
 ---
 

package/src/skills-lib/{huashu-design → wizz-huashu-design}/references/slide-decks.md

@@ -172,7 +172,7 @@ Chromium 默认不带彩色 emoji 字体，`page.pdf()` 或 `page.screenshot()`
 
 ### 2. `export_deck_pdf.mjs` 报错 `Cannot find package 'playwright'`
 
-原因：ESM 模块解析从脚本所在位置向上找 `node_modules`。脚本在 `~/.claude/skills/huashu-design/scripts/`，那里没依赖。
+原因：ESM 模块解析从脚本所在位置向上找 `node_modules`。脚本在 `~/.claude/skills/wizz-huashu-design/scripts/`，那里没依赖。
 
 **对策**：把脚本复制到 deck 项目目录（例如 `brochure/build-pdf.mjs`），在项目根跑 `npm install playwright pdf-lib`，然后 `node build-pdf.mjs --slides slides --out output/deck.pdf`。
 

package/src/skills-lib/{huashu-design → wizz-huashu-design}/references/verification.md

@@ -21,7 +21,7 @@ open -a "Google Chrome" "/path/to/your/design.html"
 HTML文件里最常见的问题是JS报错导致白屏。用Playwright跑一遍：
 
 ```bash
-python ~/.claude/skills/huashu-design/scripts/verify.py path/to/design.html
+python ~/.claude/skills/wizz-huashu-design/scripts/verify.py path/to/design.html
 ```
 
 这个脚本会：

package/src/skills-lib/{huashu-design → wizz-huashu-design}/scripts/tts-doubao.mjs

@@ -101,7 +101,7 @@ async function tts({ text, voice, speed, encoding }) {
 
   const body = {
     app: { cluster },
-    user: { uid: 'huashu-design' },
+    user: { uid: 'wizz-huashu-design' },
     audio: {
       voice_type: voiceId,
       encoding,

package/src/skills-lib/{humanizer → wizz-humanizer}/README.md

@@ -16,8 +16,8 @@ git clone https://github.com/blader/humanizer.git ~/.claude/skills/humanizer
 If you already have this repo cloned (or you downloaded `SKILL.md`), copy the skill file into Claude Code’s skills directory:
 
 ```bash
-mkdir -p ~/.claude/skills/humanizer
-cp SKILL.md ~/.claude/skills/humanizer/
+mkdir -p ~/.claude/skills/wizz-humanizer
+cp SKILL.md ~/.claude/skills/wizz-humanizer/
 ```
 
 ## Usage

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

@@ -1,5 +1,5 @@
 ---
-name: humanizer
+name: wizz-humanizer
 version: 2.3.0
 description: |
   Remove signs of AI-generated writing from text. Use when editing or reviewing

package/src/skills-lib/{humanizer → wizz-humanizer}/WARP.md

@@ -30,8 +30,8 @@ git clone https://github.com/blader/humanizer.git ~/.claude/skills/humanizer
 
 Manual install/update (only the skill file):
 ```bash
-mkdir -p ~/.claude/skills/humanizer
-cp SKILL.md ~/.claude/skills/humanizer/
+mkdir -p ~/.claude/skills/wizz-humanizer
+cp SKILL.md ~/.claude/skills/wizz-humanizer/
 ```
 
 ## How to “run” it (Claude Code)

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

@@ -1,5 +1,5 @@
 ---
-name: impeccable
+name: wizz-impeccable
 description: "Use when the user wants to review, audit, polish, redesign or improve a frontend interface. Covers hierarchy, accessibility, responsive layout, typography, color, motion, UX copy and component consistency. Wizz's self-contained adaptation runs on project evidence and bundled references."
 argument-hint: "[audit|critique|polish|shape|document|adapt|harden] [target]"
 user-invocable: true
@@ -16,7 +16,7 @@ Design and review working interfaces using project evidence. This bundle contain
 2. Preserve the established identity during refinement. For a requested redesign, choose a new direction while preserving product facts, functionality and user constraints. Explicit user choices take precedence over generic anti-pattern warnings.
 3. Choose the surface mode: **Persuade** (landing/marketing), **Operate** (app/dashboard), **Read** (docs/articles) or **Experience** (portfolio/gallery). A product can have surfaces in different modes.
 4. Map the requested action using [routing-rules](references/routing-rules.md). Read [command-workflows](references/command-workflows.md) for the relevant workflow and [design-rules](references/design-rules.md) before reviewing or changing UI.
-5. For new nontrivial components, invoke `skill:premium-landing-ui-researcher` or `skill:ui-component-curator` to obtain inspected sources. Do not replace source research with generic taste recommendations.
+5. For new nontrivial components, invoke `skill:wizz-premium-landing-ui-researcher` or `skill:wizz-ui-component-curator` to obtain inspected sources. Do not replace source research with generic taste recommendations.
 
 ## Verification