agentleFS
abuzar310abuzar310/cloneforge/AGENTS.md

cloneforge

AGENTS.md1 starsChanged 3 months agoMITView on GitHub

This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in node_modules/next/dist/docs/ before writing any code. Heed deprecation notices. <!-- END:nextjs-agent-rules --> Cursor-first: Prefer Cursor’s built-in browser MCP (cursor-ide-browser) when available. Also works with Claude Code, Codex, Copilot, Windsurf, and other agents listed in the README. The default src/app/page.tsx is a CloneForge showcase landing. Replace it when cloning a target site. @docs/research/INSPECTION_GUIDE.md

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

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Cursor-first: Prefer Cursor’s built-in browser MCP (cursor-ide-browser) when available.

    line 12
  2. Distinctive:

    When launching parallel builder agents, prefer each teammate in their own worktree/branch.

    line 68
  3. Very specific:

    After editing AGENTS.md, run bash scripts/sync-agent-rules.sh (or npm run sync:agents) to regenerate platform-specific instruction files.

    line 69
  4. Very specific:

    After editing .claude/skills/clone-website/SKILL.md, run node scripts/sync-skills.mjs (or npm run sync:skills).

    line 70

≈ “Common” is an estimate: at least 1 in 5 of the 36,368 AGENTS.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
AGENTS.md
<!-- BEGIN:nextjs-agent-rules -->

This is NOT the Next.js you know

This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in node_modules/next/dist/docs/ before writing any code. Heed deprecation notices.

<!-- END:nextjs-agent-rules -->

CloneForge

What This Is

A reusable template for reverse-engineering any website into a clean, modern Next.js codebase using AI coding agents. The Next.js + shadcn/ui + Tailwind v4 base is pre-scaffolded — run /clone-website <url1> [<url2> ...].

Cursor-first: Prefer Cursor’s built-in browser MCP (cursor-ide-browser) when available. Also works with Claude Code, Codex, Copilot, Windsurf, and other agents listed in the README.

The default src/app/page.tsx is a CloneForge showcase landing. Replace it when cloning a target site.

Tech Stack

  • Framework: Next.js 16 (App Router, React 19, TypeScript strict)
  • UI: shadcn/ui (Base UI / Radix-style primitives, Tailwind CSS v4, cn() utility)
  • Icons: Lucide React (default — will be replaced/supplemented by extracted SVGs)
  • Styling: Tailwind CSS v4 with design tokens
  • Runtime: Node.js 20+
  • Deployment: Vercel

Commands

  • npm run setup — Node check + install
  • npm run dev — Start dev server
  • npm run build — Production build
  • npm run lint — ESLint check
  • npm run typecheck — TypeScript check
  • npm run check — Run lint + typecheck + build
  • npm run sync:skills — Regenerate /clone-website for all platforms

Code Style

  • TypeScript strict mode, no any
  • Named exports, PascalCase components, camelCase utils
  • Tailwind utility classes, no inline styles (except when matching extracted computed styles that Tailwind cannot express)
  • 2-space indentation
  • Responsive: mobile-first

Design Principles

  • Pixel-perfect emulation — match the target's spacing, colors, typography exactly
  • No personal aesthetic changes during emulation phase — match 1:1 first, customize later
  • Real content — use actual text and assets from the target site, not placeholders
  • Beauty-first — every pixel matters

Project Structure

src/
  app/              # Next.js routes
  components/       # React components
    ui/             # shadcn/ui primitives
    icons.tsx       # Extracted SVG icons as React components
  lib/
    utils.ts        # cn() utility (shadcn)
  types/            # TypeScript interfaces
  hooks/            # Custom React hooks
public/
  images/           # Downloaded images from target site
  videos/           # Downloaded videos from target site
  seo/              # Favicons, OG images, webmanifest
docs/
  research/         # Inspection output (design tokens, components, layout)
  design-references/ # Screenshots and visual references
scripts/            # setup + sync scripts

MOST IMPORTANT NOTES

  • When launching parallel builder agents, prefer each teammate in their own worktree/branch; merge at the end and resolve conflicts with full pipeline context.
  • After editing AGENTS.md, run bash scripts/sync-agent-rules.sh (or npm run sync:agents) to regenerate platform-specific instruction files.
  • After editing .claude/skills/clone-website/SKILL.md, run node scripts/sync-skills.mjs (or npm run sync:skills).
  • Credit upstream: see NOTICE.md (based on JCodesMore/ai-website-cloner-template).

@docs/research/INSPECTION_GUIDE.md

Download now (ZIP)

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 28,693 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository5 other files it gives its agents.

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.