karpathy-guidelines

Outlines how to implement minimal-impact code changes across the enterprise with Apache Kafka.

Updated May 13, 2026
One-click install
npx skills add https://github.com/Ricardo-Vae/codex-research-skills --skill karpathy-guidelines-ricardo-vae
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: karpathy-guidelines
Source: https://github.com/Ricardo-Vae/codex-research-skills/tree/main/skills/karpathy-guidelines
Command: npx skills add https://github.com/Ricardo-Vae/codex-research-skills --skill karpathy-guidelines-ricardo-vae

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents overengineering by enforcing disciplined, goal-driven coding: think first, keep diffs small, and implement only what the user outcome requires.

Core Features & Use Cases

  • Think Before Coding: Restate the real goal, inspect existing code, and pick the smallest surface that solves it.
  • Simplicity First: Prefer the simplest correct approach, avoid speculative abstractions and unnecessary dependencies.
  • Surgical Changes: Touch as few files and symbols as possible, keep behavior changes narrow, and avoid drive-by edits.

Use case examples: applying a minimal fix in an unfamiliar codebase, tightening an implementation to the requested behavior, or refactoring safely when the user wants “simple” and “surgical” edits rather than redesign.

Quick Start

Use the karpathy-guidelines skill when you want to implement a change with minimal diffs by first restating the target outcome and then applying the smallest necessary edits to reach it.

Frequently Asked Questions about karpathy-guidelines

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

FAQPage Schema
How do I make surgical code changes instead of large refactors?

Surgical code changes require restating the target outcome, identifying the smallest necessary edit set, and reusing existing patterns to touch as few files as possible. This approach keeps diffs minimal and prevents overengineering.

What is goal-driven development for preventing overengineering?

Goal-driven development enforces disciplined coding by restating the real objective, inspecting existing code, and implementing only what the user outcome requires. This prevents speculative abstractions and unnecessary dependencies.

How do I apply minimal diffs when fixing bugs in an unfamiliar codebase?

Applying minimal diffs involves inspecting the existing code, choosing the simplest correct approach, and touching as few symbols as possible. This avoids drive-by edits and keeps behavior changes narrow.

When should I avoid speculative abstractions during software refactoring?

Speculative abstractions should be avoided when the user requests simple and surgical edits rather than a redesign. Prefer the simplest correct approach that solves the explicit goal without adding unnecessary dependencies.

Does code discipline require reusing existing patterns for simple fixes?

Code discipline mandates reusing existing patterns to implement minimal fixes. By leveraging established code structures, you avoid unnecessary dependencies and keep the change surface narrow for safer refactoring.

Why does my refactoring introduce unnecessary complexity?

Refactoring introduces unnecessary complexity when it lacks goal-driven discipline and includes speculative abstractions. Restate the real goal, inspect existing code, and apply only the smallest change set to solve it.