karpathy-guidelines

Enforce coding discipline with simplicity, assumption checks, and dead-code removal.

Updated Jun 28, 2026

Search Tags:#coding guidelines #coding discipline #assumption checks #overengineering resistance #dead code avoidance

Ready to run

npx skills add https://github.com/Mesteriis/Engineering-Bible-AI --skill karpathy-guidelines-mesteriis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: karpathy-guidelines
Source: https://github.com/Mesteriis/Engineering-Bible-AI/tree/main/skills/karpathy-guidelines
Command: npx skills add https://github.com/Mesteriis/Engineering-Bible-AI --skill karpathy-guidelines-mesteriis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill aids in maintaining coding discipline by encouraging simplicity, assumption checks, and dead-code avoidance, reducing overengineering and confusion.

Core Features & Use Cases

Coding Discipline: Encourages simplicity and critical thinking.
Assumption Checks: Helps verify assumptions before coding.
Dead Code Avoidance: Reminds to remove dead code during development.
Use Case: Before starting a complex feature, use this Skill to ensure you're building in a disciplined manner that avoids unnecessary complexity.

Quick Start

Load the 'karpathy-guidelines' skill and follow the rules for simplicity and thorough assumption checking in your code.

Frequently Asked Questions about karpathy-guidelines

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

FAQPage Schema

How do I avoid overengineering when building a complex software feature?▼

To avoid overengineering, validate your assumptions before coding and actively remove dead code to maintain simplicity. This approach ensures you build only what is necessary, reducing confusion and unnecessary complexity in your codebase.

What is coding discipline and how does assumption checking prevent bugs?▼

Coding discipline is the practice of maintaining simplicity and critical thinking during development. Assumption checks prevent bugs by forcing you to verify your premises before writing code, ensuring your logic is grounded and reducing overengineering.

Can I apply these coding guidelines to any existing codebase?▼

Yes, these coding guidelines are suitable for any codebase regardless of platform. They focus on universal practices like minimal assumptions, simplicity, and dead-code removal to improve clarity and prevent confusion during development.

What's the best way to remove dead code without breaking functionality?▼

The best way to remove dead code is to follow disciplined coding practices that emphasize simplicity and clarity. By continuously validating assumptions and removing unused code during development, you prevent confusion and maintain a clean codebase.

Why does overengineering cause confusion in software development?▼

Overengineering causes confusion by introducing unnecessary complexity and dead code into a project. Validating assumptions before coding and prioritizing simplicity helps maintain coding discipline, reducing confusion and making the codebase easier to manage.

Do I need specific dependencies or frameworks to follow these coding practices?▼

No, you do not need specific dependencies or frameworks to follow these coding practices. The guidelines focus on simplicity, assumption validation, and dead-code avoidance, making them applicable to any codebase without external requirements.