agentleFS
Sign inStart free
444Nazky444Nazky/ai-cloner/AGENTS.md

ai-cloner

AGENTS.md0 starsChanged 8 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 --> @docs/research/INSPECTION_GUIDE.md

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. gokulgk6798-afk/Claude_skill★ 0100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • 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 31,439 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.

The file

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

2 rules. About 0 are common, 0 are distinctive, and 2 are 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.

  • 2

    Very specific

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

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

    After editing AGENTS.md, run bash scripts/sync-agent-rules.sh to regenerate platform-specific instruction files.

    line 62
  2. Very specific:

    After editing .claude/skills/clone-website/SKILL.md, run node scripts/sync-skills.mjs to regenerate the skill for all platforms.

    line 63

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 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 -->

Website Reverse-Engineer Template

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 — just run /clone-website <url1> [<url2> ...].

Tech Stack

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

Commands

  • 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

Code Style

  • TypeScript strict mode, no any
  • Named exports, PascalCase components, camelCase utils
  • Tailwind utility classes, no inline styles
  • 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/            # Asset download scripts

MOST IMPORTANT NOTES

  • When launching Claude Code agent teams, ALWAYS have each teammate work in their own worktree branch and merge everyone's work at the end, resolving any merge conflicts smartly since you are basically serving the orchestrator role and have full context to our goals, work given, work achieved, and desired outcomes.
  • After editing AGENTS.md, run bash scripts/sync-agent-rules.sh to regenerate platform-specific instruction files.
  • After editing .claude/skills/clone-website/SKILL.md, run node scripts/sync-skills.mjs to regenerate the skill for all platforms.

@docs/research/INSPECTION_GUIDE.md

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