ai-website-cloner-template: Give an AI coding agent a URL to recreate a website as a clean Next.js app.
What problem it solves
Web teams and developers can need to rebuild an existing site in a modern codebase when migrating platforms, recovering lost source code, or learning how a production site is constructed. This template gives an AI coding agent a repeatable workflow for recreating a site as an editable Next.js application while comparing its appearance and behavior with the source.
Key features
Four-stage cloning workflow — The `/clone-website` skill maps routes, observes source pages and states, builds editable components, and compares the result with the source.
Source: README
Responsive inspection and comparison — The workflow inspects desktop and mobile pages, exercises alternate states, and reviews source and local pages at matched sizes and states. It also includes focused guidance for responsive variants, media, sticky scenes, and scroll- or time-driven motion.
Source: README
Modern Next.js foundation — Cloned sites are produced in a Next.js application with the App Router, React, TypeScript strict mode, Tailwind CSS, and shadcn/ui primitives.
Source: README, next.config.ts
Support for multiple coding agents — The project provides a portable Agent Skill that Codex, Cursor, and OpenCode can read directly, plus a Claude Code command bridge for `/clone-website`.
Source: README, .agents/skills
Built-in validation commands — The package provides commands for development, production builds, linting, TypeScript checks, and a combined production check.
Source: README
Quick start
Copied verbatim from the project's README.
Set up https://github.com/JCodesMore/ai-website-cloner-template
as a standalone project in a new folder on my computer.
Ask me where to put it. Clone the repository, remove its origin remote,
install dependencies, and run npm run check. Leave it ready for me
to clone a website./clone-website https://example.comWho it may suit
This may suit developers and teams migrating owned websites, recovering lost source code, or studying site layouts and interactions through an editable Next.js codebase.
Topics to discuss
Which source pages and alternate states should the cloning workflow inspect first?
How should route mappings and comparison evidence be documented for complex sites?
What safeguards would help ensure recreated sites are used only for authorized purposes?
Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.
Read the original README https://github.com/JCodesMore/ai-website-cloner-template#readme
ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.
Comments
…