CascadingLabs

Use for bounded read-only QA over an existing Yosoi observation index.

Use for bounded agent discovery over a Yosoi QA observation index with evidence-bound navigate/click actions and deterministic postconditions.

Use when acquiring web page evidence with Yosoi without scraping: safe LLM-bounded content previews, raw/static HTML, rendered HTML, cleaned HTML, text/markdown, links, headers, network endpoints, accessibility snapshots, bundles, and advisory contract probes…

Use when an agent needs to use Yosoi for crawl, search, fetch, or research workflows. Triggers include web crawl, source discovery, page fetch, evidence packet, research frontier, local Perplexity, candidate contracts, scrape pipeline planning, and turning…

Use when doing exploratory web/data research with Yosoi primitives before building a deterministic scraper or always-on pipeline. Triggers include research frontier, data frontier, local Perplexity, competitor analysis, web stats, source mapping, candidate…

Use when doing exploratory web/data research with Yosoi primitives before building a deterministic scraper or always-on pipeline. Triggers include research frontier, data frontier, local Perplexity, competitor analysis, web stats, source mapping, candidate…

Use when planning a Yosoi change before implementation, especially when the work crosses core modules, tests, provider behavior, or observability.

Use when starting work in Yosoi, mapping the relevant package area, or deciding which committed project docs and nested AGENTS files to inspect first.

Stealthy, concurrent headless browsing via the voidcrawl-mcp MCP server. Use for bulk/parallel web fetches, JS-rendered pages, bot-detection evasion (Cloudflare/Turnstile/fingerprinting), isolated per-task browser sessions, or durable element targeting…

Use when planning a VoidCrawl change that may cross Rust core, PyO3, Python API, MCP, docs, or tests.

Use when starting work in VoidCrawl or mapping Rust core, PyO3 bindings, Python package, MCP server, tests, or docs before editing.

Use when deciding how to validate a VoidCrawl change across Rust, Python, bindings, and browser-dependent tests.

Use when planning a QScrape change that may affect scraper benchmarks, level behavior, framework parity, or site data.

Use when starting work in QScrape or mapping the relevant L1, L2, L3, framework, or site-specific area before editing.

Use when deciding how to validate a QScrape change across build, lint, and scraper-visible behavior.

Use when planning a CascadingLabsFE change before editing pages, docs, components, styling, or metadata.

Use when starting work in CascadingLabsFE or deciding which site, docs, component, or styling areas to inspect first.

Use when deciding how to validate a CascadingLabsFE change with formatting, build, preview, or Lighthouse checks.

Use when planning an Assets change before editing logos, generated outputs, QR codes, or reusable templates.

Use when starting work in Assets or mapping the relevant design-token, asset, QR, or template area before editing.

Use when deciding how to validate an Assets change with regeneration, visual inspection, or template review.

Use when turning a requested change into a scoped implementation approach before editing files.

Use when starting work in this repository, mapping the codebase, or deciding which committed project docs and modules to inspect first.

Use when deciding what evidence is needed to show a change is correct and safe before or after implementation.

Use when planning a CLWorkstation change before editing playbooks, roles, vars, or test scenarios.

Use when starting work in CLWorkstation or mapping the relevant playbook, role, vars, or molecule area before editing.

Use when deciding how to validate a CLWorkstation change with dry-runs, molecule, or targeted role checks.