JCodesMore/ai-website-cloner-template

This repository is a template plus an Agent Skill that lets a supported AI coding agent recreate a website as a local Next.js project. It is aimed at people who want real source code for a site they own or are authorized to rebuild — for a platform migration, a lost repository, or studying how a production page achieves its layout and motion. It is not a hosted cloning service; the work happens in your own project folder through the agent.

How it works

The /clone-website skill follows four stages: map source URLs to local routes without overwriting existing work; observe desktop and mobile pages, pull real assets and fonts, and exercise alternate states; build editable components with working interactions; then compare source and local pages at matched sizes and states and run the production check. Framer pages and animated sites get specific guidance for responsive variants, sticky scenes and scroll- or time-driven motion. The agent finishes with route mappings, run instructions, comparison screenshots and a list of remaining gaps, so you can see what differs rather than trusting a one-shot result.

The scaffold is Next.js 16 with React 19, TypeScript strict, shadcn/ui and Tailwind CSS v4; source-specific components and assets are kept under sites/<site> folders and research notes under docs/research/.

Supported agents and requirements

Claude Code with Opus 5.5 is the recommended path; Codex CLI, Cursor and OpenCode are also listed as supported. The Agent Skill lives in .agents/skills/clone-website/ and is read directly by Codex, Cursor and OpenCode, while Claude Code uses a thin command bridge so /clone-website still works. In every path you need Node.js 24+ and a coding agent with browser access enabled, because inspection and comparison depend on viewing the pages. Setup can be started by pasting a prompt into your agent or by creating a copy from the GitHub template, then installing dependencies and running npm run check — see the quick start and supported platforms. Optional Docker commands exist for building and running the app.

Constraints

MIT licensing covers the template itself, but logos, brand assets and original copy remain their owners' property; the README explicitly rules out passing off someone's design as your own. It also excludes phishing or impersonation and warns that some sites prohibit scraping or reproduction in their terms of service, which should be checked before cloning. The author states these boundaries but does not provide a technical enforcement or legal review mechanism.

HotRepo's take

The repository had a fast-tracked presence on the GitHub daily board between June and October 2026, but recorded board days alone do not demonstrate lasting adoption or output quality. The documented fit is narrow and concrete: you have a site you may lawfully rebuild, you use one of the named agents, and you want a maintainable Next.js codebase rather than a static screenshot copy.