Geronimo Ezequiel Perez Salas GeroSalas

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.

Technical Documentation Template

First of all, you need to understand you are not writing documentation for you, nor for your current team. You are writing documentation for the future developers that were not there when you first wrote this code. Worst of it, they might think it is bad code for many reasons and won’t understand why you wrote this way.

Taken from: How to write good software technical documentation

RFC Template

Feature Name: (fill me in with a unique identity, myawesomefeature)

Type: (feature, enhancement)

Start Date: (fill me in with today's date, YYYY-MM-DD)

Author: (your names)

Naming Conventions
Documentation
Declarations
Format
JSHint Rules

Naming Conventions

Use PascalCase when naming constructors

function Person(name) {

	#/bin/bash
	#Ask some info
	echo -n "Enter ELK Server IP or FQDN: "
	read eip
	echo -n "Enter Admin Web Password: "
	read adpwd

	#Update System
	sudo apt-get update
	sudo apt-get upgrade -y

	'use strict';

	var elasticsearch = require('elasticsearch');
	var Promise = require('bluebird');

	var log = console.log.bind(console);

	var client = new elasticsearch.Client({
	host: 'localhost:9200',
	log: 'trace'

	-- show running queries (pre 9.2)
	SELECT procpid, age(clock_timestamp(), query_start), usename, current_query
	FROM pg_stat_activity
	WHERE current_query != '<IDLE>' AND current_query NOT ILIKE '%pg_stat_activity%'
	ORDER BY query_start desc;

	-- show running queries (9.2)
	SELECT pid, age(clock_timestamp(), query_start), usename, query
	FROM pg_stat_activity
	WHERE query != '<IDLE>' AND query NOT ILIKE '%pg_stat_activity%'