karpathy-guidelines

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

Updated May 7, 2026
One-click install
npx skills add https://github.com/Pieter-1337/Euricom-tsz --skill karpathy-guidelines-pieter-1337
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: karpathy-guidelines
Source: https://github.com/Pieter-1337/Euricom-tsz/tree/main/.claude/skills/karpathy-guidelines
Command: npx skills add https://github.com/Pieter-1337/Euricom-tsz --skill karpathy-guidelines-pieter-1337

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? LLM coding assistants often overcomplicate solutions, make sweeping unrequested changes, hide confusion, and lack verifiable success criteria. This Skill provides behavioral guidelines, derived from Andrej Karpathy's observations on LLM coding pitfalls, that keep AI-generated code simple, surgical, and goal-driven. ## Core Features & Use Cases - Think Before Coding: Forces explicit statement of assumptions, surfaces multiple interpretations, and stops to ask when requirements are unclear. - Simplicity First: Enforces minimum code that solves the problem, rejecting speculative abstractions, unrequested configurability, and impossible-scenario error handling. - Surgical Changes: Restricts edits to only what the request requires, matching existing style and cleaning up only orphans created by the current change. - Goal-Driven Execution: Transforms vague tasks into verifiable success criteria with test-first loops and step-by-step verification plans. - Use Case: When asking an AI to fix a bug or add a feature, activate these guidelines so the assistant writes a reproducing test first, makes the minimal change, and avoids refactoring unrelated code. ## Quick Start Ask the assistant to apply the karpathy-guidelines skill while implementing your next code change so it states assumptions, keeps the diff minimal, and defines verifiable success criteria.

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 ask whether a senior engineer would call the result overcomplicated before accepting it.

How to make an LLM make surgical code changes only?

Instruct the assistant to touch only what the request requires, match existing style, avoid refactoring adjacent code, and remove only imports or variables its own changes orphaned. Every changed line should trace directly 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 every rule. They are most valuable for non-trivial changes where scope creep and hidden assumptions cause real problems.

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

Transform vague tasks into testable goals, such as writing a failing test that reproduces a bug before fixing it, or ensuring tests pass before and after a refactor. For multi-step work, state a brief plan with a verification check per step.