Emmanuel Salomon ManUtopiK

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

Personal Knowledge Wiki

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.

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.

3 Common Misunderstandings About Vue, and 4 Reasons Why I Choose Vue

Yutaro Koizumi

2025-09-30

A Frontend Night to Know the Respective Merits of Next.js vs Nuxt

Cursor's Memory Bank

I am Cursor, an expert software engineer with a unique characteristic: my memory resets completely between sessions. This isn't a limitation - it's what drives me to maintain perfect documentation. After each reset, I rely ENTIRELY on my Memory Bank to understand the project and continue work effectively. I MUST read ALL memory bank files at the start of EVERY task - this is not optional.

Memory Bank Structure

The Memory Bank consists of required core files and optional context files, all in Markdown format. Files build upon each other in a clear hierarchy:

flowchart TD

	/* eslint-disable @typescript-eslint/no-explicit-any */
	import type { Component } from "vue";
	import {
	memo,
	useEffect,
	useLayoutEffect,
	useMemo,
	useRef,
	useState,
	useCallback,

	/* eslint-disable @typescript-eslint/no-explicit-any */
	import type { Component } from "vue";
	import {
	memo,
	useEffect,
	useLayoutEffect,
	useMemo,
	useRef,
	useState,
	useCallback,

	#!/bin/bash

	# Default values
	PORT=22
	WITH_PASSPHRASE=false

	# Parse CLI arguments
	while [[ "$#" -gt 0 ]]; do
	case $1 in
	--server-name)

	#!/bin/bash

	# Default values
	SSH_ENABLE=false
	SSH_PORT=22
	SSH_ALLOW_FROM=""
	RESET=false

	# Args parsing
	while [[ "$#" -gt 0 ]]; do

	#!/bin/bash

	# Variables
	USERNAME="myuser"
	SSH_PORT=22
	EDIT_SSH_PORT=false
	SSHD_CONFIG="/etc/ssh/sshd_config"
	BACKUP_CONFIG="${SSHD_CONFIG}.bak_$(date +%Y%m%d%H%M%S)"

	# Args parsing

	import {
	defineConfig,
	presetIcons,
	presetTypography,
	presetWind3,
	transformerDirectives,
	transformerVariantGroup,
	} from 'unocss';

	export default defineConfig({