jokester

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.

jokester

用 Claude Code + OpenCLI 自动提交 GitHub DMCA 版权举报

记录一次用 AI Agent 自动完成 GitHub DMCA 侵权举报的完整过程。

背景

我的开源项目 jackwener/opencli 遭到 nashsu/opencli-rs 完整抄袭：

• 项目描述、README、命令文档、代码结构全部照搬
• 未保留版权声明

jokester

# Copyright (c) 2017 Cary Kempston

# Permission is hereby granted, free of charge, to any person obtaining a copy
# of this software and associated documentation files (the "Software"), to deal
# in the Software without restriction, including without limitation the rights
# to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
# copies of the Software, and to permit persons to whom the Software is
# furnished to do so, subject to the following conditions:

# The above copyright notice and this permission notice shall be included in all

jokester

Understand the Task: Grasp the main objective, goals, requirements, constraints, and expected output.
- Minimal Changes: If an existing prompt is provided, improve it only if it's simple. For complex prompts, enhance clarity and add missing elements without altering the original structure.
- Reasoning Before Conclusions: Encourage reasoning steps before any conclusions are reached. ATTENTION! If the user provides examples where the reasoning happens afterward, REVERSE the order! NEVER START EXAMPLES WITH CONCLUSIONS!
    - Reasoning Order: Call out reasoning portions of the prompt and conclusion parts (specific fields by name). For each, determine the ORDER in which this is done, and whether it needs to be reversed.
    - Conclusion, classifications, or results should ALWAYS appear last.
- Examples: Include high-quality examples if helpful, using placeholders [in brackets] for complex elements.
   - What kinds of examples may need to be included, how many, and whether they are complex enough to benefit from p

jokester

I love crafting new stuff and make things happen.

My interested fields includes:

• Web / GUI / Graphics
• ML / DL

jokester

theme: simple

---

DataFrame

Takeaway: they are spreadsheets

---

jokester

moved to https://github.com/jokester/debian-rbpi-btrfs-image

jokester

# poc of string interpolation in bash / github action

- name: print env variables to job output
  run: for v in `cat env` ; do echo "::set-env name=${v%%=*}::${v##*=}" ; done


- name: use (maybe ) in shell command
  run: docker push myrepo/myapp:${TAG_REF#refs/tags/}
  env:
    TAG_REF: ${{ github.ref }}

jokester

module Converter
  class BaseConverter
    def initialize input_file, **options
      @input_file = input_file
      @options = options
    end

    def write output_file, force: false
      if output_file.exist? && !force
        puts "  NOT overwriting #{output_file}. remove dest file and rerun or specify 'force' flag"

jokester

#cloud-config

# Set the hostname for this machine (takes precedence over hostname assigned by DHCP lease).
hostname: myhost
# Authorize SSH keys for the `rancher` sudoer user
ssh_authorized_keys:
  - ssh-rsa AAA...ZZZ example1@rancher