name: plan-mega-review
version: 2.0.0
description: |
The most thorough plan review possible. Three modes: SCOPE EXPANSION (dream big,
build the cathedral), HOLD SCOPE (review what's here with maximum rigor), and
SCOPE REDUCTION (strip to essentials). Context-dependent defaults, but when the
user says EXPANSION — go full send. Challenges premises, maps every failure mode,Discover gists
| name | wiki |
|---|---|
| description | Compile personal data (journals, notes, messages, whatever) into a personal knowledge wiki. Ingest any data format, absorb entries into wiki articles, query, cleanup, and expand. |
| argument-hint | ingest | absorb [date-range] | query <question> | cleanup | breakdown | status |
You are a writer compiling a personal knowledge wiki from someone's personal data. Not a filing clerk. A writer. Your job is to read entries, understand what they mean, and write articles that capture understanding. The wiki is a map of a mind.
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.
| Windows Registry Editor Version 5.00 | |
| [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\PriorityControl] | |
| "ConvertibleSlateMode"=dword:00000001 |
| #!/usr/bin/env bash | |
| echo "──────────────────────────────────────────────" | |
| echo " Removing Python's EXTERNALLY-MANAGED lock " | |
| echo "──────────────────────────────────────────────" | |
| echo "* Developed and engineered by:" | |
| echo "* Felipe Alfonso Gonzalez <f.alfonso@res-ear.ch>" | |
| echo "* Computer Science Engineer" | |
| echo "* Chile" | |
| echo "------------------------------------------------" |
I've been running Andrej Karpathy's LLM Wiki pattern for several months — reading sources, compiling them into a compounding, git-diffable wiki instead of re-deriving everything from scratch every session — and I'm a genuine convert. But two things kept nagging at me: query salience (finding the right page reliably, not just something plausible) and token economy (not re-reading half the wiki to answer one question).
100 prompt shortcuts that change how Claude responds. Type any code at the start of your message.
Interactive searchable version with copy-to-clipboard: clskills.in/prompts
| Code | What it does |
|---|
| javascript:(function(){var destination = prompt("Destination (Don't include http/https: ");window.location='https://translate.google.com/translate?sl=auto&tl=en&u='+'https://'+destination})(); |