Weapons Forge weaponsforge

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

General rules

Follow standard conventions.
Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
Boy scout rule. Leave the campground cleaner than you found it.
Always find root cause. Always look for the root cause of a problem.

Design rules

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.

	FROM node:20.15.3-alpine AS base
	RUN mkdir -p /opt/app
	WORKDIR /opt/app
	RUN adduser -S user
	RUN chown -R user /opt/app
	COPY package*.json ./

	FROM base AS development
	RUN npm install
	COPY . ./

	#!/bin/bash

	# Stops and deletes ALL Docker resources
	docker image prune
	docker rmi $(docker images -a -q)
	docker stop $(docker ps -a -q)
	docker rm $(docker ps -a -q)
	docker system prune -f
	docker system prune -a
	docker volume prune -f