← All projects
Operating
LLM Knowledge Base
A version-controlled store of prompts, skills, knowledge packs, and tools — Git as the source of truth, the LLM front-end as a consumer.
Problem
Prompts, custom tools, and knowledge documents rot inside LLM front-ends — unversioned, untestable, and locked to one host.
Solution
Every reusable building block lives in Git as plain text and syncs one-way into the front-end on a schedule; the front-end becomes replaceable, the content becomes an asset.
Architecture
Git repo (prompts · skills · knowledge · tools) → oikb sync (30 min) → Open WebUI → Any LLM
A small system with an outsized principle: content is infrastructure. The same discipline that governs code — version control, conventions, portability, secret hygiene — applied to the prompts and knowledge that make AI systems behave.
Repo evidence
- One-directional Git → front-end sync running every 30 minutes
- Written conventions — one concept per file, retrieval-priority naming, no secrets in tracked content, sanitized deployment records
- Knowledge packs covering infrastructure, methodology, and product briefs, portable to any host