This handbook serves as a comprehensive guide to the architectural choices, design patterns, and technology stack for projects leveraging Feature-First Clean Architecture and Elysia.
Discover gists
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.
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.
| Function UploadFiles(aFiles, aAlias : String) : Boolean; | |
| Var | |
| aaAlias : String; | |
| Begin | |
| Result := False; | |
| if MyFTP.Connected Then MyFTP.Disconnect; | |
| MyFTP.Host := sFTPHost; | |
| MyFTP.Username := sFTPUserID; | |
| MyFTP.Password := sFTPPass; | |
| aaAlias := '<..Folder FTP server..>' + aAlias; |
- Enter plan mode for ANY non-trivial task (3+ steps or architectural decisions)
- If something goes sideways, STOP and re-plan immediately - don't keep pushing
- Use plan mode for verification steps, not just building
- Write detailed specs upfront to reduce ambiguity
- Use subagents liberally to keep main context window clean
| tf is this gist thing | |
| oh do i have to write a code here? | |
| cool. | |
| why? |
| {#--------------------------------------------------------------------- | |
| custom_pub_chat_template_qwen36.jinja | |
| ===================================== | |
| A public, harness-friendly fork of Qwen's Qwen3.6-27B chat template, | |
| tuned for open-source agentic coding harnesses like: | |
| - anomalyco/opencode (https://github.com/anomalyco/opencode) | |
| - earendil-works/pi (https://github.com/earendil-works/pi) | |
| - openclaw, OpenHarness, similar Claude-Code-style harnesses | |
| WHY THIS FORK EXISTS |
| {#--------------------------------------------------------------------- | |
| custom_pub_chat_template_gemma4.jinja | |
| ===================================== | |
| A public, harness-friendly fork of Google's Gemma 4 chat template, | |
| tuned for open-source agentic coding harnesses like: | |
| - anomalyco/opencode (https://github.com/anomalyco/opencode) | |
| - earendil-works/pi (https://github.com/earendil-works/pi) | |
| - openclaw, OpenHarness, similar Claude-Code-style harnesses | |
| WHY THIS FORK EXISTS |
| name | wiki |
|---|---|
| description | Compile personal data (journals, notes, messages, whatever) into a personal knowledge wiki. Ingest any data format, absorb entries into wiki articles, query, cleanup, and expand. |
| argument-hint | ingest | absorb [date-range] | query <question> | cleanup | breakdown | status |
You are a writer compiling a personal knowledge wiki from someone's personal data. Not a filing clerk. A writer. Your job is to read entries, understand what they mean, and write articles that capture understanding. The wiki is a map of a mind.
If you, like me, resent every dollar spent on commercial PDF tools,
you might want to know how to change the text content of a PDF without
having to pay for Adobe Acrobat or another PDF tool. I didn't see an
obvious open-source tool that lets you dig into PDF internals, but I
did discover a few useful facts about how PDFs are structured that
I think may prove useful to others (or myself) in the future. They
are recorded here. They are surely not universally applicable --
the PDF standard is truly Byzantine -- but they worked for my case.