TL;DR
A single CLAUDE.md file inspired by Andrej Karpathy's observations about LLM coding mistakes gained 24,000 GitHub stars in one week. Here is what it teaches and why it resonated.
Read next
Matt Pocock's Claude Code skills library picked up 3,372 GitHub stars on a single day. Here's what's inside, how to install it, and whether the skills hold up in real projects.
5 min readobra/superpowers is a structured 7-stage development methodology for AI coding agents, installable directly in Claude Code, Cursor, and Gemini CLI - and trending hard with 173,000 GitHub stars.
6 min readA four-principle CLAUDE.md distilling Andrej Karpathy's observations on LLM coding mistakes gained 44k stars in a single week - and is now installable as a Claude Code plugin in two commands.
6 min readThe andrej-karpathy-skills repository crossed 102,000 GitHub stars this week, adding roughly 24,000 in seven days alone - numbers that rival established frameworks with years of community investment. The repository is a single CLAUDE.md file. No library. No CLI. No npm package. Just a set of behavioral guidelines for Claude Code, distilled from observations about recurring mistakes LLMs make when writing code.
The star velocity tells you something concrete: developers are actively looking for ways to make AI coding assistants behave more predictably, and a well-articulated behavioral file - structured as a Claude Code skill - is apparently the answer many of them were missing.
The repository contains guidelines organized around four principles, each targeting a specific failure mode in AI-assisted development.
The first principle is Think Before Coding. Rather than jumping to a solution, the guidelines instruct Claude Code to state its assumptions explicitly, present multiple interpretations when a request is ambiguous, and ask for clarification rather than guessing. This directly addresses the silent-assumption problem - where an AI confidently produces code based on an unstated assumption that turns out to be wrong, leaving you with output that solves a problem you did not have.
The second principle is Simplicity First. The guidelines push Claude Code toward writing only the minimum code needed for the task. No speculative features. No unnecessary abstractions. No premature generalization. This runs counter to what many default system prompts encourage - comprehensive, extensible, future-proofed code - but it aligns with how experienced engineers actually want to collaborate with an AI: do the small thing well, then do the next small thing.
Third is Surgical Changes. The rule is direct: edit only what was requested. Match the existing code style. Do not refactor code that was not broken. Do not touch dead code adjacent to the area you are working in. This one matters enormously in production codebases, where unrelated edits introduce unpredictable regressions that take far longer to debug than the original task took to complete.
Fourth is Goal-Driven Execution. Before starting work, define verifiable success criteria. Establish a testing loop rather than a vague directive like "make this better" or "clean this up." If you cannot describe what done looks like in observable terms, do not start coding.
Together these four principles form a behavioral contract that guides Claude Code toward focused, minimal, verifiable work - the kind that experienced developers actually want from an AI collaborator.
Get the weekly deep dive
Tutorials on Claude Code, AI agents, and dev tools - delivered free every week.
From the archive
Apr 29, 2026 • 11 min read
Apr 29, 2026 • 11 min read
Apr 29, 2026 • 10 min read
Apr 29, 2026 • 12 min read
There are three ways to use this repository.
The fastest path is the Claude Code plugin marketplace. With Claude Code installed, run:
/plugin install andrej-karpathy-skills@karpathy-skills
This installs the skill globally. All four guidelines activate immediately for every project you open.
For per-project use, download the CLAUDE.md file directly and drop it in your project root:
curl -o CLAUDE.md https://raw.githubusercontent.com/forrestchang/andrej-karpathy-skills/main/CLAUDE.md
Your project-level CLAUDE.md takes effect the next time you start a Claude Code session in that directory. If your project already has a CLAUDE.md, you can append the relevant sections rather than replacing the whole file.
If you use Cursor, the repository also includes .cursor/rules/karpathy-guidelines.mdc - the same four principles formatted for Cursor's rules system.
The full install takes under a minute. There is no configuration, no API key, and no additional account required.
This is most valuable for developers who have been using Claude Code for more than a few weeks and have started noticing patterns in where it goes wrong.
If you have ever asked for a small fix and watched Claude Code rewrite three unrelated functions, the Surgical Changes principle addresses that directly. If you have watched it build a solution around an assumption it never surfaced to you, Think Before Coding is the fix. If it has handed you a 300-line abstraction when you asked for a simple utility function, Simplicity First will feel immediately useful.
It is also valuable for teams standardizing how Claude Code behaves across a shared codebase. Dropping the CLAUDE.md into a repository means every team member - and every Claude Code session in that repo - operates from the same behavioral baseline. This is the practical implementation of the "AI engineering standards" conversation that many teams are having but few have actually written down and committed to version control.
For developers newer to Claude Code, the four principles also serve as a useful orientation. They describe what good AI-assisted coding looks like from the perspective of the engineer in the loop - explicit about scope, minimal in implementation, and grounded in verifiable outcomes.
DevDigest has covered the Claude Code skills ecosystem in depth - from the basics of what skills are to building custom workflows and using the skills marketplace. The andrej-karpathy-skills repository is a natural part of that landscape. It is a skill in the technical sense: a CLAUDE.md file that extends and refines Claude Code behavior without requiring changes to your project's source code.
If you are building your own skills or customizing Claude Code for your team, the four-principle structure here is worth studying as a design pattern. Explicit assumptions, minimal scope, surgical edits, verifiable goals - these map directly onto the questions you face when writing any skill intended for repeated use across diverse projects.
The broader skills directory at skills.developersdigest.tech includes Claude Code skills available through the marketplace, organized by category. For generating a CLAUDE.md tailored to your own project - stack, conventions, and team constraints - the CLAUDE.md generator at developersdigest.tech/claudemd-generator gives you a structured starting point. The Karpathy behavioral guidelines layer cleanly on top of whatever project-specific instructions you produce there.
For teams building with MCP servers alongside Claude Code - documented at mcp.developersdigest.tech - these principles extend naturally. An MCP server whose tools follow the same behavioral contract as your CLAUDE.md - minimal, explicit, verifiable - creates a more consistent development experience end to end.
The star velocity is genuine, but some context is useful.
The underlying principles are not novel. Minimal viable changes, explicit assumptions, and verifiable success criteria are software engineering fundamentals that predate LLMs by decades. What this repository does is package them as a CLAUDE.md, which means they reach Claude Code directly as behavioral instructions rather than sitting in a developer's mental checklist that gets forgotten under deadline pressure.
The practical impact depends on your current setup. If your existing CLAUDE.md or project instructions already cover these patterns, you will find limited additional value here. If you have been using Claude Code with no behavioral guidelines at all, this is a well-reasoned starting point.
One genuine limitation: the file is static. It does not adapt to your codebase's specific patterns, your team's conventions, or your technology stack. The four principles are general enough to apply broadly, but they do not know that your project uses a specific state management pattern, avoids a particular library, or requires certain testing conventions. For teams with specialized needs, this is better treated as a foundation to build on than a complete solution.
The 102,000 stars reflect real demand. Developers want Claude Code to behave more predictably, and behavioral configuration files are currently the most direct path to that. Whether this specific file is the one you use or the one that inspires a better version for your context, that demand is worth taking seriously.
Technical content at the intersection of AI and development. Building with AI agents, Claude Code, and modern dev tools - then showing you exactly how it works.
Anthropic's agentic coding CLI. Runs in your terminal, edits files autonomously, spawns sub-agents, and maintains memory...
View ToolInteractive TUI dashboard that shows exactly where your Claude Code and Cursor tokens are going, in real time.
View ToolAnthropic's flagship reasoning model. Best-in-class for coding, long-context analysis, and agentic workflows. 1M token c...
View ToolThe original AI coding assistant. 77M+ developers. Inline completions in VS Code and JetBrains. Copilot Workspace genera...
View ToolEvery coding agent in one window. Stop alt-tabbing between Claude, Codex, and Cursor.
View AppTurn a one-liner into a working Claude Code skill. From idea to installed in a minute.
View AppUnlock pro skills and share private collections with your team.
View AppConfigure Claude Code for maximum productivity -- CLAUDE.md, sub-agents, MCP servers, and autonomous workflows.
AI AgentsPrefix prompts with ! to run shell commands directly, bypassing Claude.
Claude CodeExecute shell commands with persistent working directory in project bounds.
Claude Code
Nimbalyst Demo: A Visual Workspace for Codex + Claude Code with Kanban, Plans, and AI Commits Try it: https://nimbalyst.com/ Star Repo Here: https://github.com/Nimbalyst/nimbalyst This video demos N...

Composio: Connect AI Agents to 1,000+ Apps via CLI (Gmail, Google Docs/Sheets, Hacker News Workflows) Check out Composio here: http://dashboard.composio.dev/?utm_source=Youtube&utm_channel=0426&utm_...

Anthropic has released Channels for Claude Code, enabling external events (CI alerts, production errors, PR comments, Discord/Telegram messages, webhooks, cron jobs, logs, and monitoring signals) to b...
obra/superpowers picked up 1,600+ GitHub stars in a single day by solving the real problem with coding agents - they ski...
Matt Pocock's Claude Code skills library picked up 3,372 GitHub stars on a single day. Here's what's inside, how to inst...
Matt Pocock's .claude skills directory hit 74.7k GitHub stars, offering structured workflows that address the four most...
Matt Pocock released production-ready agent skills straight from his .claude directory. With 66k stars and 16k added thi...
The mattpocock/skills repository hit 62k stars on GitHub's weekly trending list with 17 composable Claude Code agent ski...
obra/superpowers is a composable, opinionated methodology for AI coding agents - structured workflows covering planning,...

New tutorials, open-source projects, and deep dives on coding agents - delivered weekly.