Built 26/04/15 21:42commit 9419fc3
Forrestchang Andrej Karpathy Skills Repository
中文 | English
Summary
This repository packages Karpathy-inspired coding guidance into three reusable Claude Code surfaces at once: a CLAUDE.md prompt layer, a reusable skill, and installable plugin metadata.
Source
- Raw file: raw/karpathy/forrestchang-andrej-karpathy-skills.md
- Translated raw file: raw/karpathy/forrestchang-andrej-karpathy-skills.zh.md
- Original URL: https://github.com/forrestchang/andrej-karpathy-skills
- Author: forrestchang
- Ingest date: 2026-04-16
Key Contributions
- Turns Karpathy's operator observations about coding-model failure modes into a compact, reusable instruction package.
- Shows the same operating model distributed across repo-local instructions, reusable skills, and Claude plugin metadata.
- Makes explicit that lightweight behavior contracts can target specific failure classes: hidden assumptions, overengineering, collateral edits, and weak success criteria.
- Provides another concrete example of an agent-first repository exposing a distribution story rather than only a single prompt file.
Strongest Claims
- Good coding guidance for LLMs can stay short if it names the right recurring failure modes.
- The same operating model can be repackaged for different consumption surfaces without changing its core ideas.
- Success-criteria prompting and surgical diffs are not just prompting tips, they are reusable repository assets.
Relationship To Existing Karpathy Coverage
This is not the original Karpathy source.
Instead, it is a downstream packaging repository that translates Karpathy's X-thread observations into reusable Claude Code assets. That makes it complementary to the existing Karpathy Claude Coding Thread page rather than a duplicate of it.
Practical Implications
- Agent methodology increasingly ships as installable repo assets, not only as advice in threads or docs.
- Small skills and plugin manifests can serve as a distribution layer for coding norms.
- Reusable instruction packs can bridge individual operator insight and team-wide default behavior.