karpathy-guidelines

Apply Karpathy-style behavioral guidelines to code writing, review, and refactoring.

5|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/kenlck/skills --skill karpathy-guidelines-kenlck
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: karpathy-guidelines
Source: https://github.com/kenlck/skills/tree/main/ken-swe/skills/karpathy-guidelines
Command: npx skills add https://github.com/kenlck/skills --skill karpathy-guidelines-kenlck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Behavioral guidelines help teams avoid common LLM coding mistakes by surfacing assumptions, enforcing simplicity, and guiding surgical changes.

Core Features & Use Cases

  • Think Before Coding: surface assumptions and ask clarifying questions.
  • Simplicity First: keep solutions minimal and avoid unnecessary abstractions.
  • Surgical Changes: modify only what's needed, preserving existing behavior elsewhere.
  • Goal-Driven Execution: define verifiable success criteria and loop until satisfied.

Quick Start

Consider a coding task and apply the four rules: state assumptions, choose the simplest solution, modify only necessary code, and define measurable 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 prevent LLM coding mistakes during refactoring?

To prevent LLM coding mistakes during refactoring, apply behavioral guidelines that surface assumptions, enforce simplicity, and guide surgical changes. This ensures modifications remain minimal and existing behavior is preserved.

What is the best way to keep LLM generated code simple and avoid unnecessary abstractions?

The best way to keep LLM generated code simple is to enforce a simplicity-first guideline that chooses minimal solutions and avoids unnecessary abstractions during the code generation and review process.

How do I make surgical code changes with an LLM without breaking existing behavior?

To make surgical code changes with an LLM without breaking existing behavior, apply guidelines that modify only necessary code while explicitly preserving all other existing functionality elsewhere in the codebase.

Why does my LLM coding task lack verifiable success criteria?

Your LLM coding task lacks verifiable success criteria because it requires goal-driven execution guidelines to define measurable outcomes and loop until the code satisfies those specific goals.

Can I use these coding guidelines for both writing and reviewing code?

Yes, you can use these coding guidelines for both writing and reviewing code. They are applicable during either process to surface assumptions, keep changes surgical, and define verifiable success criteria.

When do I need to surface assumptions before an LLM writes code?

You need to surface assumptions before an LLM writes code when facing complex requirements, utilizing a think-before-coding guideline to ask clarifying questions and state explicit assumptions before execution.