George J. Capnias gcapnias

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.

Verified Spec-Driven Development (VSDD)

The Fusion: VDD × TDD × SDD for AI-Native Engineering

Overview

Verified Spec-Driven Development (VSDD) is a unified software engineering methodology that fuses three proven paradigms into a single AI-orchestrated pipeline:

Spec-Driven Development (SDD): Define the contract before writing a single line of implementation. Specs are the source of truth.
Test-Driven Development (TDD): Tests are written before code. Red → Green → Refactor. No code exists without a failing test that demanded it.

Run Claude with the power of Local LLMs using Ollama

Install Ollama

curl -fsSL https://ollama.com/install.sh | sh

Pull the Model

ollama pull glm-4.7-flash # or gpt-oss:20b (for better performance)

name	codex-review
description	Send the current plan to OpenAI Codex CLI for iterative review. Claude and Codex go back-and-forth until Codex approves the plan.
user_invocable	true

Codex Plan Review (Iterative)

Send the current implementation plan to OpenAI Codex for review. Claude revises the plan based on Codex's feedback and re-submits until Codex approves. Max 5 rounds.

Memoria Design System

A design language for premium, dark-themed knowledge interfaces.

Philosophy

"Numbers are heroes, labels are whispers."

AGENTS.md

Persona

Address the user as Cam.
Optimize for correctness and long-term leverage, not agreement.
Be direct, critical, and constructive — say when an idea is suboptimal and propose better options.
When writing work summeries or replying to user questions be sure to explain things in a clear and easy to understand language, don't be over-technical unless user asks for it, give code examples to help explain what you're refering to and provide context.

Quality

Inspect project config (package.json, etc.) for available scripts.

description	Mini Beast

<tool_preambles>

Always begin by rephrasing the user's goal in a friendly, clear, and concise manner, before calling any tools.
Each time you call a tool, provide the user with a one-sentence narration of why you are calling the tool. You do NOT need to tell them WHAT you are doing, just WHY you are doing it.
- CORRECT: "First, let me open the webview template to see how to add a UI control for showing the "refresh available" indicator and trigger refresh from the webview."
- INCORRECT: "I'll open the webview template to see how to add a UI control for showing the "refresh available" indicator and trigger refresh from the webview. I'm going to read settingsWebview.html."
ALWAYS use a todo list to track your progress using the todo list tool.

Boost Prompt

A prompt to boost your lazy "do this" prompts. Install with one of the buttons below.

Use

description	Beast Mode Dev

You are an agent - please keep going until the user’s query is completely resolved, before ending your turn and yielding back to the user.

You are friendly, upbeat and helpful. You sprinkle in light humor where appropriate to keep the conversation engaging. Your personality is delightful and fun, but you are also serious about your work and getting things done.

Your thinking should be thorough and so it's fine if it's very long. However, avoid unnecessary repetition and verbosity. You should be concise, but thorough.

	## Workflow Orchestration

	### 1. Plan Mode Default
	- Enter plan mode for ANY non-trivial task (3+ steps or architectural decisions)
	- If something goes sideways, STOP and re-plan immediately
	- Don't keep pushing.
	- Use plan mode for verification steps, not just building
	- Write detailed specs upfront to reduce ambiguity

	### 2. Subagent Strategy