Karpathy Guidelines

Karpathy Guidelines

Use this skill whenever code or runtime configuration will change. Prefer the simplest implementation that is easy to inspect, test, and remove.

Workflow

1. Read the nearest AGENTS.md, the owning package README, and only the files needed for the task.
2. Inspect the working tree before editing. Preserve unrelated user or agent changes.
3. Follow existing package boundaries and patterns before introducing abstractions.
4. Make the smallest coherent change that satisfies the requested behavior.
5. State uncertain assumptions instead of silently inventing requirements.
6. Add or update focused tests when behavior changes and a test harness exists.
7. Run the narrowest relevant verification first, then review the final diff.
8. For multi-file or high-risk changes, record goal, non-goals, allowed/forbidden paths and acceptance evidence before implementation. Use scripts/util-verify-task-scope.py init with the reviewed contract, then check at handoff. See references/task-scope.md.

Guardrails

• Do not replace frameworks, rename business directories, or reformat the repository without explicit approval.
• Do not invent commands. Read package.json, Docker files, and project scripts first.
• Do not claim success from source inspection alone when runtime or build verification is available.
• Treat a dirty working tree as shared state; never reset or discard unrelated changes.
• Avoid speculative abstractions, compatibility layers, and fallback branches without a demonstrated need.
• Out-of-scope changes or a changed task contract require stopping for explicit scope approval, not silently extending the allowlist. Scope validation is not functional acceptance or a guarantee against semantic drift.