ecesar88

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.

ecesar88

export const logFetchingSingleRecord = (id: string, obj?: Record<string, unknown>) => {
	logger({
		level: LOG_TYPE.INFO,
		message: `Fetching client with id '${id}'`,
    ...(obj ? ({
      object: colorizeAsJSON(obj),
    }) : ({}))
	});
}

ecesar88

" VimPlug START
" Specify a directory for plugins
" - For Neovim: stdpath('data') . '/plugged'
" - Avoid using standard Vim directory names like 'plugin'

" Autoinstall vim-plug if it isn't installed already
if empty(glob('~/.config/nvim/autoload/plug.vim'))
  silent !curl -fLo ~/.config/nvim/autoload/plug.vim --create-dirs
        \ https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim
  autocmd VimEnter * PlugInstall

ecesar88

enum EXCHANGE_RATE_REGIMES {
  FLOATING_EXCHANGE = "CÂMBIO FLUTUANTE",
}

class Person {
  constructor(age: number, name: string) {
    this.age = age;
    this.name = name;
  }

ecesar88

Quick examples

• feat: new feature
• fix(scope): bug in scope
• feat!: breaking change / feat(scope)!: rework API
• chore(deps): update dependencies

Commit types

• build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
• ci: Changes to CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
• chore: Changes which doesn't change source code or tests e.g. changes to the build process, auxiliary tools, libraries

ecesar88

import { AxiosError } from 'axios';
import { useCallback, useEffect, useRef, useState } from 'react';

interface useApiOptions<T = object, Args extends any[] = any[]> {
  queryFn: (...args: Args) => Promise<T>;
  onComplete?: (data: NonNullable<T>) => void;
  immediate?: boolean;
}

type ErrorType = {

ecesar88

import getValidations from "./validations";
import useForm from "src/hooks/useForm";

const {
    handleSubmit,
    registerKey,
    clearErrors,
    clearForm,
    validations: { validateSingleSchema, schema: validationSchema },
    formState: { errors, payload, setPayload },

ecesar88

// zSucrilhos' CS:GO config
// Updated 14/12/2022

// Launch options
// -novid -nojoy -nod3d9ex -no3d9ex1 -freq 60
// To test: '+snd_use_hrtf 0'

cl_disablefreezecam 1
cl_showloadout 1
cl_autowepswitch 0

ecesar88

Contribua

Se você quiser adicionar mais algum tópico deixe seu comentário, o objetico é facilitar para os iniciantes ou aqueles que buscam dominar JavaScript, quais tópicos são importantes para dominar JavaScript.

São tópicos para quem sabe o minimo de JavaScript (declarar variáveis), a ordem em que eles aparecem são por importância para o dominio como um todo. Mesmo que você já tenha experiência com JS, recomendo que leia os links de cada tópico para fortalecer suas bases teóricas e ter um comportamento mais profundo da linguagem.

Lista originalmente criada e compilada por Vinicius Reis

ecesar88

#!/bin/sh

# Usage:
# tabc.sh <tabbed-id> <command>
# Commands:
#    add <window-id> 	- Add window to tabbed
#    remove <window-id> - Remove window from tabbed
#    list				- List all clients of tabbed

#