karpathy-guidelines

Apply Karpathy guidelines to code writing, review, and refactoring tasks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Behavioral guidelines to reduce common LLM coding mistakes, derived from Andrej Karpathy's observations, empowering developers to avoid overcomplication, surface assumptions, and define verifiable success criteria.

Core Features & Use Cases

  • Explicit assumptions: Forces you to surface and record assumptions before coding.
  • Surgical changes: Encourages targeted edits that affect only the intended area, avoiding collateral changes.
  • Plan and verify: Promotes a plan-first workflow with measurable success criteria and testability.
  • Use Case: Teams using LLM-powered development can integrate these guidelines into code review prompts and refactoring tasks to improve correctness and reliability.

Quick Start

Instruct the AI to apply Karpathy Guidelines to the current task and surface any assumptions before coding.

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 and code generation?

To reduce LLM coding mistakes during refactoring, apply surgical coding guidelines that enforce explicit assumptions, plan-first workflows, minimal targeted edits, and measurable success criteria before code generation begins.

What are the best practices for minimizing risk when reviewing LLM generated code?

Best practices for reviewing LLM generated code involve enforcing surgical edits that affect only the intended area, surfacing hidden assumptions, and verifying that measurable success criteria are met without introducing collateral changes.

How do I enforce surgical code changes for AI assisted development?

You can enforce surgical code changes by instructing the AI to apply targeted editing guidelines, ensuring modifications affect only the intended area, avoiding collateral changes, and explicitly recording assumptions before code execution.

Why do I need to surface explicit assumptions before writing code with an LLM?

Surfacing explicit assumptions before writing code prevents overcomplication and reduces errors by forcing developers to define verifiable success criteria and plan-first workflows, ensuring clarity, safety, and minimal changes.

Can I integrate these coding guidelines into automated code review prompts?

Yes, you can integrate these coding guidelines into code review prompts for LLM-powered development, applying structured guidance to refactoring tasks and reviews to improve correctness, reliability, and risk minimization across software tasks.

When should I avoid using minimal changes for code refactoring?

You should reconsider surgical minimal changes when a refactoring task requires systemic architectural updates, as these guidelines target targeted edits to reduce collateral changes rather than broad structural overhauls.