Skip to content

Instantly share code, notes, and snippets.

@karpathy
karpathy / microgpt.py
Last active February 15, 2026 03:01
microgpt
"""
The most atomic way to train and inference a GPT in pure, dependency-free Python.
This file is the complete algorithm.
Everything else is just efficiency.
@karpathy
"""
import os # os.path.exists
import math # math.log, math.exp
@TerryCavanagh
TerryCavanagh / howtorunexefilesonlinux.md
Last active February 15, 2026 03:00
How to run windows .exe files on Linux by just double clicking on them

Here's a little script I use to easily run windows exe files on Linux by just double clicking on them, like you would on windows. It uses Valve's Proton, and assumes you have Steam installed somewhere on Linux. I'm using Ubuntu with Gnome.

First, copy this shell script somewhere in your home directory. Mine is in /home/terry/scripts/protonlauncher.sh. (I didn't write this script, I found it on google)

#!/usr/bin/env bash

if [ "$#" -ne 1 ]; then
    echo "Usage: $0 <executable-path>"
    exit 1
@steipete
steipete / agent.md
Created October 14, 2025 14:41
Agent rules for git
  • Delete unused or obsolete files when your changes make them irrelevant (refactors, feature removals, etc.), and revert files only when the change is yours or explicitly requested. If a git operation leaves you unsure about other agents' in-flight work, stop and coordinate instead of deleting.
  • Before attempting to delete a file to resolve a local type/lint failure, stop and ask the user. Other agents are often editing adjacent files; deleting their work to silence an error is never acceptable without explicit approval.
  • NEVER edit .env or any environment variable files—only the user may change them.
  • Coordinate with other agents before removing their in-progress edits—don't revert or delete work you didn't author unless everyone agrees.
  • Moving/renaming and restoring files is allowed.
  • ABSOLUTELY NEVER run destructive git operations (e.g., git reset --hard, rm, git checkout/git restore to an older commit) unless the user gives an explicit, written instruction in this conversation. Treat t
[
['00-00-00', 'XEROX CORPORATION'],
['00-00-01', 'XEROX CORPORATION'],
['00-00-02', 'XEROX CORPORATION'],
['00-00-03', 'XEROX CORPORATION'],
['00-00-04', 'XEROX CORPORATION'],
['00-00-05', 'XEROX CORPORATION'],
['00-00-06', 'XEROX CORPORATION'],
['00-00-07', 'XEROX CORPORATION'],
['00-00-08', 'XEROX CORPORATION'],
@OmerFarukOruc
OmerFarukOruc / claude.md
Last active February 15, 2026 02:26
AI Agent Workflow Orchestration Guidelines

AI Coding Agent Guidelines (claude.md)

These rules define how an AI coding agent should plan, execute, verify, communicate, and recover when working in a real codebase. Optimize for correctness, minimalism, and developer experience.


Operating Principles (Non-Negotiable)

  • Correctness over cleverness: Prefer boring, readable solutions that are easy to maintain.
  • Smallest change that works: Minimize blast radius; don't refactor adjacent code unless it meaningfully reduces risk or complexity.