| <!doctype html> | |
| <html> | |
| <head> | |
| <title>This is the title of the webpage!</title> | |
| </head> | |
| <body> | |
| <p>This is an example paragraph. Anything in the <strong>body</strong> tag will appear on the page, just like this <strong>p</strong> tag and its contents.</p> | |
| </body> | |
| </html> |
| # ✨ Emoji Picker for Linux ✨ | |
| # Copies emojis to your clipboard on select. | |
| # | |
| # Install the Apple Color Emoji (https://github.com/samuelngs/apple-emoji-linux) font for Linux to get the iconic emoji style. | |
| # Uses rofi as dmenu was unable to render emojis: | |
| # https://gitlab.freedesktop.org/xorg/lib/libxft/-/issues/6 | |
| #!/bin/bash | |
| set -e |
Append this to your Obsidian vault's root CLAUDE.md (or create one if it doesn't exist). This gives Claude Code the context it needs to use the tooling.
## Karpathy LLM Knowledge Base Workflow
This vault operates as an LLM-compiled knowledge base. Raw sources go into `raw/`, the LLM compiles them into wiki articles scattered across topic directories, and indexes are auto-generated.
### Directory Additions
A prompt you give to an AI agent (Claude Code, Cursor, etc.) to set up the farvis personal wiki system from scratch. The agent will ask you questions and configure everything automatically.
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.
Resonance: A Plague Tale Legacy Trainer 2026 for Windows with God Mode, Unlock All Codex Entries, Unlock All Chapters, Unlock Everything, Change Resonance Points, Resonance Points Editor, profiles, hotkeys, configs, and a clean desktop workflow.
| dism /online /set-edition:serverstandard /productkey:VDYBN-27WPP-V4HQT-9VMD4-VMK7H /accepteula |
| 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.
| name | llm-council |
|---|---|
| description | Run any question, idea, or decision through a council of 5 AI advisors who independently analyze it, peer-review each other anonymously, and synthesize a final verdict. Based on Karpathy's LLM Council methodology. MANDATORY TRIGGERS: 'council this', 'run the council', 'war room this', 'pressure-test this', 'stress-test this', 'debate this'. STRONG TRIGGERS (use when combined with a real decision or tradeoff): 'should I X or Y', 'which option', 'what would you do', 'is this the right move', 'validate this', 'get multiple perspectives', 'I can't decide', 'I'm torn between'. Do NOT trigger on simple yes/no questions, factual lookups, or casual 'should I' without a meaningful tradeoff (e.g. 'should I use markdown' is not a council question). DO trigger when the user presents a genuine decision with stakes, multiple options, and context that suggests they want it pressure-tested from multiple angles. |
