karpathy-guidelines

Enforce conservative coding practices and surgical edits for LLM-generated changes.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/ToXMon/tolu --skill karpathy-guidelines-toxmon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: karpathy-guidelines
Source: https://github.com/ToXMon/tolu/tree/main/skills/karpathy-guidelines
Command: npx skills add https://github.com/ToXMon/tolu --skill karpathy-guidelines-toxmon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

These guidelines reduce common LLM-generated coding mistakes by forcing explicit assumptions, discouraging premature complexity, and requiring verifiable outcomes so AI-assisted edits are minimal, correct, and reviewable.

Core Features & Use Cases

  • Think Before Coding: Surface assumptions, present alternative interpretations, and stop to ask clarifying questions when ambiguous requirements exist.
  • Simplicity First & Surgical Changes: Prefer the minimal implementation that meets requirements and change only the lines required by the task to avoid drive-by refactors.
  • Goal-Driven Execution: Convert requests into verifiable success criteria and test-first steps so fixes and refactors can be validated independently.
  • Use Cases: AI-assisted code generation, PR reviews, refactors, bug fixes, and feature implementations where minimizing unintended changes and ensuring reproducibility are priorities.

Quick Start

Apply these rules to the current coding task: state assumptions, suggest the simplest change, modify only required lines, and define one or two verifiable success criteria to confirm the result.

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 code generation mistakes during refactoring?

Apply conservative coding practices to prevent LLM code generation mistakes during refactoring: force explicit assumptions, mandate minimal-scope surgical edits, and define verifiable success criteria for reproducible test-driven changes.

What is the best way to review AI-generated pull requests?

Review AI-generated pull requests by checking for simplicity-first implementations, verifying only required lines were modified to prevent drive-by refactors, and confirming explicitly defined verifiable success criteria.

How do I enforce surgical code edits when using AI for feature implementation?

Enforce surgical code edits during AI feature implementation by converting requests into verifiable success criteria, preferring the minimal implementation that meets requirements, and modifying only the lines required by the task.

Why does AI-assisted coding introduce unintended complexity and how do I limit it?

AI-assisted coding introduces unintended complexity by ignoring premature simplification. Limit it by applying simplicity-first guidelines that surface assumptions, present alternative interpretations, and stop to ask clarifying questions when requirements are ambiguous.

Does applying conservative coding guidelines work for human-proposed changes in bug fixes?

Applying conservative coding guidelines works for human-proposed changes in bug fixes by ensuring minimal-scope edits, explicit assumptions, and test-first steps so fixes can be validated independently and reproducibly.