karpathy-guidelines

Apply Karpathy guidelines to coding tasks for explicit assumptions and verifiable steps.

1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/JamesClonk/ai-box --skill karpathy-guidelines-jamesclonk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: karpathy-guidelines
Source: https://github.com/JamesClonk/ai-box/tree/main/config/.config/opencode/skills/karpathy
Command: npx skills add https://github.com/JamesClonk/ai-box --skill karpathy-guidelines-jamesclonk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Karpathy guidelines provide a structured approach to avoid common LLM coding mistakes by enforcing explicit assumptions, minimal changes, and measurable success criteria.

Core Features & Use Cases

  • Explicit assumptions and surface tradeoffs before coding
  • Surgical changes that touch only what is broken
  • Goal-driven execution with verifiable steps
  • Guidelines for writing, reviewing, and refactoring code

Quick Start

Summarize a given code change by listing explicit assumptions, propose a minimal modification, and define 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 reduce common LLM coding mistakes when refactoring code?

Reduce common LLM coding mistakes by applying Karpathy guidelines to surface assumptions, make surgical changes, and define verifiable success criteria during writing, reviewing, or refactoring code.

What are the Karpathy guidelines for LLM coding best practices?

Karpathy guidelines for LLM coding best practices enforce explicit assumptions, surgical changes that touch only what is broken, and goal-driven execution with verifiable steps to ensure predictable, auditable outcomes.

How do I define verifiable success criteria for a coding task?

Define verifiable success criteria for a coding task by listing explicit assumptions, proposing a minimal modification, and establishing a clear plan with verifiable steps to ensure predictable, auditable outcomes.

When should I use explicit assumptions in code review?

Use explicit assumptions in code review to surface tradeoffs before coding, enforce minimal changes that touch only what is broken, and ensure predictable, auditable outcomes through goal-driven execution.

Do I need any specific frameworks to apply these coding guidelines?

No specific frameworks are required to apply these coding guidelines, as they operate as a structured approach to enforce explicit assumptions and minimal changes without any external dependencies.