kibotu

Prompt Injection & Jailbreak Techniques — Comprehensive Reference

Purpose & scope. A defensive/educational knowledge base cataloguing known prompt-injection and jailbreak patterns, the models/systems they have affected, and the defenses against them. Compiled from primary literature (arXiv papers, vendor disclosures) and security research, June 2026.

How to read this. Every technique lists: how it works, an illustrative structural skeleton (the shape of the attack, not a weaponized payload), the models/systems it was reported against, and its current status. Examples are deliberately defanged. >

karpathy

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.

rohitg00

LLM Wiki v2

A pattern for building personal knowledge bases using LLMs. Extended with lessons from building agentmemory 20K+ Stars ⭐️, a persistent memory engine for AI coding agents.

This builds on Andrej Karpathy's original LLM Wiki idea file. Everything in the original still applies. This document adds what we learned running the pattern in production: what breaks at scale, what's missing, and what separates a wiki that stays useful from one that rots.

What the original gets right

The core insight is correct: stop re-deriving, start compiling. RAG retrieves and forgets. A wiki accumulates and compounds. The three-layer architecture (raw sources, wiki, schema) works. The operations (ingest, query, lint) cover the basics. If you haven't read the original, start there.

cpursley

PostgreSQL is Enough

See the new site: https://postgresisenough.dev

---

• Simplify: move code into database functions
• Just Use Postgres for Everything
• Just use Postgres
• PostgreSQL is the worlds’ best database

Klerith

Instalar dependencias Testing

1. Vitest

npm install --save-dev vitest jsdom

2. React Testing Library

Postrediori

MS Visual Studio Installers and ISO direct links

Contents

• VS 2019
• VS 2017
  • VS 2017 Express
• VS 2015
  • VS 2015 Original release (without updates)
  • VS 2015 Express

dsample

ASCI art characters for creating diagrams

Characters:

Single line

• ASCII code 191 = ┐ ( Box drawing character single line upper right corner )
• ASCII code 192 = └ ( Box drawing character single line lower left corner )
• ASCII code 193 = ┴ ( Box drawing character single line horizontal and up )
• ASCII code 194 = ┬ ( Box drawing character single line horizontal down )

josejuansanchez

DROP DATABASE IF EXISTS universidad;
CREATE DATABASE universidad CHARACTER SET utf8mb4;
USE universidad;
 
CREATE TABLE departamento (
    id INT UNSIGNED AUTO_INCREMENT PRIMARY KEY,
    nombre VARCHAR(50) NOT NULL
);

CREATE TABLE persona (

santoshshinde2012

Resources to start with Multi-tenant Architecture

Introduction

Multi tenant architecture is an ecosystem or model, in which a single environment can serve multiple tenants utilising a scalable, available, and resilient architecture. The underlying infrastructure is completely shared, logically isolated, and with fully centralised services.

SaaS Deep Dive: Designing and Building Multi-Tenant Solutions • Tod Golding • GOTO 2020

Creating a multi-tenant software-as-a-service (SaaS) application requires developers and architects to take new approaches to how they design, build, operate, and deploy their solutions. SaaS touches every dimension of your design, including how you decompose your system into services, how those services are built, how they are secured, how they store data, and how they are deployed.