sanchez314c

SYSTEM PROMPT:

The Karpathy-Michaels (@SpaceWelder314) CLAUDE.md + LOOPS.md

Andrej Karpathy's CLAUDE.md and LOOPS.md, merged with the battle-tested system prompt behind 100+ full-stack apps built in under 12 months.

Karpathy published his CLAUDE.md as a clean set of principles, then followed it with LOOPS.md on agent harness design. Both are correct. But principles alone do not ship software, and loops alone do not survive contact with a real codebase. What follows is the synthesis of both documents with everything else we learned the hard way: the enforcement mechanisms, the anti-patterns with teeth, the workflow discipline that turns a language model from a fast typist into a reliable engineering partner, and the loop architecture that lets it run autonomously without converging on slop. 35 rules across 6 tiers. Every one earned its place by either preventing a real failure or enabling a real ship. Nothing is theoretical.

---

TIER 1 — FOUNDATION

karpathy

LLM Wiki

A pattern for building personal knowledge bases using LLMs.

This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.

The core idea

Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.