karpathy-guidelines
Skill0 starsChanged 3 months agoMITView on GitHub
Maintenance-only engineering guidelines for working ON this workspace's own code. Use when writing, reviewing, refactoring or debugging the tools, tests and configuration here: keep it simple, make surgical changes, surface assumptions, define verifiable success criteria. Not part of /scrape, /rank or /shortlist and never changes the product boundary.
136 other projects use a version of this, 121 of them edited.
Adopted by
Most recently taken up by
- Floppa2003/skillsedited, first seen Nov 16, 2026
- KPISTOLAS/claude-skillsedited, first seen Nov 16, 2026
- Scratchydisk/claude-skillsedited, first seen Nov 16, 2026
- vparsatwar-git/claude-skillsedited, first seen Nov 16, 2026
- pwizzang/claude-skillsedited, first seen Nov 16, 2026
- troia-51/claude-skillsedited, first seen Nov 16, 2026
Used with
Projects with it also use audit-context-building, huashu-design and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
allanninalSkillaudit-context-building
Enables ultra-granular, line-by-line code analysis to build deep architectural context before vulnerability or bug finding.
Also in 3 projects that use this
XIYBHKSkillhuashu-design
花叔Design(Huashu-Design)——用HTML做高保真原型、交互Demo、幻灯片、动画、设计变体探索+设计方向顾问+专家评审的一体化设计能力。HTML是工具不是媒介,根据任务embody不同专家(UX设计师/动画师/幻灯片设计师/原型师),避免web design tropes。触发词:做原型、设计Demo、交互原型、HTML演示、动画Demo、设计变体、hi-fi设计、UI mockup、prototype、设计探索、做个HTML页面、做个可视化、app原型、iOS原型、移动应用mockup、导出MP4、导出GIF、60fps视频、设计风格、设计方向、设计哲学、配色方案、视觉风格、推荐风格、选个风格、做个好看的、评审、好不好看、review this design。**主干能力**:Junior Designer工作流(先给假设+reasoning+placeholder再迭代)、反AI slop清单、React+Babel最佳实践、Tweaks变体切换、Speaker Notes演示、Starter Components(幻灯片外壳/变体画布/动画引擎/设备边框)、App原型专属守则(默认从Wikimedia/Met/Unsplash取真图、每台iPhone包AppPhone状态管理器可交互、交付前跑Playwright点击测试)、Playwright验证、HTML动画→MP4/GIF视频导出(25fps基础 + 60fps插帧 + palette优化GIF + 6首场景化BGM + 自动fade)。**需求模糊时的Fallback**:设计方向顾问模式——从5流派×20种设计哲学(Pentagram信息建筑/Field.io运动诗学/Kenya Hara东方极简/Sagmeister实验先锋等)推荐3个差异化方向,展示24个预制showcase(8场景×3风格),并行生成3个视觉Demo让用户选。**交付后可选**:专家级5维度评审(哲学一致性/视觉层级/细节执行/功能性/创新性各打10分+修复清单)。
Also in 3 projects that use this
rogue-dev-studioSkillgithub-cli
GitHub CLI authentication and workflow configuration. Use when the project needs this capability or the user / team manifest asks for it. Use for specialized `github-cli` work when listed in TEAM.yaml or explicitly requested.
Also in 3 projects that use this
OpenAISkillusing-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
Also in 10 projects that use this
OpenAISkilldispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Also in 13 projects that use this
lithStudySkillbanner-design
Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with AI-generated visuals. Actions: design, create, generate banner. Platforms: Facebook, Twitter/X, LinkedIn, YouTube, Instagram, Google Display, website hero, print. Styles: minimalist, gradient, bold typography, photo-based, illustrated, geometric, retro, glassmorphism, 3D, neon, duotone, editorial, collage. Uses ui-ux-pro-max, frontend-design, ai-artist, ai-multimodal skills.
Also in 4 projects that use this
- +3 more from openai
Other versions136 projects use a version of this.
Word for word · 0
None found.
Edited · 121
- forrestchang/andrej-karpathy-skills★ 217k91% same
- multica-ai/andrej-karpathy-skills★ 214k91% same
- ghostfolio/ghostfolio★ 9.7k91% same
- OpenBMB/PilotDeck★ 5k91% same
- didi/mpx★ 4k91% same
- hzm0321/real-time-fund★ 1.8k91% same
- x-tools-author/x-tools★ 1.1k91% same
- mxyhi/ok-skills★ 51191% same
- vtroisWhite/andrej-karpathy-skills★ 42691% same
- Y80/bmm★ 34191% same
111 more not listed
Wrote their own version · 15
- coco-research/coco★ 797same name
- tev6/andrej-karpathy-skills-zhCN★ 17same name
- Sspacegray/andrej-karpathy-skills-codex★ 8same name
- richling98/karpathy-codex-skills★ 4same name
- hahuyhungdev/ai-coding-config★ 3same name
- mel0nyrame/skills★ 3same name
- Hotakus/hotakus-useful-skills★ 2same name
- thlaure/Signalist★ 2same name
- ahmadrishi/agentic-mahoraga★ 1same name
- Binbin-miao/workbuddy-expert-team★ 1same name
5 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- humanizerSkill
- job-matcherSkill
- scrapeSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. 14 are common, 0 are distinctive, and 1 is very specific to this project.
14
Common
Most of the 131 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 28
If multiple interpretations exist, present them - don't pick silently.
- Common: line 29
If a simpler approach exists, say so.
- Common: line 30
If something is unclear, stop.
- Common: line 36
No features beyond what was asked.
- Common: line 37
No abstractions for single-use code.
- Common: line 39
No error handling for impossible scenarios.
- Common: line 40
If you write 200 lines and it could be 50, rewrite it.
- Common: line 42
Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify.
- Common: line 48
When editing existing code:
- Common: line 49
Don't "improve" adjacent code, comments, or formatting.
- Common: line 50
Don't refactor things that aren't broken.
- Common: line 52
If you notice unrelated dead code, mention it - don't delete it.
- Common: line 54
When your changes create orphans:
- Very specific: line 55
Remove imports/variables/functions that YOUR changes made unused.
- Common: line 56
Don't remove pre-existing dead code unless asked.
“Common” is measured: kept by at least 6 in 10 of the 131 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Karpathy Guidelines
Behavioral guidelines to reduce common LLM coding mistakes, derived from Andrej Karpathy's observations on LLM coding pitfalls.
Tradeoff: These guidelines bias toward caution over speed. For trivial tasks, use judgment.
Scope in this workspace
This is a MAINTENANCE skill. It governs how the code in this repository is changed; it governs nothing the product does at runtime.
- It applies to coding, code review, bug fixing and refactoring of
tools/,config/,.claude/and the tests. - It is not a dependency of
/scrape,/rank,/shortlist,/screenor/healthcheck, and those commands must run identically whether or not it is loaded. - It never widens the product boundary.
discover -> verify -> match -> rank -> shortlist -> stopis unchanged, and nothing here authorises an application action, a new capability, a tool grant, or a relaxation of the trust boundary. - Where it disagrees with
CLAUDE.md, the project rules win. This advises on HOW to change code, not on WHAT this workspace is allowed to do.
1. Think Before Coding
Don't assume. Don't hide confusion. Surface tradeoffs.
Before implementing:
- State your assumptions explicitly. If uncertain, ask.
- If multiple interpretations exist, present them - don't pick silently.
- If a simpler approach exists, say so. Push back when warranted.
- If something is unclear, stop. Name what's confusing. Ask.
2. Simplicity First
Minimum code that solves the problem. Nothing speculative.
- No features beyond what was asked.
- No abstractions for single-use code.
- No "flexibility" or "configurability" that wasn't requested.
- No error handling for impossible scenarios.
- If you write 200 lines and it could be 50, rewrite it.
Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify.
3. Surgical Changes
Touch only what you must. Clean up only your own mess.
When editing existing code:
- Don't "improve" adjacent code, comments, or formatting.
- Don't refactor things that aren't broken.
- Match existing style, even if you'd do it differently.
- If you notice unrelated dead code, mention it - don't delete it.
When your changes create orphans:
- Remove imports/variables/functions that YOUR changes made unused.
- Don't remove pre-existing dead code unless asked.
The test: Every changed line should trace directly to the user's request.
4. Goal-Driven Execution
Define success criteria. Loop until verified.
Transform tasks into verifiable goals:
- "Add validation" -> "Write tests for invalid inputs, then make them pass"
- "Fix the bug" -> "Write a test that reproduces it, then make it pass"
- "Refactor X" -> "Ensure tests pass before and after"
For multi-step tasks, state a brief plan:
1. [Step] -> verify: [check]
2. [Step] -> verify: [check]
3. [Step] -> verify: [check]Strong success criteria let you loop independently. Weak criteria ("make it work") require constant clarification.
In this workspace, "verified" means
The deterministic gates already exist. Use them as the success criteria rather than inventing new ones:
python tools/validate_workspace.py --deep
python tools/job_state.py doctor
python tools/preflight.py
python tools/candidate_config.py validate
python tools/match_evaluation.py validate-policy
python tools/application_audit.py auditA behaviour change is finished when a test proves the OLD behaviour would have failed, not merely when the suite is still green.
Attribution
MIT licensed. Principles derived from Andrej Karpathy's observations on LLM coding pitfalls.
The four numbered sections are reproduced from the upstream skill with their wording unchanged; the only edit is typographic, replacing the arrow character with -> to match this workspace's ASCII convention. The ## Scope in this workspace and ## In this workspace, "verified" means sections are this workspace's own integration notes and are not upstream content.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

