karpathy-guidelines

Guide code writing, review, and refactoring to mitigate common LLM mistakes.

799|76|Updated Aug 29, 2025
One-click install
npx skills add https://github.com/vinhnx/VTCode --skill karpathy-guidelines-vinhnx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: karpathy-guidelines
Source: https://github.com/vinhnx/VTCode/tree/main/.agents/skills/andrej-karpathy-skills/skills/karpathy-guidelines
Command: npx skills add https://github.com/vinhnx/VTCode --skill karpathy-guidelines-vinhnx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers and AI agents avoid common pitfalls and overcomplication when writing, reviewing, or refactoring code, leading to more robust and maintainable software.

Core Features & Use Cases

  • Promotes Clarity: Encourages explicit statement of assumptions and surfacing of tradeoffs.
  • Enforces Simplicity: Guides towards writing the minimum necessary code, avoiding speculative features or premature abstractions.
  • Ensures Surgical Precision: Advocates for touching only necessary code and cleaning up only one's own modifications.
  • Drives Goal-Oriented Development: Emphasizes defining clear, verifiable success criteria for tasks.
  • Use Case: When an LLM is asked to refactor a complex function, these guidelines ensure it focuses only on the requested changes, simplifies the code without adding unnecessary features, and clearly states how the success of the refactoring will be measured.

Quick Start

Apply the karpathy-guidelines skill to ensure all code changes are minimal and directly address the user's request.

Frequently Asked Questions about karpathy-guidelines

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

FAQPage Schema
What are the best coding guidelines to prevent common LLM coding mistakes during refactoring?

To prevent common LLM coding mistakes during refactoring, apply guidelines that enforce explicit assumption surfacing, write minimal necessary code, and make surgical modifications to avoid premature abstractions and overcomplication.

How do I ensure code review principles focus on simplicity and explicit assumptions?

Code review principles focus on simplicity and explicit assumptions by requiring developers to state tradeoffs clearly, define verifiable success criteria, and ensure all code modifications are surgical and directly address the requested changes.

How do I stop an AI agent from adding speculative features when writing software?

To stop an AI agent from adding speculative features when writing software, enforce behavioral guidelines that drive goal-oriented execution, advocate for the minimum necessary code, and restrict modifications to only the requested changes.

Does applying strict coding guidelines work for both human developers and AI agents?

Applying strict coding guidelines works for both human developers and AI agents by providing a shared behavioral framework that mitigates common mistakes, enforces simplicity, and reduces complexity during software development.

What is the best way to define verifiable success criteria for code refactoring tasks?

The best way to define verifiable success criteria for code refactoring tasks is to establish goal-driven execution metrics upfront, ensuring the refactored code maintains functionality while strictly reducing complexity and avoiding unnecessary features.

When should I avoid making surgical code modifications during software development?

You should avoid deviating from surgical code modifications only when a broader architectural overhaul is explicitly requested; otherwise, strict guidelines require touching only necessary code and cleaning up solely your own modifications to prevent overcomplication.