A general guide for humans building AI rule systems, and for AI agents learning how to read and apply them. Covers: Cursor, Claude Code, Gemini CLI, Google Antigravity, OpenCode, OpenAI Codex, GitHub Copilot.
A prompt tells an AI what to do once.
| const std = @import("std"); | |
| const assert = std.debug.assert; | |
| entropy: []const u8, | |
| pub const Error = error{OutOfEntropy}; | |
| const FRNG = @This(); | |
| pub fn init(entropy: []const u8) FRNG { |
A general guide for humans building AI rule systems, and for AI agents learning how to read and apply them. Covers: Cursor, Claude Code, Gemini CLI, Google Antigravity, OpenCode, OpenAI Codex, GitHub Copilot.
A prompt tells an AI what to do once.
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.
| /** | |
| * dwmconfig.h | |
| * Hardware multimedia keys | |
| */ | |
| /* Somewhere at the beginning of config.h include: */ | |
| /* | |
| You obviously need the X11 development packages installed, X11proto in particular, but | |
| here is the location of the keysyms header upstream copy if you can't bother | |
| using the contents of your own hard drive. ;-P |
Create a production-quality Hermes skill named openrouter-expert that makes you excellent at building with OpenRouter and the OpenRouter SDKs.
This is not a notes file. It must be an agent-optimized resolver skill: compact, durable, triggerable, and designed to look up the right current docs before making claims or writing code.
Source material to read first:
The way you approach solving a coding problem—how you think, communicate, and refine—is often more valuable than simply arriving at the right answer. Use ChatGPT as a supportive partner as you work incrementally through the six steps of the UMPIRE framework:
Understand → Match → Plan → Implement → Review → Evaluate
| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="UTF-8" /> | |
| <meta name="viewport" content="width=device-width, initial-scale=1.0" /> | |
| <title>Game-Style Progress Bar Prototype</title> | |
| <style> | |
| :root { | |
| --bg: #0b1020; | |
| --panel: rgba(10, 16, 32, 0.72); |