karpathy-guidelines

Enforce explicit assumptions and verifiable plans for LLM coding tasks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Behavioral guidelines to reduce common LLM coding mistakes, helping you write clearer, safer, and more review-friendly code.

Core Features & Use Cases

  • Think Before Coding: Surface assumptions and tradeoffs before implementing.
  • Surgical Changes: Change only what you must, preserve existing code.
  • Goal-Driven Execution: Define verifiable success criteria and loop until verified.

Quick Start

Follow these guidelines at the start of any coding task to surface assumptions and plan verifiable steps.

Frequently Asked Questions about karpathy-guidelines

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

FAQPage Schema
What guidelines help surface tradeoffs before writing code with an LLM?

To reduce LLM coding mistakes, enforce explicit assumptions and tradeoffs before implementation, ensuring the model surfaces hidden dependencies and defines a concise plan with verifiable success criteria.

Can I define verifiable success criteria for LLM generated code?

Enforce surgical changes during LLM code review by requiring the model to limit unnecessary modifications and preserve existing logic, ensuring changes remain strictly scoped to the defined task.

Does applying behavioral guidelines limit unnecessary code changes?

Ensure LLM code generation follows a measurable plan by defining verifiable success criteria upfront and looping the execution until those measurable outcomes are explicitly verified.

What is the best way to surface assumptions before LLM coding tasks?

LLMs make unnecessary changes during code refactoring because they lack explicit behavioral constraints, which can be mitigated by enforcing surgical rules that preserve existing code and limit scope creep.