karpathy-guidelines

Applies behavioral guidelines to reduce common LLM coding mistakes during code writing and review.

1|Updated Jun 25, 2026
One-click install
npx skills add https://github.com/curtismu7/AI-DEMO2 --skill karpathy-guidelines-curtismu7
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: karpathy-guidelines
Source: https://github.com/curtismu7/AI-DEMO2/tree/main/.claude/skills/karpathy-guidelines
Command: npx skills add https://github.com/curtismu7/AI-DEMO2 --skill karpathy-guidelines-curtismu7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? LLM coding assistants often overcomplicate solutions, make sweeping unrequested changes, hide assumptions, and lack verifiable success criteria. This Skill provides behavioral guidelines that keep AI-generated code simple, surgical, and goal-driven. ## Core Features & Use Cases - Think Before Coding: Surfaces assumptions, presents alternative interpretations, and stops to ask when requirements are unclear. - Simplicity First: Enforces minimum code that solves the problem, rejecting speculative abstractions and unrequested configurability. - Surgical Changes: Restricts edits to only what the task requires, matching existing style and avoiding unrelated refactors. - Goal-Driven Execution: Transforms vague tasks into verifiable success criteria with test-driven loops. - Use Case: When asking an AI agent to fix a bug in a large repository, the guidelines ensure it writes a reproducing test first, changes only the relevant lines, and verifies the fix rather than refactoring surrounding code. ## Quick Start Ask the AI to apply the karpathy-guidelines skill while implementing or reviewing your next code change.

Frequently Asked Questions about karpathy-guidelines

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stop an AI coding assistant from overcomplicating code?▼

Apply simplicity-first guidelines that require the minimum code solving the problem, ban speculative abstractions and unrequested configurability, and prompt a rewrite when a 200-line solution could be 50 lines.

How to make AI code changes surgical instead of refactoring everything?▼

Use surgical-change rules: touch only what the task requires, match existing style, never refactor working adjacent code, and remove only dead code your own changes orphaned. Every changed line should trace to the user's request.

What are Karpathy's guidelines for LLM coding mistakes?▼

They are behavioral rules derived from Andrej Karpathy's observations on LLM coding pitfalls, covering four areas: think before coding, simplicity first, surgical changes, and goal-driven execution with verifiable success criteria.

When should I not use these coding guidelines?▼

The guidelines bias toward caution over speed, so for trivial tasks you should use judgment rather than applying the full process. They are most valuable for multi-step or ambiguous coding work.

How do I define verifiable success criteria for AI coding tasks?▼

Transform vague goals into testable checks: turn 'fix the bug' into 'write a test that reproduces it, then make it pass'. For multi-step work, state a brief plan pairing each step with a verification check.