wizz-method 2.21.0 → 2.23.0

package/src/skills-lib/wizz-design-needs/scripts/tests/test_design_state.py

@@ -0,0 +1,143 @@
+# /// script
+# requires-python = ">=3.10"
+# dependencies = ["pytest>=8.0", "ruamel.yaml>=0.18"]
+# ///
+"""Tests for design_state.py: rubric validation and the implementation gate."""
+
+import copy
+import importlib.util
+import json
+
+import pytest
+from pathlib import Path
+
+SCRIPT = Path(__file__).resolve().parents[1] / "design_state.py"
+spec = importlib.util.spec_from_file_location("design_state", SCRIPT)
+mod = importlib.util.module_from_spec(spec)
+spec.loader.exec_module(mod)
+
+RUBRIC = mod.load_rubric()
+CEILING = mod.load_ceiling()
+
+ADAPTATION = {
+    "padrao": "o título é revelado por uma máscara que sobe com o scroll",
+    "por_que": "segura o olho no título",
+    "invariante": "a máscara anda mais rápido que o scroll",
+    "variavel": ["easing", "duração"],
+    "reimplementacao": "tokens do projeto",
+}
+
+BASE = {
+    "version": 1,
+    "nivel": 1,
+    "needs": [
+        {"id": "b1", "surface": "home", "section": "hero", "layer": "comportamento", "why": "brief editorial", "floor": 7,
+         "status": "selected", "satisfied_by": ["d1"]},
+        {"id": "s1", "surface": "home", "section": "projetos", "layer": "secao", "why": "portfólio", "floor": 6,
+         "status": "open"},
+        {"id": "s2", "surface": "home", "section": "contato", "layer": "secao", "why": "captar contato",
+         "status": "unmet", "reason": "2 fontes secas"},
+    ],
+    "discoveries": [
+        {"id": "d1", "need": "b1", "surface": "home", "layer": "comportamento", "evidence": "verified",
+         "pattern_key": "scroll-mask-reveal", "observed": ["420ms"], "disqualifiers": [],
+         "scores": {"aderencia": 3, "execucao": 2, "custo_adaptacao": 2, "custo_performance": 1, "originalidade": 1, "total": 9},
+         "verdict": "ASSINATURA", "adaptation": ADAPTATION, "status": "selected"},
+        {"id": "d2", "need": "b1", "surface": "home", "layer": "comportamento", "evidence": "verified",
+         "pattern_key": "fade-up", "observed": ["fade"], "disqualifiers": ["reduced_motion"],
+         "verdict": "DESCARTAR", "status": "rejected", "reason": "ignora reduced motion"},
+    ],
+}
+
+
+def state(**changes):
+    data = copy.deepcopy(BASE)
+    for key, value in changes.items():
+        data[key] = value
+    return data
+
+
+def codes(data):
+    return {item["code"] for item in mod.validate(data, RUBRIC, CEILING)}
+
+
+def test_rubric_and_ceiling_are_read_from_the_skill_files():
+    assert RUBRIC["cut"] == 6 and "licenca" in RUBRIC["disqualifiers"]
+    assert CEILING[1] == 1 and CEILING[5] == 8
+
+
+def test_consistent_state_has_no_findings():
+    assert mod.validate(state(), RUBRIC, CEILING) == []
+
+
+def test_verdict_must_match_the_band():
+    data = state()
+    data["discoveries"][0]["verdict"] = "FORTE"
+    assert "verdict_band" in codes(data)
+    data["discoveries"][0]["reason"] = RUBRIC["signature_cap_reason"]
+    assert "verdict_band" not in codes(data)
+
+
+def test_entry_condition_forces_descartar_and_blocks_selection():
+    data = state()
+    data["discoveries"][1]["verdict"] = "UTILITARIO"
+    data["discoveries"][1]["status"] = "selected"
+    found = codes(data)
+    assert {"verdict_band", "selected_discarded"} <= found
+
+
+def test_selected_below_the_need_floor_and_without_adaptation():
+    data = state()
+    disc = data["discoveries"][0]
+    disc["scores"] = {"aderencia": 2, "execucao": 1, "custo_adaptacao": 2, "custo_performance": 1, "originalidade": 0}
+    disc["verdict"] = "UTILITARIO"
+    disc["adaptation"] = {"padrao": "x"}
+    assert {"selected_below_floor", "adaptation_missing"} <= codes(data)
+
+
+def test_two_signatures_on_one_surface_and_behaviour_ceiling():
+    data = state()
+    second = copy.deepcopy(data["discoveries"][0])
+    second.update(id="d3", pattern_key="cursor")
+    data["discoveries"].append(second)
+    assert {"signature_cap", "behaviour_ceiling"} <= codes(data)
+
+
+def test_reasons_and_dedup_links():
+    data = state()
+    data["needs"][2]["reason"] = None
+    data["discoveries"][1]["reason"] = None
+    data["discoveries"].append({"id": "d4", "need": "b1", "evidence": "verified", "observed": ["x"],
+                                "pattern_key": "other", "dup_of": "d1", "status": "rejected", "reason": "dup"})
+    assert {"need_reason", "discovery_reason", "dup_of"} <= codes(data)
+
+
+def test_gate_passes_selected_and_blocks_open_and_unplanned():
+    blocked, results = mod.gate(state(), ["home/hero"], [])
+    assert not blocked and results[0]["discoveries"] == ["d1"]
+    blocked, results = mod.gate(state(), ["home/projetos"], [])
+    assert blocked and results[0]["result"] == "blocked"
+    blocked, results = mod.gate(state(), ["home/rodape"], [])
+    assert blocked and results[0]["result"] == "unplanned"
+
+
+def test_gate_lets_unmet_through_with_the_justification():
+    blocked, results = mod.gate(state(), [], ["s2"])
+    assert not blocked and "from scratch" in results[0]["action"]
+
+
+def test_cli_exit_codes(tmp_path, capsys):
+    from ruamel.yaml import YAML
+
+    path = tmp_path / "design-state.yaml"
+    with open(path, "w", encoding="utf-8") as handle:
+        YAML().dump(state(), handle)
+    with pytest.raises(SystemExit) as ok:
+        mod.main(["validate", str(path)])
+    assert ok.value.code == 0 and json.loads(capsys.readouterr().out)["ok"] is True
+    with pytest.raises(SystemExit) as blocked:
+        mod.main(["gate", str(path), "--section", "home/projetos"])
+    assert blocked.value.code == 1 and json.loads(capsys.readouterr().out)["gate"] == "blocked"
+    with pytest.raises(SystemExit) as missing:
+        mod.main(["validate", str(tmp_path / "nope.yaml")])
+    assert missing.value.code == 2

