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.

FabianWesner

description	Start a brainstorming session to create a feature specification
argument-hint	<feature-name>

Feature Specification or Bug Investigation

Start a collaborative session for: $ARGUMENTS

Mode Detection

maxjustus

import { h, ChildNode, FunctionalComponent, FunctionalUtilities } from "@stencil/core";

function vnodeToSource(elem: ChildNode, utils: FunctionalUtilities, output = "", level = 0): string {
  if (elem.vchildren) {
    let childOutput: string[] = [];

    utils.forEach(elem.vchildren, (child) => {
      childOutput.push(vnodeToSource(child, utils, output, level + 1));
    });

jdnichollsc

<animatable-component
  autoplay
  easing="ease-in-out"
  duration="800"
  delay="300"
  animation="zoomIn"
  iterations="Infinity"
  direction="alternate"
>
  <h1>Hello World</h1>

StefanNieuwenhuis

How to build a framework independent component library with StencilJS

This is a proposal for a lightning talk at Reactive Conf. Please 🌟 this gist to push the proposal! If you're on your phone, please request the 🖥 desktop site to star this gist 😇 #ReactiveConf

heygrady

Avoiding HOC; Favoring render props

The React community is moving away from HOC (higher order components) in favor of render prop components (RPC). For the most part, HOC and render prop components solve the same problem. However, render prop components provide are gaining popularity because they are more declarative and flexible than an HOC.

Read more:

• Use a render prop
• Breaking up with HOC
• HOC vs. render props
• React HOC docs
• React render props docs

markerikson

import React from "react";
import ReactDOM from "react-dom";

import configureStore from "./store/configureStore";


const store = configureStore();


const rootEl = document.getElementById("root");

hoschi

import mySaga from 'mySaga';
import { take, fork, cancel } from 'redux-saga/effects';

const sagas = [mySaga];

export const CANCEL_SAGAS_HMR = 'CANCEL_SAGAS_HMR';

function createAbortableSaga (saga) {
    if (process.env.NODE_ENV === 'development') {
        return function* main () {

CamdenSegal

class MAP_API_DemoItemType extends WP_JSON_CustomPostType {
	protected $base = '/map/demo';
	protected $type = 'demo';

	public function register_routes( $routes ) {
		$routes = parent::register_routes( $routes );
		return $routes;
	}
}

codfish

'use strict';

/**
 * Equal Heights
 *
 * Attach this directive to the parent/wrapping element of
 * a bunch of elements that are columns. This directive will
 * calculate the height of every direct child (one level down)
 * then set all of them to be the height of the tallest one.
 *