Clone website guide
Skill radustefandumitru/overdrive/skills/clone-website-guide
Improve your AI coding agents easily.
npx -y skills add radustefandumitru/overdrive --skill clone-website-guideAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 13 stars13 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Safely guide authorized website rebuilds and visual recreations from a URL, including when to use JCodesMore's ai-website-cloner-template as a fresh project template. Use for "clone this website", "rebuild this landing page", "make a site like this", or "replicate this design" requests.
SKILL.md
3.5 KB, as published. Nobody here has run it
Clone Website Guide
Use this skill when the user wants to rebuild, recreate, or closely reference a website from a URL or screenshot.
The goal is to help users make legitimate, authorized rebuilds and design-inspired implementations without phishing, impersonation, asset theft, or trademark misuse.
Permission Gate
Before cloning or closely reproducing a site, establish one of:
- The user owns the site.
- The user has permission from the owner/client.
- The site is their competitor/reference and the goal is structural inspiration, not copying.
- The task is educational and the output will be clearly non-deceptive.
Refuse or redirect requests that are primarily for phishing, credential collection, impersonation, bypassing paywalls, brand spoofing, or deceptive copies of banks, marketplaces, login portals, crypto services, government portals, or other sensitive services.
Choose The Right Path
Path A: Fresh Template Flow
Use this when the user explicitly wants to use JCodesMore/ai-website-cloner-template or is starting from scratch.
- Tell the user this is a full project template, not a portable global skill.
- Start from a fresh repo/project created from the template, following the template's current README.
- Use only public/authorized URLs.
- Keep generated assets and copied text legally safe.
- After generation, run normal Overdrive review: accessibility, responsive behavior, performance, and brand/legal cleanup.
Do not force this template into an existing app unless the user wants a separate prototype that will be manually ported.
Path B: Existing Project Rebuild
Use this for most Overdrive work in an existing repo.
Recommended sequence:
design-extractfor page structure, styles, screenshots, and design tokens where lawful.site-architecturefor page/component structure.redesign-existing-projectsif integrating into an existing app.design-taste-frontend,impeccable,high-end-visual-design, ormodern-web-guidancefor quality.playwright-clifor visual/browser verification.seo-audit,cro, orpage/copy skills only if the rebuild includes content/marketing work.
Path C: Inspiration-Only
Use this when the target is a third-party site without permission.
- Extract layout patterns, interaction ideas, IA, and visual principles.
- Use new brand, copy, colors, assets, and product positioning.
- Avoid duplicating logos, proprietary illustrations, exact copy, protected trade dress, or distinctive branded combinations.
Output Contract
For URL-based rebuild requests, produce:
- permission/safety classification
- recommended path: fresh template, existing project rebuild, or inspiration-only
- required inputs: target URL, screenshots, brand assets, desired framework, pages, and fidelity level
- implementation plan
- legal/brand constraints
- verification checklist
Verification Checklist
- The site cannot be mistaken for the original owner if it is not owned/authorized.
- No login or payment collection is copied deceptively.
- No proprietary images, logos, fonts, or testimonials are used without rights.
- The build is responsive, accessible, and performant.
- The user can explain what changed from the source and why.