karpathy-guidelines

Apply behavioral guidelines to reduce LLM coding mistakes during code tasks.

Updated May 1, 2026
One-click install
npx skills add https://github.com/oguzhanguvenkaya/oguzhan_claude_code_configurations --skill karpathy-guidelines-oguzhanguvenkaya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: karpathy-guidelines
Source: https://github.com/oguzhanguvenkaya/oguzhan_claude_code_configurations/tree/main/skills/karpathy-guidelines
Command: npx skills add https://github.com/oguzhanguvenkaya/oguzhan_claude_code_configurations --skill karpathy-guidelines-oguzhanguvenkaya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Behavioral guidelines to reduce common LLM coding mistakes, derived from Andrej Karpathy's observations on LLM coding pitfalls. This collection helps teams write, review, and refactor code with caution, surface hidden assumptions, and define verifiable success criteria to avoid overcomplication.

Core Features & Use Cases

  • Think before coding: explicitly state assumptions, surface tradeoffs, and present multiple interpretations when unsure.
  • Simplicity first: require the minimal, robust solution with no unnecessary abstractions.
  • Surgical changes: modify only what is needed, preserve surrounding context, and avoid collateral edits.
  • Goal-driven execution: transform tasks into measurable goals and loop on verification until criteria are met.
  • Use cases: during writing, reviewing, or refactoring code to reduce complexity and increase traceability.

Quick Start

Outline assumptions, surface tradeoffs, and apply the simplest verifiable change to a coding task.

Frequently Asked Questions about karpathy-guidelines

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

FAQPage Schema
How do I reduce LLM coding mistakes during code generation?

To reduce LLM coding mistakes, apply strict behavioral guidelines that enforce stating assumptions, planning step-by-step, and making minimal surgical changes. This surfaces hidden tradeoffs and prevents overcomplication by requiring verifiable success criteria for every task.

What are the best practices for LLM code review and refactoring?

Best practices for LLM code review involve checking for minimal surgical changes, verifying measurable outcomes, and surfacing hidden assumptions. Goal-driven execution ensures tasks transform into measurable goals, looping on verification until defined success criteria are met.

Can I use these coding guidelines to prevent unnecessary abstractions in generated code?

Yes, you can use these guidelines to prevent unnecessary abstractions by enforcing a simplicity-first rule. They require the minimal, robust solution for coding tasks, explicitly avoiding overcomplication and collateral edits to preserve surrounding context.

When do I need to define verifiable success criteria for LLM coding tasks?

You need to define verifiable success criteria whenever executing LLM coding tasks to ensure goal-driven execution. Transforming tasks into measurable goals allows you to loop on verification until criteria are met, preventing complex, untraceable code generation.

Why does my LLM generated code include unintended collateral edits?

Unintended collateral edits occur when LLMs lack strict surgical change guidelines. Applying behavioral rules ensures the model modifies only what is needed, preserves surrounding context, and avoids unnecessary abstractions during refactoring or writing code.