karpathy

Best practices for LLM-based coding involve applying behavioral guidelines that emphasize thinking before coding, prioritizing simplicity, making surgical changes, and maintaining goal-driven execution to reduce common pitfalls. This Skill provides these four core principles to guide developers.

To apply coding guidelines before a feature implementation, invoke the Skill command to set the right mindset for caution and minimalism. This triggers behavioral rules that help you think through the design and execute surgical changes during non-trivial coding work or refactoring.

You should use minimalism and surgical changes during code refactoring when working on non-trivial coding tasks to avoid introducing new errors. Applying these guidelines ensures you make targeted modifications rather than broad, complex rewrites, keeping the codebase stable and goal-driven.

Yes, you can use these developer productivity guidelines for any software engineering project, especially during feature implementation or code refactorings. The principles are behavioral and aim to improve coding practices universally by emphasizing caution, simplicity, and goal-driven execution across LLM-based projects.

Emphasizing simplicity first helps avoid coding pitfalls by ensuring solutions remain straightforward and manageable rather than overly complex. This approach, part of Andrej Karpathy's guidelines, reduces the likelihood of introducing errors during non-trivial coding work and refactoring by prioritizing clear, goal-driven execution.

No, you do not need specific dependencies to use Andrej Karpathy's coding guidelines. The Skill operates independently to provide behavioral rules for LLM-based coding, requiring only the invocation of its command to set the appropriate mindset before beginning a new coding project or refactoring.