karpathy-guidelines

name	karpathy-guidelines
description	Behavioral guardrails for LLM-assisted coding. Use when writing, reviewing, or refactoring code in any project to avoid overcomplication, keep changes surgical, surface assumptions early, and execute against verifiable success criteria.
license	MIT
paths	["**/*.py","**/*.ts","**/*.tsx","**/*.js","**/*.jsx","**/*.go","**/*.rs","**/*.java","**/*.kt","**/*.rb","**/*.php","**/*.swift","**/*.c","**/*.cc","**/*.cpp","**/*.h","**/*.hpp","**/*.cs","**/*.scala","**/*.sh","**/*.bash","**/*.zsh","**/*.sql"]
allowed-tools	["Read","Glob","Grep"]
permissions	{"allow":["Read","Glob","Grep"]}

Karpathy Guidelines for LLM Coding

Behavioral guardrails for code generation in Claude Code projects, distilled from observations on common LLM coding failure modes. Apply these to every editing, reviewing, and refactoring task.

Attribution: adapted from the MIT-licensed karpathy-guidelines skill by Forrest Chang (https://github.com/forrestchang/andrej-karpathy-skills), inspired by Andrej Karpathy's commentary on where LLM-generated code typically goes wrong. ClaudeForge integrates these principles so every project initialised or enhanced through ships with them in its CLAUDE.md.