Discover gists

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.

how to leverage oracle's temping offers

free tier limits

The limits of the free tier say that you can create up to 4 instances.

x2 x86 instances (2core/1g)
x2 ampere instances (with 4core/24g spread between them)
200GB total boot volume space across all intances (minimum of 50G per instance)

[!WARNING]

Common Terminal Commands

Key Commands & Navigation

Before we look at some common commands, I just want to note a few keyboard commands that are very helpful:

Up Arrow: Will show your last command
Down Arrow: Will show your next command
Tab: Will auto-complete your command
Ctrl + L: Will clear the screen

Running Claude Code via Third-Party API Proxies

A comprehensive, step-by-step developer's guide to installing, configuring, and running Anthropic's Claude Code CLI client on PC, Linux, macOS, and Termux using alternative compatible API endpoints.

	#!/usr/bin/env bash
	#
	# namecheck — check project name availability everywhere at once:
	# npm · PyPI · crates.io · GitHub (org/user) · domains (RDAP)
	#
	# Usage:
	# ./namecheck.sh tokenscope burnmeter taximeter
	# ./namecheck.sh -f names.txt
	# ./namecheck.sh -t com,dev,io,sh,app tokenscope
	# ./namecheck.sh -n tokenscope # skip domains, package registries only

	# AGENTS.md

	- Do not preserve backward compatibility. Remove obsolete paths instead of adding compatibility layers, fallbacks, or migrations.
	- Choose the simplest implementation that fully meets the current requirements. Avoid speculative abstractions, configuration, and indirection.
	- Grow the system in layers. Start from the smallest version that works end to end, and add each new capability on top of a product that already works. Never trade a working product for unfinished complexity.
	- Keep components modular and concerns clearly separated.
	- Prefer established, well-maintained libraries when they reduce overall complexity or improve reliability. Do not reimplement common functionality without a clear reason.
	- Lean on the dependencies already in the project before writing your own implementation or adding packages. Do not assume a library lacks a capability without checking its documentation and types.
	- Make architectural decisions for the long term. Do not accept a stopgap that only works for now an