super-extractionlisted

Forensic website extraction — tear down any website, web app, or landing page into a full local source mirror + reference screenshots + a TEARDOWN.md complete enough that an engineer who has never seen the site could rebuild it pixel-for-pixel. Curl-first capture, deep code read (every constant, shader, easing, breakpoint), live browser verification, licensing flags, 1:1 rebuild checklist. Triggers: "extract this website", "tear down / teardown this site", "reverse engineer this landing page / app / UI", "break it down pixel by pixel", "pick it apart piece by piece", "replicate this design/site" (extraction is always step 1 of replication), "super extraction", "every inch and pixel", "how does this site work under the hood". NOT for: simple screenshots or scraping text (that's vbt-browse-op); building UI from a taste spec (a UI-builder skill); aesthetic-only decoding (a design-taste skill) — this is engineering forensics: code + behavior + assets, not just visual taste. Deliverable = TEARDOWN.md + full local
vb-tyagi/OP-teardown-any-website-skill · ★ 0 · Web & Frontend · score 70

Install: claude install-skill vb-tyagi/OP-teardown-any-website-skill

# VBT Super Extraction — Forensic Website Teardown Tear a live website apart into a spec so complete that an engineer who has never seen it could rebuild it pixel-for-pixel. Source code is truth; screenshots only verify. Deliverable lives inside the current project: ``` <project>/replica-<slug>/ TEARDOWN.md # the canonical spec (section skeleton in Phase 4) original-source/ # full mirror — HTML, CSS, JS, every asset, site's own layout reference-screenshots/ # numbered states: 01-default, 02-…, NN-mobile ``` > **Reference output shape** — a `replica-<slug>/` folder containing `TEARDOWN.md`, > `original-source/` and `reference-screenshots/`. The worked example referenced > throughout this doc is a WebGL tarot site teardown produced with exactly this method. --- ## Phase 0 — Superprompt framing (before touching the site) Write (mentally, or via /superprompt if the user invoked it) a one-paragraph objective with a definition of done: **"a teardown complete enough that an engineer who has never seen the site could rebuild it pixel-for-pixel."** Pin the truth rules up front: - Every number in the spec comes from actual source code or a live browser measurement — NOTHING eyeballed from screenshots. - Unconfirmable values get labeled **unverified** — and that label survives into the final doc. - If a behavior can't be replicated (server-side, missing asset), say so plainly. Pin assumptions visibly: where the mirror lives, whether original assets a