wizz-method 2.17.1 → 2.17.2

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "wizz-method",
-  "version": "2.17.1",
+  "version": "2.17.2",
   "description": "Wizz Method: método de agência orientado por IA em PT-BR",
   "keywords": [
     "agile",

package/src/modules/wizz/agents/wizz-designer/customize.toml

@@ -41,7 +41,7 @@ principles = [
 [[agent.menu]]
 code = "LP"
 description = "Landing page, hero, conversion page, 3D experience"
-prompt = "Invoke the GLOBAL skill 'wizz-premium-landing-ui-researcher' via the Skill tool to research references/components and build the landing page. Bring the result in easy {communication_language} and show the visual before the code."
+prompt = "Invoke the GLOBAL skill 'wizz-premium-landing-ui-researcher' via the Skill tool to research references/components and build the landing page. Mining runs on live sources opened in this session (load WebSearch/WebFetch first; curl, agent-browser or the local source cache as fallback); with none of them, report BLOCKED instead of recommending from memory. Bring the result in easy {communication_language} and show the visual before the code."
 
 [[agent.menu]]
 code = "UI"
@@ -61,4 +61,4 @@ prompt = "Invoke the GLOBAL skill 'wizz-taste-skill' via the Skill tool to revie
 [[agent.menu]]
 code = "CC"
 description = "Choose components that fit the existing project"
-prompt = "Invoke the GLOBAL skill 'wizz-ui-component-curator' via the Skill tool to analyze the project and recommend compatible components."
+prompt = "Invoke the GLOBAL skill 'wizz-ui-component-curator' via the Skill tool to analyze the project and recommend compatible components. Mining runs on live sources opened in this session (load WebSearch/WebFetch first; curl, agent-browser or the local source cache as fallback); with none of them, report BLOCKED instead of recommending from memory."

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

@@ -16,6 +16,10 @@ Check for `{output_folder}/design-state.yaml` (default `_wizz-output/`). Cheap c
 - **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.
 
+## Gate 0.5: open the access (always, before the first search)
+
+Read [web-access-and-evidence](references/web-access-and-evidence.md) and run its Step 0: load the web tools (on Claude Code, WebSearch and WebFetch are deferred and need `ToolSearch`), then fall back to `curl`, `agent-browser` and the local source cache. No web and no cache means BLOCKED, never research from memory. Before delivering, every recommended component passes that file's evidence gate; the rest are UNVERIFIED and are never recommended.
+
 ## Gate 1: Source-First (always, before any UI code)
 
 This skill exists because writing shaders, animations, hovers, and components from scratch is NOT the way. The way is to curate mature components, animations, and shaders from professional sources (the user's `modelos lp/`, React Bits, Cult UI, Ali Imam, Watermelon, StyleUI, Skiper UI, Componentry, and public registries) and adapt them to the brand.
@@ -64,5 +68,6 @@ 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) |
+| 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.

package/src/skills-lib/wizz-premium-landing-ui-researcher/references/component-sources.md

@@ -11,7 +11,7 @@ Research flow (public sources first; log evidence per [source-first-protocol](so
 3. public shadcn registries;
 4. taste/motion sources (Impeccable, Taste Skill, Design Motion Principles, MotionSites, Vibe Code Components, Refero Styles with a free DESIGN.md);
 5. open visual sources (Landing Love, Godly, Design Spells, Mobbin, Refero, ScreensDesign, DesignVault, Spline, Unicorn Studio);
-6. coherent strategic hypotheses, when there is no external access.
+6. with no web and no local cache: BLOCKED, per [web-access-and-evidence](web-access-and-evidence.md). Strategic hypotheses can shape the direction, never stand in for a component source.
 
 ## Mining Evidence
 

package/src/skills-lib/wizz-premium-landing-ui-researcher/references/source-first-protocol.md

@@ -56,7 +56,7 @@ Log in the existing design artifact (or create `design-research.md` in the proje
 |---|---|---|---|---|---|---|
 | Item actually inspected | Terms used and catalog | Real URLs or paths | SHA/tag; date if there's no version | Verified or pending | Tested / static / unavailable | Accepted/rejected and reason |
 
-Also include searches with no results and unavailable sources. Never fill in component names, paths, license, or test results by assumption.
+Also include searches with no results and unavailable sources. Never fill in component names, paths, license, or test results by assumption. A row missing any of the five fields in [web-access-and-evidence](web-access-and-evidence.md) is UNVERIFIED and cannot be the recommendation.
 
 Show 1-3 compatible candidates per component, with a recommendation and adaptation cost. If the user has already authorized the implementation and defined the direction, choose the best option within that scope and proceed. Only ask when a material decision about direction, paid access, or scope change is missing.
 

package/src/skills-lib/wizz-premium-landing-ui-researcher/references/web-access-and-evidence.md

@@ -0,0 +1,40 @@
+# Web access and evidence gate
+
+Shared by `wizz-premium-landing-ui-researcher` and `wizz-ui-component-curator`. Read it before the first search. It covers two moments: opening access before mining, and checking evidence before delivering.
+
+Mining from memory is the failure this file exists to prevent. Component names, URLs, licenses and APIs the model "remembers" are hypotheses, and a hypothesis delivered as research is worse than no research: the user builds on it without knowing.
+
+## Step 0: open the access (before any query)
+
+A tool you do not see is not a tool you do not have. In a subagent, the web tools often start unloaded.
+
+1. **Load the web tools.** On Claude Code, WebSearch and WebFetch are deferred: load them with `ToolSearch` (`select:WebSearch,WebFetch`) before deciding they are missing. Do the same for an Exa or scrapling MCP if the session lists one. On other platforms, use that platform's native web search and fetch.
+2. **Fallbacks, in order:** `curl -sL <url>` through the shell (raw HTML, registry JSON, `raw.githubusercontent.com` source files), then `agent-browser` (also the tool for watching hover and motion live).
+3. **Local source cache:** `~/.claude/design-sources/` holds real repositories (React Bits, Cult UI, Ali Imam, Watermelon, StyleUI). Reading a file there counts as evidence, as long as you record the path and the revision (`git -C <repo> rev-parse --short HEAD`) and say the cache may be behind the remote.
+4. **Record the outcome** in one line before mining: which access worked (`web`, `curl`, `agent-browser`, `cache only`) and which failed, with the error.
+
+If none of the four works, stop and return:
+
+```text
+BLOCKED: no web access and no local source cache.
+Tried: <tool → error, one per line>
+Unblock: <what the user can do, e.g. enable WebFetch, install agent-browser, clone the sources into ~/.claude/design-sources/>
+```
+
+BLOCKED is a complete, correct answer. Do not deliver component recommendations instead of it, not even marked "(verify)". Direction work that needs no source (site level, motion budget, style read of the project) can still be delivered next to BLOCKED, labelled as such.
+
+## Evidence gate (before delivering)
+
+Every candidate needs all five, collected in this session:
+
+| Field | Counts | Does not count |
+|---|---|---|
+| URL or path | The exact demo and the exact source file or registry item you opened | A catalog homepage, a search snippet, a URL you did not open |
+| Date | Today's date or the repo revision (SHA/tag) | "recent", "current" |
+| License | Read in the repo or registry | Assumed from the catalog's reputation |
+| Dependencies | Read from the actual imports or registry JSON | Guessed from the component's name |
+| Source read | The code file was opened and its imports checked | The demo alone |
+
+A candidate missing any field is **UNVERIFIED**. UNVERIFIED items go in a separate section of the report, with what is missing and why. They are never recommended and never placed in the top 1-3, and the implementation plan never depends on them. If every candidate for a need is UNVERIFIED, the need is reported as `unmet`, not filled.
+
+Before closing, check the delivery against this gate once: every recommended item has its five fields in the research log (`design-research.md` or the project's design artifact), and the access line from Step 0 is in the report.

package/src/skills-lib/wizz-ui-component-curator/SKILL.md

@@ -21,7 +21,7 @@ If `{output_folder}/design-state.yaml` exists, the need being worked is already
 
 Not there? Look before deciding it does not exist: `find . -name design-state.yaml -not -path '*/node_modules/*'`. A map found anywhere else is still the map: use it, and tell the user it is off-place (it belongs in `{output_folder}`).
 
-With no state file, continue normally.
+With no state file and more than one need in the request (a polish pass, "effects and animations", a dashboard), run `wizz-design-needs` first and mine against the map it writes. With no state file and one isolated component the user named, continue, and say the map was not created.
 
 ## 1. Read and infer the style DNA
 
@@ -42,7 +42,7 @@ Do not ask the user to describe the style unless the project has no inspectable
 
 Start with existing project components. Then search the public sources. The full authorized list (React Bits, Cult UI, Ali Imam, Watermelon, StyleUI, Skiper UI, Bklit UI, Componentry, shadcn/ui, plus the reference galleries) lives in one place: [component-sources](../wizz-premium-landing-ui-researcher/references/component-sources.md). Read it instead of relying on memory. Compare at least two suitable sources per need.
 
-Use whatever search tools the session has: web search (Exa when configured, WebSearch otherwise), WebFetch, scrapling, and `agent-browser` to watch hover and motion live. A tool that errors or hangs is not the end of the research: record the failure, move to the next tool, and never stop without reporting what was and was not checked.
+Before the first query, open the access as described in [web-access-and-evidence](../wizz-premium-landing-ui-researcher/references/web-access-and-evidence.md): load the web tools (on Claude Code, WebSearch and WebFetch are deferred and need `ToolSearch`), then fall back to `curl`, `agent-browser` and the local source cache. Search with whatever that step opened: web search (Exa when configured, WebSearch otherwise), WebFetch, scrapling, and `agent-browser` to watch hover and motion live. A tool that errors or hangs is not the end of the research: record the failure, move to the next tool, and never stop without reporting what was and was not checked. With no web and no cache, return BLOCKED instead of recommending from memory.
 
 Open the exact demo and source file/registry item. Check the actual imports, license, dependencies, stack variant and revision; use current official documentation (Context7 when available) for API compatibility. Inspect animation/interaction in the available browser; label static-only inspection honestly. If a source fails, record the failure and continue elsewhere.
 
@@ -57,6 +57,8 @@ Use the inferred style DNA as the search filter. Prefer:
 
 Do not present unranked lists. Shortlist internally, then surface only the strongest matches.
 
+Only candidates that pass the evidence gate in [web-access-and-evidence](../wizz-premium-landing-ui-researcher/references/web-access-and-evidence.md) can be shown here. The rest are UNVERIFIED and go to the evidence section.
+
 For each candidate, say briefly:
 - why it fits
 - what role it plays
@@ -131,4 +133,4 @@ Up to 2 backup options only if genuinely different and useful.
 What changes, which files, any dependency or adaptation work.
 
 ## Research evidence
-Exact candidate demo/source links, revision/date, license and dependencies, visual inspection status, decisions and unavailable sources. State what still needs a user decision.
+The access line (what worked, what failed), then exact candidate demo/source links, revision/date, license and dependencies, visual inspection status, decisions and unavailable sources. UNVERIFIED items listed apart, with what is missing. State what still needs a user decision.