web-clone

Redirect legacy website cloning requests to the Visual Forge workflow.

2|Updated May 3, 2026
One-click install
npx skills add https://github.com/JustineDevs/roblox-ai-os --skill web-clone-justinedevs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-clone
Source: https://github.com/JustineDevs/roblox-ai-os/tree/main/skills/web-clone
Command: npx skills add https://github.com/JustineDevs/roblox-ai-os --skill web-clone-justinedevs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill serves as a historical reference for legacy URL-driven website cloning workflows that have been superseded by more modern visual-delivery systems.

Core Features & Use Cases

  • Legacy Routing: Provides guidance on migrating deprecated cloning tasks to current standards.
  • Workflow Consolidation: Ensures that visual implementation, mockup generation, and site cloning are handled by a unified system.
  • Use Case: If you encounter an old instruction to use this skill, you should instead route your request to the Visual Forge system to ensure proper visual fidelity and functional parity.

Quick Start

Reroute your website cloning request to the visual-forge skill to ensure your project uses the current implementation pipeline.

Frequently Asked Questions about web-clone

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate a deprecated website cloning workflow to a new system?

To migrate a deprecated website cloning workflow, route your URL-driven visual implementation tasks to the unified Visual Forge system to ensure proper visual fidelity and functional parity.

What is the visual-forge workflow used for in web cloning?

The visual-forge workflow is used for consolidating visual implementation, mockup generation, and site cloning into a unified system to ensure consistent visual delivery.

Do I need to use the web-clone skill for URL-driven visual implementation tasks?

You do not need to use the web-clone skill for URL-driven visual implementation tasks, as it only provides a deprecation notice and migration path to the supported Visual Forge workflow.

Why is my legacy website cloning operation no longer supported?

Legacy website cloning operations are no longer supported because they have been superseded by modern visual-delivery systems that provide better consistency in visual delivery.

What is the best way to handle historical archive references for legacy site cloning?

The best way to handle historical archive references for legacy site cloning is to use them as a deprecation guide to transition your tasks to the modern architectural patterns in Visual Forge.

Can I still generate mockups using the old website cloning workflow?

You cannot generate mockups using the old website cloning workflow; you must reroute your website cloning request to the visual-forge skill to use the current implementation pipeline.