Skip to content

Instantly share code, notes, and snippets.

View StarJade-Park's full-sized avatar
๐Ÿ˜ƒ
Hi

0x0d5 StarJade-Park

๐Ÿ˜ƒ
Hi
View GitHub Profile

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.

@bessarabov
bessarabov / gist:674ea13c77fc8128f24b5e3f53b7f094
Last active September 2, 2025 01:50
One-liner to generate data shown in post 'At what time of day does famous programmers work?' โ€” https://ivan.bessarabov.com/blog/famous-programmers-work-time
git log --author="Linus Torvalds" --date=iso | perl -nalE 'if (/^Date:\s+[\d-]{10}\s(\d{2})/) { say $1+0 }' | sort | uniq -c|perl -MList::Util=max -nalE '$h{$F[1]} = $F[0]; }{ $m = max values %h; foreach (0..23) { $h{$_} = 0 if not exists $h{$_} } foreach (sort {$a <=> $b } keys %h) { say sprintf "%02d - %4d %s", $_, $h{$_}, "*"x ($h{$_} / $m * 50); }'
@lisawolderiksen
lisawolderiksen / git-commit-template.md
Last active April 25, 2026 00:53
Use a Git commit message template to write better commit messages

Using Git Commit Message Templates to Write Better Commit Messages

The always enthusiastic and knowledgeable mr. @jasaltvik shared with our team an article on writing (good) Git commit messages: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the

@intinig
intinig / .clang-format
Last active October 13, 2025 06:37
.clang-format for UE4
---
Language: Cpp
AccessModifierOffset: -4
AlignAfterOpenBracket: DontAlign
AlignConsecutiveAssignments: false
AlignConsecutiveDeclarations: false
AlignEscapedNewlines: Left
AlignOperands: true
AlignTrailingComments: true
AllowAllParametersOfDeclarationOnNextLine: true
#include <stdio.h>
#include <iostream>
#include <stack>
#include <cstring>
#include <queue>
#define ll long long int
#define MAX(a,b) (a)>(b)?(a):(b)
#define MIN(a,b) (a)>(b)?(b):(a)
#define pii pair<int , int>
#include <stdio.h>
#include <iostream>
#include <stack>
#include <cstring>
#define ll long long int
#define MAX(a,b) (a)>(b)?(a):(b)
#define MIN(a,b) (a)>(b)?(b):(a)
using namespace std;
#include <stdio.h>
#include <iostream>
#include <stack>
#include <cstring>
#define ll long long int
#define MAX(a,b) (a)>(b)?(a):(b)
#define MIN(a,b) (a)>(b)?(b):(a)
#define pii pair<int , int>
#define time first
#include <stdio.h>
#include <iostream>
#include <stack>
#include <cstring>
#include <queue>
#define ll long long int
#define MAX(a,b) (a)>(b)?(a):(b)
#define MIN(a,b) (a)>(b)?(b):(a)
#define pii pair<int , int>

๋ฌธ์ž์—ด ์ธ์ฝ”๋”ฉ์— ๋Œ€ํ•ด์„œ...

๋ฌธ์ž ์ฝ”๋“œ๋Š” ์šฐ๋ฆฌ๊ฐ€ ํ‘œํ˜„ํ•˜๊ณ ์ž ํ•˜๋Š” ๋ฌธ์ž๋“ค์˜ ์ง‘ํ•ฉ์„ ์ฝ”๋“œํ™”์‹œํ‚จ ๊ฒƒ์ด๊ณ , ๋ฌธ์ž์—ด ์ธ์ฝ”๋”ฉ์€ ๊ทธ๋Ÿฌํ•œ ๋ฌธ์ž ์ฝ”๋“œ์˜ ๋ฐฐ์—ด์„ ๋ฉ”๋ชจ๋ฆฌ์ƒ์— ํ‘œํ˜„ํ•˜๋Š” ๋ฐฉ๋ฒ•์ž…๋‹ˆ๋‹ค.

๋ฌธ์ž ์ฝ”๋“œ ์ธ์ฝ”๋”ฉ
์•„์Šคํ‚ค ์ฝ”๋“œ iso 8859