Karpathy setup

Four rules before the model writes

Stays in this browser

Set the rules. Then read the diff.

Andrej Karpathy’s notes on how coding models overbuild, as a critic you can run on a task and a patch. No account, no upload.

01

Think before coding

State assumptions. Ask if two readings exist.

02

Simplicity first

Only the code this task actually needs.

03

Surgical changes

Every changed line traces to the request.

04

Goal-driven

Name the check. Loop until it passes.

Try one

Task

Ambiguous verbs get a question. A named check does not.

Paste a task. Vague verbs earn a question. A named check does not.

Brief

The brief appears here.

Diff

— drift

Paste a unified diff. Quote flips, extra errors, and strategy-pattern piles get flagged.

Plan

Number the steps. Each line should say verify, test, or check.

Four calls

Pick the move that matches the rules. The score stays on this browser.

The request is “export user data”. What do you do first?
The request is “add a function to calculate a discount”. What belongs in the diff?
The bug is an empty email crashing the validator. The diff also rewrites comments, adds a docstring, and rejects short usernames. Verdict?
The request is “fix the authentication system”. Which plan is ready to run?

Nothing scored yet.