Github trending [multica-ai/andrej-karpathy-skills] Karpathy式LLM编程行为准则

[web1992]

项目地址

https://github.com/multica-ai/andrej-karpathy-skills

AI 摘要

该项目提供了一套基于 Andrej Karpathy 对 LLM 编程缺陷观察的 Claude Code 行为准则，核心包含四条原则：先思考再编码（明确假设、提出歧义、必要时反驳）、简洁优先（拒绝过度设计与抽象）、外科手术式修改（只改动必要代码，不破坏无关内容）、目标驱动执行（以测试与可验证标准定义成功）。它通过安装插件或写入 CLAUDE.md 使用，也可用于 Cursor 编辑器。核心思想是：与其命令模型“做什么”，不如给出明确的成功标准，让其自主循环直至达成目标。

README 原文

Karpathy-Inspired Claude Code Guidelines

Check out my new project Multica — an open-source platform for running and managing coding agents with reusable skills.

Follow me on X: https://x.com/jiayuan_jy

A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.

English | 简体中文

The Problems

From Andrej's post:

"The models make wrong assumptions on your behalf and just run along with them without checking. They don't manage their confusion, don't seek clarifications, don't surface inconsistencies, don't present tradeoffs, don't push back when they should."

"They really like to overcomplicate code and APIs, bloat abstractions, don't clean up dead code... implement a bloated construction over 1000 lines when 100 would do."

"They still sometimes change/remove comments and code they don't sufficiently understand as side effects, even if orthogonal to the task."

The Solution

Four principles in one file that directly address these issues:

Principle	Addresses
Think Before Coding	Wrong assumptions, hidden confusion, missing tradeoffs
Simplicity First	Overcomplication, bloated abstractions
Surgical Changes	Orthogonal edits, touching code you shouldn't
Goal-Driven Execution	Leverage through tests-first, verifiable success criteria

The Four Principles in Detail

1. Think Before Coding

Don't assume. Don't hide confusion. Surface tradeoffs.

LLMs often pick an interpretation silently and run with it. This principle forces explicit reasoning:

• State assumptions explicitly — If uncertain, ask rather than guess
• Present multiple interpretations — Don't pick silently when ambiguity exists
• Push back when warranted — If a simpler approach exists, say so
  ...