bitflower

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.

bitflower

description	Start a brainstorming session to create a feature specification
argument-hint	<feature-name>

Feature Specification or Bug Investigation

Start a collaborative session for: $ARGUMENTS

Mode Detection

bitflower

// import { createFilter } from 'rollup-pluginutils'

function assign(target, source) {
  Object.keys(source).forEach((key) => {
    target[key] = source[key];
  });
  return target;
}

// const DEFAULT_HEADER = 'import React from \'react\';'

bitflower

<key>LSSupportsOpeningDocumentsInPlace</key>
<true/>
<key>UIFileSharingEnabled</key>
<true/>

bitflower

let moduleExports = (app: Application) => {
  const authentication = new AuthenticationService(app);

  // authentication.register('jwt', new JWTStrategy());
  // authentication.register('local', new LocalStrategy());
  // authentication.register('google', new GoogleStrategy());
  authentication.register('microsoft', new MicrosoftStrategy()); // TODO: Let add from the cloud-app?

  // authentication.register('microsoft', new OidcStrategy());

bitflower

// src/global/app.ts

import { setup } from './vendor/shoelace';

export default async function (): Promise<void> {
  setup();
}

bitflower

Add this to you AndroidManifest.xml in the application element

<application
    ...
    android:usesCleartextTraffic="true"
    ...

Link: https://stackoverflow.com/questions/60906953/ionic-5-capacitor-err-cleartext-not-permitted-in-android

bitflower

The 2014-03-03T... notation is a fancy JavaScript Date Time String Format and expects a time zone. If you don't provide one, it defaults to Z (UTC).

The 2014-03-03 18:30:00 notation, however, is just a regular string without an interesting name and, if you don't provide a time zone, it assumes local time.

This info was taken from the MDN article about Date.parse().

Link: https://stackoverflow.com/questions/22151477/javascript-iso-8601-string-into-date-object

bitflower

...
    <key>UIFileSharingEnabled</key>
    <true/>
    <key>LSSupportsOpeningDocumentsInPlace</key>
    <true/>
...

bitflower

import { OPCUAClient, OPCUAClientOptions } from 'node-opcua';

import { CO_OPCUA_CLIENT_DEFAULTS } from './client-defaults';

import { CoOPCUAClientConfig } from '../config';

let client: OPCUAClient;

export const createClient = (options: CoOPCUAClientConfig) => {
  const optionsCombined: OPCUAClientOptions = {