From b00t
Applies Karpathy's four coding principles: Think Before Coding, Simplicity First, Surgical Changes, and Goal-Driven TDD. Useful for any coding session where methodical, minimal, and test-driven work is desired.
How this skill is triggered — by the user, by Claude, or both
Slash command
/b00t:karpathy-autoresearchThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Andrej Karpathy's way of working, distilled into four principles for LLM coding agents. (1) Think Before Coding — state assumptions, surface ambiguity, push back when warranted. (2) Simplicity First — minimum code, no speculative abstractions, DRY+NRtW. (3) Surgical Changes — touch only what you must, trace every line to the request. (4) Goal-Driven TDD — failing test first, loop until verified...
Andrej Karpathy's way of working, distilled into four principles for LLM coding agents. (1) Think Before Coding — state assumptions, surface ambiguity, push back when warranted. (2) Simplicity First — minimum code, no speculative abstractions, DRY+NRtW. (3) Surgical Changes — touch only what you must, trace every line to the request. (4) Goal-Driven TDD — failing test first, loop until verified, never claim solved without testing.
Applied in b00t: soul-first (learn before implement), lfmf for lessons, autolearn loop for goal-driven knowledge loading, and OODA for autonomous execution.
Apply Karpathy's principles in every coding session. Think before implementing, keep changes minimal and surgical, and always write the failing test first.
npx claudepluginhub elasticdotventures/_b00t_ --plugin skill-document-understandingFour-principle contract for reducing LLM coding pitfalls: think-first, simplicity, surgical edits, verifiable goals. Use before starting implementation or during code review.
Applies Karpathy guidelines to reduce LLM coding mistakes: think before coding, prioritize simplicity, make surgical changes, and define verifiable success criteria when writing, reviewing, or refactoring code.
Behavioral guidelines to avoid overcomplication, make surgical code changes, surface assumptions, and define verifiable success criteria. For writing, reviewing, or refactoring code.