recreate
Recreate a website from a link
Input: one URL ($ARGUMENTS). Follow the phases in order; do not skip the evidence steps.
Phase 0 — Study-build terms (mandatory, every run)
This is a local study build: recreate the reference exactly — layout, text, images, fonts, audio, motion. In exchange, every output MUST ship the disclaimer:
- README.md in the build must state, prominently: the design, copy, images, fonts and audio belong to the original owners; this build is a private study/reference recreation; it must not be deployed, published, sold, or presented as your own work; publishing requires replacing every borrowed asset (list them) and obtaining licenses.
- Header comment in the HTML repeats the same notice in one line.
- Provenance list: every borrowed asset path + source URL enumerated in the README.
- If the user later wants to publish, that is a separate brief: replace assets → publish. Never quietly drop the disclaimer.
Scope: whole page or specific sections? A continuous scroll-narrative (fixed stage + long spacer) is one unit — do not force per-section pages onto it. Target: single-file build by default; conversion is offered after QA, never assumed (see Phase 4).
Phase 1 — Evidence (free MCP, all read-only)
Any URL works, but check Awwwards first. Step 1 is always
search_siteswith the site's domain/name. If the site is listed →get_site_detailsfor its recorded DNA (palette, tech, elements, awards) and carry that into the report. If no match → say so once and continue: only the search/index tools are Awwwards-sourced; every capture tool below runs on any public link, and the live evidence still gives you everything.