Skip to content
obsidian-wiki

Folder structure

Every wiki lands on the same shape on disk: three zones plus two config files and an index at the root. Folder names are yours to choose at setup; the machinery underneath stays the same.

WIKI ROOT <wiki-root>/ CLAUDE.md generic schema, identical across every wiki this plugin manages wiki-config.md this wiki's specific configuration; edit to reconfigure index.md auto-maintained catalog of every page ZONE 1, ENTRY POINTS you drop files here; the agent reads them on /ingest 99_Quick-notes/ raw notes, brain dumps, your inbox 98_Other/ articles, PDFs, web clips you save 4_Conversations/ LLM session exports (custom) add your own at setup: voice transcripts, daily journal, images... ZONE 2, STRUCTURED KNOWLEDGE where /ingest writes distilled output; you can read and edit by hand 1_Projects/ active work, one folder per category, archived ones in _old/ 3_Documentation/ durable knowledge articles, the agent's main output 2_Resources/ lists, references, personal memory (custom) people, concepts, anything you declare in wiki-config.md ZONE 3, _SERVICE/, AGENT-ONLY STATE tracking, logs, feedback; do not edit by hand unless you know why .manifest.json sha256 ledger of every ingested source, enables incremental reruns log.md append-only operation log hot.md last 20 touched pages, for cheap 'what changed?' queries feedback.md behavioral rules you've taught the agent via /feedback sources/ one summary page per ingested source, with backlinks to pages _archives/ timestamped snapshots from /archive and pre-/rebuild entry-points/ where source files are moved after post_ingest: move lint-<date>.md latest /lint report, per-day file custom-procedures/ optional: per-wiki procedure files (task-extraction, ...). User-authored. Everything in _service/ is regenerable from sources via /rebuild, except feedback.md. FOCAL: YOUR CUSTOMIZATION MONOSPACE = FILE OR FOLDER NAMES CONFIGURABLE AT SETUP

Folder names are chosen at setup

Section titled “Folder names are chosen at setup”

The diagram uses one example naming scheme. The names of the entry points and knowledge folders are yours to pick during /setup-wiki; nothing in the commands hard-codes them. Two people running this plugin can end up with folder trees that look nothing alike, while the three-zone layout and the operating contract stay identical.

The two config files drive everything

Section titled “The two config files drive everything”

Two files at the root drive everything, and every command reads both on every invocation.

CLAUDE.md is generic boilerplate, identical across every wiki this plugin manages. It describes the three-zone architecture, the hard boundary, folder permissions, routing rules, page types, and the reading order. Do not edit it by hand; /setup-wiki writes it from the plugin template and /upgrade refreshes it when the template changes.

wiki-config.md is your wiki’s configuration and the file you actually edit. Its frontmatter holds the name, slug, root path, entry points (each with a path, source type, default quality, post-ingest rule, and exclude list), knowledge folders, dashboards, protected paths, project thresholds, tag vocabulary, and writing style. The body holds free-form prose about page types, naming conventions, and any wiki-specific rules.

Section titled “Related reference”