superloopy-clone

# Superloopy Clone Reverse-engineer a target URL into a working local implementation with audit artifacts. Use this only for authorized cloning, migration, learning, or recovery work. Do not help with phishing, deceptive impersonation, credential capture, or evading a site's terms. When multiple URLs are provided, process each host independently. Keep every site's research, screenshots, assets, and evidence isolated under paths like `docs/research/<hostname>/`, `docs/design-references/<hostname>/`, and `.superloopy/evidence/website-clone/<hostname>/`. This is not "inspect once, then redraw." Act as the foreman: inspect one section, write the exact spec, dispatch or build that bounded slice, then keep extracting the next section while builders run. A hard section is where extraction gets stricter, not where approximation becomes acceptable. ## Reference Example Transferloom.com is a reference result for this workflow: `superloopy-clone` reproduced the page locally and passed desktop/mobile browser validation with preserved sticky navigation, animated hero, app preview sections, comparison table, security panel, sister app banner, footer, local assets, and a Superloopy evidence trail. Use that bar for completion claims. A clone is successful only when it has this shape of evidence: source screenshots, research notes, component specs, downloaded assets, local browser screenshots, validation output, visual QA notes, and a final evidence artifact. ## Superloopy Contract - ...