package/src/skills-lib/wizz-impeccable/references/design-rules.md

@@ -48,6 +48,24 @@ One hard typographic ceiling you currently miss:
 **Gemini-specific defect: hard ban.** Never animate `<img>` elements on hover. This includes any `transform` on `:hover` of an image, AND `.group:hover .group-hover\:scale` / `.group:hover .group-hover\:rotate` / `.group:hover .group-hover\:translate` patterns from Tailwind that animate a child image via a parent hover. This is your single most common motion tell; it adds no information (the image isn't an action target) and reads as "AI animated this because it could". If a card needs hover feedback, animate the card's background, border, or shadow. Never the image, never via the image's parent. <!-- rule:skill-interaction-gemini-no-image-hover -->
 </gemini>
 
+#### Landing fine-tuning (Wizz addition, moved here from the landing Audit Protocol)
+
+Run with real tokens, real typography and real images; these only show once the page is alive.
+
+- **Spacing scale.** Section padding and margins follow one scale (4/8/12/16/24/32/48/64/96/128), not 24 here and 28 there.
+- **Heading hierarchy.** H1, H2 and H3 do not compete: each step has clear size or weight contrast.
+- **Leading.** Body `line-height` ≥ 1.5; display headlines ≤ 1.15.
+- **Small uppercase tracking.** Mono and small-caps labels need more tracking (~0.18em).
+- **Optical alignment.** Icons match the visual weight of adjacent text; mono numbers line up on a shared baseline.
+- **Vertical rhythm.** No run of sections without air, no unexplained huge gap.
+- **Colour hierarchy.** Five or more greys for text need a reason; the accent goes only on what is actionable.
+- **Image cropping.** Thumbnails in one grid share an aspect ratio.
+- **Weight contrast.** Heavy headings need a light or regular body to read against.
+- **Content edge cases.** Check a 1-word and a 4-word project name, a 2-line and a 4-line description.
+- **Tab order.** Focus follows the editorial sequence of the page, not a jump between sections.
+
+Output of this check: up to 7 adjustments, each as a specific before/after (e.g. "Hero subhead: leading 1.1 → 1.3").
+
 ### New projects only (when no prior work exists)
 
 #### Color & Theme

package/src/skills-lib/wizz-ios-build/SKILL.md

@@ -0,0 +1,61 @@
+---
+name: wizz-ios-build
+description: Build, sign and install an iOS app on a real iPhone from the command line with xtool (SwiftPM project, no Xcode IDE), on macOS, Linux or Windows via WSL. Covers setup and Apple login, creating the project, xtool.yml (bundle ID, Info.plist, icon, resources, entitlements, extensions) and the build-install loop on the device. Use when the user wants to build or install an iOS app without opening Xcode, or to develop for iPhone from Linux or Windows. Not for reviewing native UI against the Apple HIG (apple-design) or for shipping to TestFlight or the App Store.
+---
+
+# iOS build with xtool
+
+xtool ([xtool-org/xtool](https://github.com/xtool-org/xtool), MIT) builds a SwiftPM package into an `.app`, signs it with your Apple ID and installs it on a connected device. It replaces the Xcode build system, not the iOS SDK: on macOS Xcode still has to be installed for the SDK. The CLI is the registry entry `xtool` (dev area, opt-in).
+
+## 1. Check before anything
+
+Run `command -v xtool`. If it is missing, show the `install:` of the `xtool` entry and wait for the user. Then check the platform prerequisites:
+
+| Platform | Needs | Check |
+|---|---|---|
+| macOS | Xcode installed and opened once (SDK + toolchain) | `xcrun -sdk iphoneos --show-sdk-path` and `swift --version` |
+| Linux | Swift 6.4 toolchain, `usbmuxd`, the `Xcode.xip` downloaded from developer.apple.com in the browser (needs login), then `xtool sdk` | `swift --version`, `usbmuxd --help` |
+| Windows | everything from Linux inside WSL, plus USB passthrough (usbipd) to reach the iPhone | as Linux, from WSL |
+
+## 2. One-time setup
+
+`xtool setup` asks for the login mode. Explain the choice before the user picks:
+
+- **API Key**: needs a paid Apple Developer Program membership; uses the public App Store Connect API (a Team Key with the App Manager role). Recommended when they have the membership.
+- **Password**: any Apple ID, but goes through private Apple APIs. Suggest a throwaway Apple ID.
+
+Credentials are typed by the user in their terminal. Never ask them to paste a password or key into the chat, and never write one into a file of the project.
+
+## 3. Project
+
+- New app: `xtool new <Name>` creates a SwiftPM package with `xtool.yml` (bundle ID, default `com.example.<Name>`) and `.bsp/xtool.json` (editor support through SourceKit-LSP).
+- Existing SwiftPM code: add an `xtool.yml` with at least `version: 1` and `bundleID:`.
+
+Everything about the bundle lives in `xtool.yml`:
+
+| Key | What it does |
+|---|---|
+| `bundleID` | the app's ID; on device xtool prefixes it (e.g. `XTL-1234.`) so two free accounts don't collide |
+| `infoPath` | a partial `Info.plist` with only the keys to add or replace (display name, orientations) |
+| `iconPath` | PNG, ideally 1024x1024 |
+| `resources` | files copied to the root of the `.app` (e.g. `GoogleServices-Info.plist`); images used in code go in SwiftPM `resources:` instead |
+| `entitlementsPath` | an `.entitlements` plist |
+| `product` + `extensions` | which product is the app and which are extensions (widget, share), each with its own `infoPath` |
+
+A mistyped key is ignored without an error (e.g. `entitlements` instead of `entitlementsPath`): after a build, open `./xtool/<App>.app` and confirm the `Info.plist` and files are there.
+
+## 4. Build and install loop
+
+1. `xtool dev` builds and installs. The first build takes minutes (it builds the SDK modules once, then caches them). Use `xtool dev build` to only build.
+2. Connect the iPhone by USB. First time: tap **Trust** on the phone; if xtool errors right after pairing, run `xtool dev` again.
+3. xtool registers the device, creates certificate, App ID and provisioning profile, signs and installs.
+4. If iOS asks for **Developer Mode**, the user enables it (Settings > Privacy & Security) and you run `xtool dev` again.
+5. First launch shows "Untrusted Developer": Settings > General > VPN & Device Management > the account > Trust.
+
+Other commands: `xtool devices` (list connected devices), `xtool install <app.ipa>`, `xtool uninstall`, `xtool launch`, `xtool ds` (Apple Developer Services).
+
+## 5. Limits to say up front
+
+- Some entitlements don't work with a free account (Network Extension), some need special permission from Apple, and each capability needs a mapping inside xtool; a missing one fails late, at install. When the app depends on one of these, say so before building.
+- With a free account, apps installed this way expire after a few days and need a reinstall; the paid membership lifts that.
+- This skill covers development builds on a device. Shipping to TestFlight or the App Store is out of scope here.

package/src/skills-lib/wizz-motion-3d-director/references/motion-paths.md

@@ -29,6 +29,8 @@ Use when you need **real interaction**.
 - Framer Motion or Motion for scroll integration;
 - GSAP (ScrollTrigger) when scroll orchestrates the scene — 100% free since v3.13, all plugins included.
 
+**Reference for fluid effects:** when the brief asks for a fluid cursor trail, liquid distortion or ink-like smoke over a Three.js scene, `artcodev/three-fluid-fx` (MIT, npm `three-fluid-fx`, 0.1.0 on 2026-10-24) is a drop-in 2D Stable-Fluids solver with WebGL/GLSL and WebGPU/TSL pipelines. Pointer only: the method does not install it, and an early version means pinning the exact release and checking the mobile cost against the performance targets before adopting it.
+
 **Examples:** a 3D object that follows the cursor; a mouse-reactive particle sphere; a camera that advances on scroll; real-time wireframe terrain; a configurable 3D product; an interactive WebGL background.
 
 **Avoid if:**

package/src/skills-lib/wizz-offer-forge/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wizz-offer-forge
-description: Forges irresistible direct-response and info-product offers by integrating a unique mechanism, offer thesis, value stacking, reverse guarantee, price anchoring, and a creative matrix for paid traffic. Use when the user wants to create a new offer from scratch, restructure an existing offer that isn't converting, stack high-perception bonuses, define an aggressive guarantee, or translate audience research (Piva/VoC) into a sales machine. Do NOT use for raw audience research (use wizz-pesquisa-de-publico-do-piva) or final page copywriting (use wizz-copywriting).
+description: Forges irresistible direct-response and info-product offers by integrating a unique mechanism, offer thesis, value stacking, reverse guarantee, price anchoring, and a creative matrix for paid traffic. Use when the user wants to create a new offer from scratch, restructure an existing offer that isn't converting, stack high-perception bonuses, define an aggressive guarantee, or translate audience research (VoC) into a sales machine. Do NOT use for raw audience research (use wizz-pesquisa-de-publico) or final page copywriting (use wizz-copywriting).
 ---
 
 # Wizz Offer Forge
@@ -34,7 +34,7 @@ A master artifact `OFFER-SPEC.md` containing:
 If the `wizz-cerebro` skill is installed, run `/wizz-cerebro ver` for the project and grep by theme in `_decisions/`. Look specifically for: a previous offer to the same audience, a price already tested, a guarantee already used, and any logged decision that forbids a certain path. Bring back what you found as input and state in your reply where it came from. Without the skill installed, skip this block and proceed with the questions below.
 
 Then, consult existing context or ask the user:
-1. **Prior Audience Research:** Is there a report from the `wizz-pesquisa-de-publico-do-piva` skill or VoC notes? If so, import it as primary input. If not, define the Avatar, Latent Pain, and initial Awareness Level.
+1. **Prior Audience Research:** Is there a report from the `wizz-pesquisa-de-publico` skill or VoC notes? If so, import it as primary input. If not, define the Avatar, Latent Pain, and initial Awareness Level.
 2. **Business Model:** Low-ticket (R$ 10 to R$ 97), Mid front-end (R$ 197 to R$ 497), or High-ticket / Mentorship (R$ 1,000 to R$ 10,000+)?
 3. **Delivery Vehicle:** Recorded course, community, templates/tools, live mentorship, SaaS, or hybrid?
 

package/src/skills-lib/wizz-paid-ads/SKILL.md

@@ -86,7 +86,8 @@ LI_LeadGen_CMOs-SaaS_Whitepaper_Mar24
 
 **Scaling phase:**
 - Consolidate budget into winning combinations
-- Increase budgets 20-30% at a time
+- On Meta with a bid cap campaign, follow the order in `wizz-lowticket-metodologia` `knowledge/03-campanha-bidcap.md`: bid cap first, then validated creatives, then budget by the ROAS ruler
+- Without a bid cap (other platforms, or a campaign not built on it yet): increase budgets 20-30% at a time
 - Wait 3-5 days between increases for algorithm learning
 
 ---

package/src/skills-lib/wizz-paywall-upgrade-cro/SKILL.md

@@ -67,6 +67,7 @@ When trial is ending:
 - Early warnings (7, 3, 1 day)
 - Clear "what happens" on expiration
 - Summarize value received
+- People restarting the trial with new accounts: don't block by IP; use the risk score in `wizz-signup-flow-cro` (trial abuse)
 
 ### Time-Based Prompts
 After X days of free use:

package/src/skills-lib/{wizz-pesquisa-de-publico-do-piva → wizz-pesquisa-de-publico}/README.md

@@ -1,17 +1,15 @@
-# Pesquisa de Público do Piva — a skill for Claude
+# Pesquisa de Público — a skill for Claude
 
 Turns **an offer document** into a complete audience research arsenal for paid traffic: six chained reports (VoC, Psychographic Profile, Levels of Awareness, Trend, Angle Matrix and Lexicon) compiled into a tab-navigable HTML, ready to hand to the client or use as a copy foundation.
 
-Made by **[@soupiva](https://www.instagram.com/soupiva/)**.
-
----
-
 ## What's in the box
 
 ```
-pesquisa-de-publico-do-piva/
+wizz-pesquisa-de-publico/
 ├── SKILL.md              → the workflow Claude follows
 ├── prompts.md            → the six research prompts, production-tested
+├── references/
+│   └── interview-mode.md → the guided interview for when there is no data yet
 ├── assets/
 │   └── template.html     → the final document, already styled and ready
 └── README.md             → this file
@@ -23,7 +21,7 @@ pesquisa-de-publico-do-piva/
 
 ## Installation (Claude web or desktop)
 
-1. Download the `pesquisa-de-publico-do-piva.zip` file without unzipping it.
+1. Download the `wizz-pesquisa-de-publico.zip` file without unzipping it.
 2. First, turn on code execution: **Settings → Capabilities → "Code execution and file creation"**. Without this, skills won't work.
 3. Go to **Customize → Skills**.
 4. Click **+ / Add skill** and upload the ZIP.
@@ -33,7 +31,7 @@ Done. Skills you upload are private to your account.
 
 ### Using it in Claude Code
 
-Unzip the `pesquisa-de-publico-do-piva/` folder into `~/.claude/skills/` (to use it across any project) or into `.claude/skills/` at the repo root (to use it only in that project).
+Unzip the `wizz-pesquisa-de-publico/` folder into `~/.claude/skills/` (to use it across any project) or into `.claude/skills/` at the repo root (to use it only in that project).
 
 ---
 
@@ -42,7 +40,7 @@ Unzip the `pesquisa-de-publico-do-piva/` folder into `~/.claude/skills/` (to use
 Open a conversation, attach your offer document (`.docx`, `.pdf`, `.md` or `.txt`) and write:
 
 ```
-/wizz-pesquisa-de-publico-do-piva
+/wizz-pesquisa-de-publico
 ```
 
 Or, without the slash, anything in that spirit:
@@ -57,6 +55,12 @@ At the end, you get the finished HTML ready to open in the browser.
 
 ---
 
+### No offer or audience data yet
+
+Pre-launch, or you can't describe who buys? Say so ("ainda não lancei, me entrevista"). Claude asks one question at a time, each with 3–4 possible answers to pick from, and after every answer tells you what changed in the picture. You get an illustrative persona, clearly marked as a hypothesis, plus the list of what to validate, which is your script for collecting real comments.
+
+---
+
 ## What this skill does NOT do
 
 It stops at research. **It doesn't write ads, scripts, final headlines or finished creatives.** The hooks that appear in the Angle Matrix are writing direction built from the audience's own vocabulary — raw material for the copywriter, not a ready-to-run asset.
@@ -77,7 +81,3 @@ This means you'll sometimes get less material than you expected. That's intentio
 - **The segment changes everything.** "People who want to learn X" yields generic results. "People who already tried X and gave up" yields gold. Pick the pain point, not the topic.
 - **The anchor source isn't always the product's subject.** If you sell a book summary, the goldmine might not be the book's readers — it might be the people living the problem the book solves. Tell Claude this when confirming the context.
 - **Run a second round when the caveats point to it.** Pasting 30–50 real comments you copied yourself from niche videos usually doubles the quality of the Lexicon.
-
----
-
-**[@soupiva](https://www.instagram.com/soupiva/)**

package/src/skills-lib/{wizz-pesquisa-de-publico-do-piva → wizz-pesquisa-de-publico}/SKILL.md

@@ -1,11 +1,11 @@
 ---
-name: wizz-pesquisa-de-publico-do-piva
-description: Generates a complete audience research arsenal for an infoproduct offer and paid traffic, from an offer document (.docx/.md/.txt/.pdf). Produces six chained reports — VoC, Schwartz Psychographic Profile, Levels of Awareness, Trend Report, Angle Matrix and Lexicon — compiled into a tab-navigable HTML dashboard. Use when the user sends an offer and asks for audience research, VoC, voice of customer, angle matrix, audience lexicon, persona pain points, or a copy arsenal for direct traffic. Do NOT use for technical research on libraries/code (use context7), broad B2B market research (use deep-research), or visual UI research (use wizz-premium-landing-ui-researcher). Methodology by @soupiva.
+name: wizz-pesquisa-de-publico
+description: Generates a complete audience research arsenal for an infoproduct offer and paid traffic, from an offer document (.docx/.md/.txt/.pdf). Produces six chained reports — VoC, Schwartz Psychographic Profile, Levels of Awareness, Trend Report, Angle Matrix and Lexicon — compiled into a tab-navigable HTML dashboard. Use when the user sends an offer and asks for audience research, VoC, voice of customer, angle matrix, audience lexicon, persona pain points, or a copy arsenal for direct traffic. With no offer or audience data yet (pre-launch), runs a guided interview that builds an illustrative persona and the list of what to validate. Do NOT use for technical research on libraries/code (use context7), broad B2B market research (use deep-research), or visual UI research (use wizz-premium-landing-ui-researcher).
 ---
 
-# Pesquisa de Público do Piva
+# Pesquisa de Público
 
-Direct-marketing research pipeline for infoproducts and paid-traffic offers, validated in production by @soupiva. From a single offer, it generates six chained reports and a final tab-navigable HTML document. Each report feeds the next.
+Direct-marketing research pipeline for infoproducts and paid-traffic offers, validated in production. From a single offer, it generates six chained reports and a final tab-navigable HTML document. Each report feeds the next.
 
 **This skill stops at research.** It doesn't write ads, scripts, final headlines or ready-to-run creatives. The hooks that appear in the Angle Matrix are strategic writing direction based on the audience's native language.
 
@@ -19,6 +19,8 @@ Direct-marketing research pipeline for infoproducts and paid-traffic offers, val
 6. **Audience Lexicon** — exhaustive compilation of native expressions mined by emotional territory, with confidence badge and copy-usage note.
 7. **Final HTML document** — compiles the six reports into a single tab-styled file, using `assets/template.html`.
 
+With no data yet, **interview mode** comes first: a guided interview that produces an illustrative persona (`persona-entrevista.md`), marked as a hypothesis, ending with what still needs validating. Protocol in `references/interview-mode.md`.
+
 ## Non-negotiable principle: epistemic honesty
 
 **Never fabricate quotes, links, dates or data.** Only report language that was actually found in real, indexed public sources. Mark the confidence level of every quote:
@@ -33,6 +35,8 @@ When a source can't be accessed, **state it clearly in the Caveats section** as
 
 ### Step 0 — Read the offer and extract the base context
 
+**No offer and no audience data?** (pre-launch, no comments or reviews, or the user can't describe who buys.) Run **interview mode** first, following `references/interview-mode.md`: one question per turn, each with 3-4 hypothesis answers, a new reading after every answer. Its `persona-entrevista.md` becomes the input for this step, and every report built on it says so.
+
 Read the offer document (or description). Distill the **base context**:
 - **Product**: what it is, format, price, central promise, positioning.
 - **Likely persona**: who buys, age range, life/work context, awareness level.
@@ -56,9 +60,9 @@ Follow the dependency order (full prompts in `prompts.md`):
 ### Step 2 — Compile the final HTML document
 
 1. Use the pre-formatted layout in `assets/template.html`.
-2. Replace the `{{...}}` placeholders while keeping the `<style>` and structure intact.
-3. Mandatory file naming: `Pesquisa [SHORT_NAME] - @soupiva.html` (saved to `{output_folder}/pesquisa-piva/` or the project directory).
-4. Keep the confidence badges (`.pill`) and the `@soupiva` signature.
+2. Replace the `{{...}}` placeholders while keeping the `<style>` and structure intact. `{{ORIGEM_DA_PESQUISA}}` says what the research stands on (e.g. "Documento da oferta + VoC"); in interview mode use the commented line under it, with the hypothesis badge.
+3. Mandatory file naming: `Pesquisa [SHORT_NAME].html` (saved to `{output_folder}/pesquisa-de-publico/` or the project directory).
+4. Keep the confidence badges (`.pill`).
 
 ### Step 3 — Deliver and connect
 

package/src/skills-lib/{wizz-pesquisa-de-publico-do-piva → wizz-pesquisa-de-publico}/assets/template.html

@@ -3,7 +3,7 @@
 <head>
 <meta charset="UTF-8">
 <meta name="viewport" content="width=device-width, initial-scale=1.0">
-<title>Pesquisa {{NOME_CURTO_DA_OFERTA}} - @soupiva</title>
+<title>Pesquisa {{NOME_CURTO_DA_OFERTA}}</title>
 <link rel="preconnect" href="https://fonts.googleapis.com">
 <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
 <link href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700;800&family=JetBrains+Mono:wght@400;500;700&display=swap" rel="stylesheet">
@@ -153,16 +153,8 @@ ol.findings li:before{content:counter(f,decimal-leading-zero);position:absolute;
 .caveats{background:transparent;border:1px dashed var(--line);border-radius:16px;padding:22px 24px;margin-top:28px}
 .caveats h3{color:var(--txt-mid);font-family:'JetBrains Mono',monospace;font-size:11px;letter-spacing:.16em;text-transform:uppercase}
 
-/* ---------- ASSINATURA @soupiva ---------- */
-.sig-fixed{position:fixed;right:18px;bottom:18px;z-index:99;display:flex;align-items:center;gap:9px;
-  background:rgba(8,21,19,.92);border:1px solid rgba(46,229,157,.4);border-radius:100px;
-  padding:10px 18px 10px 14px;text-decoration:none;color:var(--green);font-size:14px;font-weight:600;
-  backdrop-filter:blur(10px);box-shadow:0 6px 26px rgba(0,0,0,.55);transition:.18s}
-.sig-fixed:hover{background:rgba(46,229,157,.14);transform:translateY(-2px)}
-.sig-fixed .ico{width:19px;height:19px;filter:none}
+/* ---------- RODAPÉ ---------- */
 footer{text-align:center;margin-top:44px;padding-top:26px;border-top:1px solid var(--line)}
-footer a{display:inline-flex;align-items:center;gap:9px;text-decoration:none;color:var(--green);
-  font-size:16px;font-weight:700}
 footer .made{display:block;font-family:'JetBrains Mono',monospace;font-size:10.5px;
   letter-spacing:.16em;color:var(--txt-dim);margin-top:10px;text-transform:uppercase}
 
@@ -172,7 +164,6 @@ footer .made{display:block;font-family:'JetBrains Mono',monospace;font-size:10.5
   .tabs{grid-template-columns:repeat(3,1fr)}
   .grid-4{grid-template-columns:repeat(2,1fr)}
   .fw{flex-direction:column;gap:2px}
-  .sig-fixed{right:12px;bottom:12px;padding:9px 15px 9px 12px;font-size:13px}
 }
 </style>
 </head>
@@ -194,7 +185,6 @@ footer .made{display:block;font-family:'JetBrains Mono',monospace;font-size:10.5
   <symbol id="i-quote" viewBox="0 0 24 24"><rect x="3" y="4" width="18" height="14.5" rx="2.5"/><path d="M7.5 9h6M7.5 13h9"/></symbol>
   <symbol id="i-pulse" viewBox="0 0 24 24"><path d="M2 12h4l2.5-7 4 15L15.5 12H22"/></symbol>
   <symbol id="i-layers" viewBox="0 0 24 24"><path d="m12 3 9 5-9 5-9-5z"/><path d="m3 13 9 5 9-5"/></symbol>
-  <symbol id="i-insta" viewBox="0 0 24 24"><rect x="3" y="3" width="18" height="18" rx="5"/><circle cx="12" cy="12" r="4"/><path d="M17.2 6.8v.01"/></symbol>
   <symbol id="i-radar" viewBox="0 0 200 200">
     <circle cx="100" cy="100" r="88" stroke-opacity=".28"/><circle cx="100" cy="100" r="62" stroke-opacity=".4"/>
     <circle cx="100" cy="100" r="36" stroke-opacity=".6"/>
@@ -210,9 +200,12 @@ footer .made{display:block;font-family:'JetBrains Mono',monospace;font-size:10.5
   <!-- ================= HERO ================= -->
   <div class="hero">
     <svg class="hero-radar" style="stroke:var(--green);fill:none;stroke-width:1.2;color:var(--green)"><use href="#i-radar"/></svg>
-    <div class="kicker"><svg class="ico ico-sm"><use href="#i-target"/></svg> Arsenal de Pesquisa de Oferta · Método @soupiva</div>
-    <h1>Pesquisa {{NOME_CURTO_DA_OFERTA}} - @soupiva</h1>
+    <div class="kicker"><svg class="ico ico-sm"><use href="#i-target"/></svg> Arsenal de Pesquisa de Oferta</div>
+    <h1>Pesquisa {{NOME_CURTO_DA_OFERTA}}</h1>
     <div class="recorte">Recorte: {{RECORTE_DO_PUBLICO}}</div>
+    <div class="recorte">Origem: {{ORIGEM_DA_PESQUISA}}</div>
+    <!-- Modo entrevista: troque a linha acima por
+         <div class="recorte">Origem: Entrevista · <span class="pill pill-blue">Hipótese, validar antes de usar</span></div> -->
     <p>Seis relatórios encadeados de pesquisa de público para tráfego pago.<br>Mineração feita sobre quem vive a dor — não sobre quem já é cliente.</p>
     <div class="pipeline">
       <div class="pipe-step on"><svg class="ico"><use href="#i-mic"/></svg><span class="lbl">VoC</span></div>
@@ -390,16 +383,10 @@ footer .made{display:block;font-family:'JetBrains Mono',monospace;font-size:10.5
   </div>
 
   <footer>
-    <a href="https://www.instagram.com/soupiva/" target="_blank" rel="noopener">
-      <svg class="ico ico-sm"><use href="#i-insta"/></svg> @soupiva
-    </a>
-    <span class="made">Pesquisa de Público do Piva</span>
+    <span class="made">Pesquisa de Público</span>
   </footer>
 </div>
 
-<a class="sig-fixed" href="https://www.instagram.com/soupiva/" target="_blank" rel="noopener">
-  <svg class="ico"><use href="#i-insta"/></svg> @soupiva
-</a>
 
 <script>
 function showTab(i,btn){

package/src/skills-lib/wizz-pesquisa-de-publico/references/interview-mode.md

@@ -0,0 +1,69 @@
+# Interview mode (no data yet)
+
+For when there is nothing to mine from: pre-launch, no offer document, no VoC, or a user who can't describe the audience. The interview builds an **illustrative persona** from what the user knows and suspects. It is a hypothesis, never evidence, and its last section is the script for collecting the real VoC.
+
+## When to use it
+
+- The user has no offer document and no audience material, or says so ("ainda não lancei", "não sei quem compra", "não tenho comentário nenhum").
+- The user asks for it by name ("me entrevista", "modo entrevista").
+- An offer exists but Step 0 can't fill the likely persona or the problems it solves: offer the interview before running the reports.
+
+When real material exists (offer document, comments, reviews, calls), the normal workflow wins. The interview can still run on top to fill a gap, and the output says which parts came from where.
+
+## Protocol
+
+1. **One question per turn.** Never a questionnaire. Wait for the answer.
+2. **Every question carries 3 or 4 hypothesis answers**, lettered, plus "outra coisa". The hypotheses unlock someone who can't describe the audience; they are guesses grounded in the niche, not leading answers. The user may pick, mix or reject them.
+3. **After each answer, give a new reading before the next question:** 2 or 3 lines on what the answer changes in the persona, and what it hints at that hasn't been said yet. The reading is where the hidden blocker shows up (in testing, 4 rounds surfaced a fear of social judgment that wasn't in the briefing; the brief only talked about fear of selling).
+4. **Follow the thread that surprises.** The question order below is a default; when an answer opens something unexpected, the next question digs there.
+5. **Stop at saturation**, usually 6 to 10 rounds: when two answers in a row change nothing in the reading, or when the user asks to stop. Say how many rounds ran.
+
+### Default question sequence
+
+Ask in Portuguese, in the user's register. Adapt the wording to the niche.
+
+| # | Topic | What it opens |
+|---|---|---|
+| 1 | Who buys and at what moment of life | Persona, trigger moment |
+| 2 | What they already tried and why it didn't work | Sophistication, false solutions |
+| 3 | What stops them from buying today | **The fear that blocks the purchase** |
+| 4 | What goes through their head at night about it | Mental ruminations |
+| 5 | Who they want to become, and how others would see them | Desired identity |
+| 6 | An ordinary day: where the problem shows up | A day in the life |
+| 7 | Where they talk about it in public, and in which words | Anchor source for the real VoC |
+| 8 | What they'd never admit about it | Won't Tell / Can't Tell (feeds Report 3) |
+
+Example of one turn (question 3):
+
+> **O que mais trava essa pessoa na hora de comprar?**
+> a) Medo de jogar dinheiro fora de novo
+> b) Vergonha de os outros descobrirem que ela precisou de ajuda
+> c) Não acreditar que funciona para o caso dela
+> d) Falta de tempo para aplicar
+> e) Outra coisa
+
+## Output
+
+Save to `{output_folder}/pesquisa-de-publico/persona-entrevista.md`, in Portuguese, with these sections in this order:
+
+1. **Aviso no topo:** "Persona ilustrativa: hipótese montada em entrevista com <quem> em <data>, <N> rodadas. Não é VoC. Valide antes de usar como prova."
+2. **Contexto base** (the same five fields as Step 0).
+3. **Persona** (who, life moment, context).
+4. **O medo que bloqueia a compra.**
+5. **Ruminações mentais** (what they repeat to themselves, in their words as the user imagined them).
+6. **Identidade desejada.**
+7. **Um dia na vida.**
+8. **Plano de aplicação da persona** (where each trait goes: hook, offer, objection handling, page section).
+9. **O que ainda não sabemos** (every point where the user hesitated, guessed, or picked a hypothesis without conviction).
+10. **O que precisamos validar:** one row per hypothesis, with where to collect (the anchor source from question 7), what to look for, and what would refute it. This list **is the VoC collection script**: hand it over as the next step.
+
+Interview answers are never quotes. They never get the `Verificável`, `Fórum` or `EN` badges, and never go into the VoC report as audience language.
+
+## How the six reports use it
+
+The interview replaces the offer document as the input to Step 0. Then the workflow runs as usual:
+
+- **VoC (1) and Trend (4)** still mine the web, using the anchor source from question 7. What they find is real and keeps its badges.
+- **Schwartz (2), Awareness (3) and Matrix (5)** open with one line saying they start from interview, not VoC, and how much real VoC was found to support it. Every trait that rests only on the interview is marked `hipótese`.
+- **Lexicon (6)** only lists expressions actually found. Words the user imagined stay in the persona file.
+- In the HTML, fill `{{ORIGEM_DA_PESQUISA}}` with `Entrevista` and keep the hypothesis badge on every item from the interview.

package/src/skills-lib/wizz-premium-landing-ui-researcher/SKILL.md

@@ -11,7 +11,7 @@ Autonomous strategist for premium landing pages, SaaS UI, and advanced visual ex
 
 Check for `{output_folder}/design-state.yaml` (default `_wizz-output/`). Cheap check first: `grep -c 'status: open'`. Not there? Run `find . -name design-state.yaml -not -path '*/node_modules/*'` before concluding it does not exist: a map found elsewhere is still the map, so use it and tell the user it is off-place.
 
-- **It exists, with open needs:** you are not deciding what to research. Work **one need per pass**, in the order given, and take `query`, `budget.fontes` and `floor` as given. Read the `proibidos` block before writing any query: a query that lands on a forbidden capability is not run, not even for comparison. Write each finding back under `discoveries` with the `need` id, and move the need to `selected` or `unmet` with a reason. Stop when the needs are exhausted, not when the ideas are.
+- **It exists, with open needs:** you are not deciding what to research. Work **one need per pass**, in the order given, and take `query`, `budget.fontes` and `floor` as given. Read the `proibidos` block before writing any query: a query that lands on a forbidden capability is not run, not even for comparison. Judge each candidate with [mining-rubric](references/mining-rubric.md) (entry conditions, score, verdict, selection) and write it back under `discoveries` with the `need` id. Each need closes on one of the rubric's stop conditions, never on a feeling of having seen enough. After writing, run `uv run --no-cache ../wizz-design-needs/scripts/design_state.py validate {output_folder}/design-state.yaml` and fix its findings before the handoff. Stop when the needs are exhausted, not when the ideas are.
 - **It exists, no open needs:** the map is done. Do not open new research on your own: report it and hand back to `wizz-design-needs` if something is genuinely missing.
 - **It does not exist, and the work is non-trivial:** invoke `skill:wizz-design-needs` first. Mining without a map is how a project ends up depending on the user to name every effect, one request at a time.
 - **It does not exist, and the work is one isolated component the user named:** proceed, and say the map was not created.
@@ -28,6 +28,8 @@ Absolute rule: inspect real sources, log evidence, and recommend options, adapt
 
 ## Gate 2: classify the site's level (always, before recommending components)
 
+The brief and the visual identity belong to `wizz-decision-maker` (`brief` and `identidade` in `design-state.yaml`): when they exist, read objective, audience and references from them instead of asking again, and never redefine palette or typography here. This skill owns only the level classification and the component and motion research.
+
 If essential data is missing, ask at most 5 strategic questions: (1) business/product/offer, (2) target audience, (3) page's main objective, (4) desired visual level, (5) existing visual references. If the user doesn't answer everything, continue with coherent strategic hypotheses. Master rule: ask, infer, execute.
 
 Classify the project into one of 5 levels (rules, allowed/forbidden motion, and budget per level in [site-levels](references/site-levels.md)):
@@ -60,7 +62,8 @@ Classify the project into one of 5 levels (rules, allowed/forbidden motion, and
 | Handoffs to wizz-motion-3d-director and wizz-implementation-planner, final ladder rule | [handoffs](references/handoffs.md) |
 | SaaS Dashboard Mode and Portfolio / Authority Site Mode | [dashboard-and-portfolio-modes](references/dashboard-and-portfolio-modes.md) |
 | The mandatory 12-step process and honesty checkpoint | [mandatory-process](references/mandatory-process.md) |
-| The 5-phase protocol (inventory, public search, cache, evidence, adaptation) | [source-first-protocol](references/source-first-protocol.md) |
+| The 6-phase protocol (inventory, public search, cache, evidence, adaptation, stop) | [source-first-protocol](references/source-first-protocol.md) |
+| Entry conditions, 0-10 score, verdicts, selection, stop conditions, dedup and the adaptation protocol | [mining-rubric](references/mining-rubric.md) |
 | Audit Protocol: Pass 1 Taste, Pass 2 Impeccable, Pass 3 Cross-check, Pass 4 A11y/Perf | [audit-protocol](references/audit-protocol.md) |
 | Component sources (React Bits, Cult UI, Ali Imam, Watermelon, StyleUI, Skiper UI, Bklit UI, Componentry), animation engines (GSAP, anime.js), reference and visual inspiration sources, Clone Policy, Paid Source Policy | [component-sources](references/component-sources.md) |
 | Default stack, visual direction, palettes, typography, and animation selection rules | [stack-and-visual-direction](references/stack-and-visual-direction.md) |
@@ -68,6 +71,7 @@ Classify the project into one of 5 levels (rules, allowed/forbidden motion, and
 | Base prompts (complete landing page and 3D scroll hero) | [prompt-templates](references/prompt-templates.md) |
 | Final response format, Quality Bar, and self-check before closing the delivery | [output-format-and-quality](references/output-format-and-quality.md) |
 | Direct links to every authorized source | [source-links](references/source-links.md) |
+| The source catalogue as data (kind, access, license, need tags, cache folder), queried with `scripts/design_sources.py list --need <tag>`; cache freshness and refresh with `freshness` / `refresh` | [design-sources.yaml](references/design-sources.yaml) |
 | Opening web access before mining, BLOCKED, and the evidence gate before delivering | [web-access-and-evidence](references/web-access-and-evidence.md) |
 
 Final rule: never put real keys inside the skill (environment variables only), and never deliver a landing page that looks like a template with no positioning.