karpathy-guidelines

Enforce pre-implementation assumption surfacing and simplicity-first design in code tasks.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/Plutonian-coder/AI-hms --skill karpathy-guidelines-plutonian-coder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: karpathy-guidelines
Source: https://github.com/Plutonian-coder/AI-hms/tree/main/.agents/skills/karpathy-guidelines
Command: npx skills add https://github.com/Plutonian-coder/AI-hms --skill karpathy-guidelines-plutonian-coder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Large language models frequently produce overcomplicated, misaligned, or unnecessarily modified code when writing, reviewing, or refactoring, leading to increased technical debt, wasted engineering time, and unintended side effects in existing codebases.

Core Features & Use Cases

  • Pre-Implementation Guardrails: Requires explicit surfacing of assumptions, tradeoffs, and alternative approaches before writing any code to avoid misaligned outputs.
  • Simplicity-First Design: Enforces minimal, non-speculative code that solves only the requested problem, eliminating unrequested features, abstractions, and error handling for edge cases.
  • Surgical Editing Rules: Restricts code changes to only the scope of the user's request, preventing unplanned refactors of adjacent, functional code.
  • Use Case: A developer asking an AI to add input validation to a user registration endpoint will receive only the required validation logic, no extra features or unrelated code cleanups.

Quick Start

Use the karpathy-guidelines skill to review your recent code changes for overcomplicated logic and unrequested refactors.

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 when generating software code?

To prevent LLM coding mistakes, enforce pre-implementation assumption surfacing and simplicity-first design principles. This approach requires explicit tradeoff evaluation before code writing, ensuring outputs remain minimal and free of speculative features or unrequested adjacent refactors.

Why does AI generated code include unnecessary refactoring and overcomplicated logic?

AI generated code includes unnecessary refactoring because large language models frequently produce overcomplicated, misaligned outputs without strict guardrails. Applying surgical editing rules restricts code changes to only the requested scope, eliminating unplanned refactors of functional adjacent code.

What is the best way to enforce simplicity-first design during AI code review?

The best way to enforce simplicity-first design during AI code review is to apply development guardrails that require minimal, non-speculative code. This ensures the AI solves only the requested problem without adding unrequested abstractions or excessive edge case error handling.

How to stop AI from adding unrequested features and abstractions to existing code?

To stop AI from adding unrequested features, enforce surgical editing rules and simplicity-first design principles. This restricts modifications to only the user's explicit request, preventing the LLM from generating unplanned abstractions or performing unrelated code cleanups.

Can I apply coding guardrails to refactoring tasks across all software engineering workflows?

Yes, you can apply coding guardrails to refactoring tasks across all software engineering workflows. These guidelines ensure maintainable, minimal code modifications with clear verifiable success criteria, preventing unintended side effects in existing codebases.

When do I need pre-implementation assumption surfacing for development tasks?

You need pre-implementation assumption surfacing for development tasks before writing any code. This guardrail requires explicitly stating assumptions, tradeoffs, and alternative approaches to avoid misaligned LLM outputs and reduce technical debt.