product-clone-research

Website workflow documentation for product cloning is automated by capturing authenticated route inventories and screenshots via chrome-mcp-based traversal, producing structured manifests for defensible product planning.

Route inventory mapping enumerates public and role-gated authenticated states across a target domain, generating structured manifests that validate clone coverage and define exact scope for product planning.

Yes, you can use chrome-mcp-based traversal to capture role-gated user flows, provided you supply the target domain, confirm the allowed scope, and define the role matrix and credential method beforehand to keep traversal within approved boundaries.

Coverage validation across public and authenticated states is performed using built-in guardrails that prevent bypassing authentication mechanisms, CAPTCHA, paywalls, robots restrictions, and storing plaintext credentials during traversal.

Limitations of automated web reconnaissance for product cloning include strict guardrails preventing bypassing authentication, CAPTCHA, paywalls, and robots restrictions, restricting traversal strictly to confirmed allowed scope boundaries.

Generating a clone-scope recommendation handoff prompt requires executing manifest-based action tracking during web reconnaissance, producing explicit unknowns, route/action manifests, and a ready-to-run prompt for downstream development.