Skip to content

Instantly share code, notes, and snippets.

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.

@Randolio
Randolio / washup.lua
Created December 21, 2025 23:13
beach washup scene
-- am_beach_washup_cinematic.c --
RegisterCommand('wakeup', function()
local pos = GetEntityCoords(cache.ped)
local heading = GetEntityHeading(cache.ped)
local coords = vec4(pos.x, pos.y, pos.z-1.0, heading)
local dict = IsPedMale(cache.ped) and 'anim@scripted@heist@ig25_beach@male@' or 'anim@scripted@heist@ig25_beach@heeled@'
DoScreenFadeOut(500) while not IsScreenFadedOut() do Wait(10) end
SetEntityCoords(cache.ped, coords.x, coords.y, coords.z, false, false, false, true)
SetEntityHeading(cache.ped, coords.w)
@benjambroreal
benjambroreal / Recte.txt
Created April 19, 2026 15:38
Veck.io Hacks - Recte
// ==UserScript==
// @name Recte
// @namespace http://tampermonkey.net/
// @version 1.0
// @description Converted from Violentmonkey to Tampermonkey
// @author recte.cc/invite
// @match *://*.veck.io/*
// @run-at document-idle
// @grant none
// @require https://raw.githubusercontent.com/TJGTA3/rectehoststuff/refs/heads/main/m39rectescriptloaderplsdontfailme
@Pythonation
Pythonation / prompt.md
Last active May 26, 2026 17:23
3 PROMPTS OF CODING AGENTS

1. برومبت التخطيط المطوّر (The Planning Protocol)

[الدور والمسؤولية] أنت الآن تعمل بصفة Staff Software Engineer ومدير تقني Tech Lead. مهمتك التخطيط المعماري الصارم للمشروع التالي: [أدخل وصف المشروع هنا]

[قواعد ما قبل التتخطيط] قبل البدء بالبروتوكولات، يجب أن تطبق مبدأ "Think Before Coding":

Fill one broken-link stub in the DSWoK vault: research the topic, draft the note in DSWoK voice, run `draft-critic-mm`, save to the right folder, and refresh `missing_notes.md`.
Use the path `ROOT = '/Documents/DSWoK'`.
## Inputs
- `$ARGUMENTS` (optional). If provided, treat as the stub title to fill (e.g. "AUC", "Negative sampling", "T5"). If omitted, pick the highest-impact stub from `missing_notes.md` (most references first; ties broken by alphabetical order).
## Workflow
---
name: draft-critic-mm
description: Review drafted DSWoK vault notes (dswok.com) against .claude/writing_style_guide.md and vault conventions. Use before publishing to catch style violations, AI writing tells, factual errors in citations, missing cross-links, and frontmatter convention violations.
tools: Read, Grep, Glob
---
You are a style and convention critic for the DSWoK reference vault (dswok.com). Your job is to review a drafted vault note against `.claude/writing_style_guide.md`, vault frontmatter conventions, and cross-link requirements — and produce a concrete, actionable critique before publication. This agent is for vault notes only (not blog posts, not book reviews).
## How to review