Karpathy on Claude Code
10 articles in series
Ten essays on Andrej Karpathy's practices, philosophy, and influence on Claude Code — from Software 3.0 to the single distilled skill that encodes his coding guidelines.
The 'Build it from Scratch' Discipline in the Age of Skills
Karpathy's pedagogy prizes building from first principles. The Claude Code skills ecosystem prizes install-and-ship. These aren't in conflict — but the tension is real and worth naming.
CLAUDE.md as Context Engineering: Why Karpathy's Practice Matters
CLAUDE.md files have become the standard context-injection point for Claude Code projects. Karpathy's coding guidelines show exactly why the practice is more powerful than it looks.
From nanoGPT to Claude Skills: The Pedagogy of Karpathy's Public Code
Karpathy's 'build it from scratch' lineage — nanoGPT, micrograd, makemore — encodes a theory of understanding that ports directly into how the best Claude skills are designed.
Karpathy on Agents: His Public Takes on Autonomous Coding
Karpathy named December 2025 as the inflection point for agentic coding. Here's his actual framework for thinking about agents, the limits he flags, and what it means for Claude Code workflows.
The Karpathy Skills Repo: A One-Skill Field Guide
The multica-ai/andrej-karpathy-skills repo contains exactly one skill. That single-skill design is itself a statement about how to write useful AI guidance.
Reading Karpathy's Guidelines: What His One Skill Reveals
A close reading of the karpathy-guidelines skill — four rules, 65 lines, no ceremony. What each rule actually does and why the structure matters.
Karpathy's Skill Authoring Style: Distillation Over Accretion
The karpathy-guidelines skill is 65 lines. The Hermes superbundle is 144 skills. These represent opposite theories of how to encode AI capability. Karpathy's approach has specific advantages worth understanding.
Software 3.0: Karpathy's Framework Applied to Claude Code
Karpathy's Software 1.0/2.0/3.0 framing maps cleanly onto how Claude Code skills, prompts, and agentic workflows actually work. Here's the translation.
Vibe Coding: Karpathy's Term, Its Evolution, and What It Means in 2026
Karpathy coined 'vibe coding' in February 2025. It became Collins' Word of the Year. By 2026, the term had split into two very different practices. Here's where it stands.
What's Missing from Karpathy's Approach (and Why That's the Lesson)
Karpathy's guidelines say nothing about testing strategy, team collaboration, or long-term codebase health. Those omissions are intentional — and they teach something important about scope.