agentleFS
Sign inStart free
MahanaicoachMahanaicoach/ai-site-cloner/CLAUDE.md

ai-site-cloner

CLAUDE.md31 starsChanged 3 months agoMITView on GitHub

Template for cloning any multi-page website into this Next.js codebase, then rebranding it as your own. Two skills drive everything: /clone-website <url> and /restyle. Clone sites you own or have permission to rebuild (platform migration, lost source, learning). Never for phishing, impersonation, or passing off someone's design as your own.

We split this CLAUDE.md into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    All extraction numbers come from scripts/ (computed styles, real column counts, pixel diffs) — never estimated by eye.

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 25,680 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

ai-site-cloner

Template for cloning any multi-page website into this Next.js codebase, then rebranding it as your own. Two skills drive everything: /clone-website <url> and /restyle.

Tech Stack

  • Next.js 16 — App Router, React 19, TypeScript strict
  • Tailwind CSS v4 + shadcn/ui (base-ui primitives), oklch tokens in src/app/globals.css
  • Lucide React icons (replaced by extracted SVGs in src/components/icons.tsx during cloning)
  • Playwright (devDependency) powers all extraction/QA scripts — Chromium auto-installs on the first script run (npm run setup to do it explicitly)

Commands

  • npm run dev / npm run build / npm run lint / npm run typecheck
  • npm run check — lint + typecheck + build (must pass before any commit)

Architecture Rules

  • Content lives in src/data/*.ts, never hardcoded in components. Components take props. This is what makes /restyle possible — copy swaps without touching layout.
  • Pages: src/app/<route>/page.tsx wires data → components. Shared header/footer mount in layouts.
  • docs/research/ holds extraction artifacts (JSON, specs, manifest) — auditable, never hand-edited except spec files.
  • docs/research/manifest.json is the pipeline state. The extraction/spec/QA scripts self-report their stage transitions; update built/merged manually. Check it first on any clone-related task (node scripts/manifest.mjs status).
  • Specs (docs/research/components/**/*.spec.md) must pass node scripts/lint-spec.mjs before any builder agent is dispatched.
  • All extraction numbers come from scripts/ (computed styles, real column counts, pixel diffs) — never estimated by eye.

Code Style

  • TypeScript strict, no any
  • Named exports, PascalCase components, camelCase utils
  • Tailwind utility classes; arbitrary values (text-[17px]) when the extracted value doesn't match Tailwind's scale
  • 2-space indentation

Ethics

Clone sites you own or have permission to rebuild (platform migration, lost source, learning). Never for phishing, impersonation, or passing off someone's design as your own.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free