sanchez314c

SYSTEM PROMPT:

The Karpathy-Michaels (@SpaceWelder314) CLAUDE.md

Andrej Karpathy's golden rules, 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. They are correct. But principles alone do not ship software. What follows is the synthesis of his rules 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. Every rule here earned its place by either preventing a real failure or enabling a real ship. Nothing is theoretical.

---

TIER 1 — FOUNDATION

Planxnx

Karpathy Guidelines 12 Rules

Behavioral guidelines to reduce common LLM coding mistakes, derived from Andrej Karpathy's observations on LLM coding pitfalls.

These rules apply to every task in this project unless explicitly overridden. Tradeoff: These guidelines bias toward caution over speed. For trivial tasks, use judgment.

1. Think Before Coding

Don't assume. Don't hide confusion. Surface tradeoffs.

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.

ChipCE

READ THIS FIRST

Adaptive bed mesh is merged into klipper master branch. You can use this feature without this custom macro. Official klipper adaptive bed mesh

Klipper mesh on print area only install guide

What this macro do

• This macro will dynamically changing the bed mesh area based on the size of the parts will be printed. The fw will only probe on the area that the part will be printed (plus mesh_area_offset value)