wiki-mode

Name: wiki-mode
Author: AgriciDaniel

164installs1.1kforks

How to install wiki-mode?

agricidaniel/claude-obsidian/wiki-mode

$npx -y skills add AgriciDaniel/claude-obsidian --skill wiki-mode

Installs into the current project.

Summary

Methodology modes for the Compound Vault. Lets the vault declare an organizational style (LYT / PARA / Zettelkasten / Generic) that wiki-ingest, save, and autoresearch consult before filing new pages. Reads .vault-meta/mode.json; defaults to generic (v1.6/v1.7 behavior) when

Files · 1

View on GitHub

SKILL.md

1	# wiki-mode: Methodology Modes for the Compound Vault
2
3	The v1.6 + v1.7 vault structure was opinion-free — `wiki/sources/`, `wiki/entities/`, `wiki/concepts/`, and so on. That works for power-users with their own organizational instincts. It does NOT serve the large segment of Obsidian users who want a named methodology to follow.
4
5	v1.8 ships `wiki-mode` to close that gap. A vault declares a mode (LYT, PARA, Zettelkasten, or Generic) in `.vault-meta/mode.json`; the other skills consult it before deciding where to file new pages. Mode = `generic` is the default and preserves v1.6/v1.7 behavior exactly.
6
7	Per May 2026 compass artifact: This was priority gap 5 of the 5 identified. Ideaverse Pro 2.0 ($200 paid vault) ships LYT as an opinionated structure; no Claude+Obsidian competitor ships PARA / Zettelkasten / mode-aware routing as a first-class skill. v1.8 takes us from TIE → LEAD on the audit §9 methodology-support axis (5 of 7 axes #1).
8
9	---
10
11	## The four modes
12
13	### LYT (Linking Your Thinking — Nick Milo)
14
15	Philosophy: notes link, folders don't. The organizational primitive is the MOC (Map of Content) — a hub note that links into a cluster of atomic notes. You never browse folders; you navigate by following links.
16
17	Filing convention:
18	- `wiki/mocs/<topic>-moc.md` — the MOC for a topic cluster
19	- `wiki/notes/<atomic-note>.md` — flat list of atomic notes, named by their idea, all linked from at least one MOC
20
21	When to use: mid-to-large knowledge bases (>100 notes), users who think in terms of conceptual clusters, knowledge graphs.
22
23	### PARA (Tiago Forte)
24
25	Philosophy: organize by actionability, not topic. Active work in Projects, ongoing responsibilities in Areas, reference material in Resources, completed/inactive in Archives.
26
27	Filing convention:
28	- `wiki/projects/<project-name>/<note>.md` — active projects with a deadline/outcome
29	- `wiki/areas/<area-name>/<note>.md` — ongoing responsibilities (no deadline)
30	- `wiki/resources/<topic>/<note>.md` — reference material, organized by topic
31	- `wiki/archives/<year>/<note>.md` — completed projects, sunsetted areas
32
33	When to use: workflow-heavy users, knowledge workers managing many projects, GTD-adjacent practitioners.
34
35	### Zettelkasten (Niklas Luhmann's slip-box)
36
37	Philosophy: atomic notes, unique IDs, dense bidirectional linking. No folders. Every note answers exactly one idea. Notes find each other by ID references.
38
39	Filing convention:
40	- `wiki/<YYYYMMDDHHMMSSffffff>-<slug>.md` — flat, timestamped IDs (20 digits = date + microseconds, collision-resistant)
41	- Every note has `id:`, `parent_id:` (optional), `child_ids:` (optional) in frontmatter
42	- No subdirectories; the wiki/ root is the whole vault
43
44	When to use: academics, researchers, long-term thinkers building permanent knowledge artifacts. Highest discipline; smallest filing surface.
45
46	### Generic (default — v1.7 behavior)
47
48	Filing convention: preserves the v1.6/v1.7 default — `wiki/sources/`, `wiki/entities/`, `wiki/concepts/`, `wiki/<domain>/`. No opinion imposed.
49
50	When to use: when you don't want to commit to a methodology, or you're migrating from v1.7 and want zero behavior change.
51
52	---
53
54	## How to set the mode
55
56	```bash
57	bash bin/setup-mode.sh
58	```
59
60	Interactive prompt: pick one of the 4 modes. Writes `.vault-meta/mode.json`. Optionally seeds template folders (LYT `mocs/`, PARA `projects/areas/resources/archives/`).
61
62	To check the current mode programmatically:
63
64	```bash
65	cat .vault-meta/mode.json \| python3 -c 'import json,sys; print(json.load(sys.stdin)["mode"])'
66	```
67
68	To switch modes later: re-run `setup-mode.sh`. Existing files are NOT auto-migrated; the new mode only affects newly-filed pages from that point. Migration is a manual operation (see [migration section](#migration-between-modes) below).
69
70	---
71
72	## Mode config schema (`.vault-meta/mode.json`)
73
74	```json
75	{
76	"schema_version": 1,
77	"mode": "lyt\|para\|zettelkasten\|generic",
78	"configured_at": "ISO-8601 timestamp",
79	"config": {
80	"lyt": {
81	"moc_folder": "wiki/mocs/",
82	"notes_folder": "wiki/notes/"
83	},
84	"para": {
85	"projects_folder": "wiki/projects/",
86	"areas_folder": "wiki/areas/",
87	"resources_folder": "wiki/resources/",
88	"archives_folder": "wiki/archives/"
89	},
90	"zettelkasten": {
91	"id_format": "YYYYMMDDHHMMSSffffff",

AgriciDanielPublisher · 206 listings

Preview

AgriciDaniel/claude-obsidian

# wiki-mode: Methodology Modes for the Compound Vault

The v1.6 + v1.7 vault structure was opinion-free — `wiki/sources/`, `wiki/entities/`, `wiki/concepts/`, and so on. That works for power-users with their own org

**v1.8 ships `wiki-mode` to close that gap.** A vault declares a mode (LYT, PARA, Zettelkasten, or Generic) in `.vault-meta/mode.json`; the other skills consult

**Per May 2026 compass artifact**: This was priority gap 5 of the 5 identified. Ideaverse Pro 2.0 ($200 paid vault) ships LYT as an opinionated structure; no Cl

RepoAgriciDaniel/claude-obsidian

LicenseMIT

TypeSkills

CategoryProductivity

UpdatedMay 2026

Repo stars9.8k

First seenJul 22, 2026

People who liked this also viewed

6 picks

Type

wiki-mode

164installs1.1kforks

View on GitHub

How to install wiki-mode?

agricidaniel/claude-obsidian/wiki-mode

$npx -y skills add AgriciDaniel/claude-obsidian --skill wiki-mode

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# wiki-mode: Methodology Modes for the Compound Vault
2
3	The v1.6 + v1.7 vault structure was opinion-free — `wiki/sources/`, `wiki/entities/`, `wiki/concepts/`, and so on. That works for power-users with their own organizational instincts. It does NOT serve the large segment of Obsidian users who want a named methodology to follow.
4
5	v1.8 ships `wiki-mode` to close that gap. A vault declares a mode (LYT, PARA, Zettelkasten, or Generic) in `.vault-meta/mode.json`; the other skills consult it before deciding where to file new pages. Mode = `generic` is the default and preserves v1.6/v1.7 behavior exactly.
6
7	Per May 2026 compass artifact: This was priority gap 5 of the 5 identified. Ideaverse Pro 2.0 ($200 paid vault) ships LYT as an opinionated structure; no Claude+Obsidian competitor ships PARA / Zettelkasten / mode-aware routing as a first-class skill. v1.8 takes us from TIE → LEAD on the audit §9 methodology-support axis (5 of 7 axes #1).
8
9	---
10
11	## The four modes
12
13	### LYT (Linking Your Thinking — Nick Milo)
14
15	Philosophy: notes link, folders don't. The organizational primitive is the MOC (Map of Content) — a hub note that links into a cluster of atomic notes. You never browse folders; you navigate by following links.
16
17	Filing convention:
18	- `wiki/mocs/<topic>-moc.md` — the MOC for a topic cluster
19	- `wiki/notes/<atomic-note>.md` — flat list of atomic notes, named by their idea, all linked from at least one MOC
20
21	When to use: mid-to-large knowledge bases (>100 notes), users who think in terms of conceptual clusters, knowledge graphs.
22
23	### PARA (Tiago Forte)
24
25	Philosophy: organize by actionability, not topic. Active work in Projects, ongoing responsibilities in Areas, reference material in Resources, completed/inactive in Archives.
26
27	Filing convention:
28	- `wiki/projects/<project-name>/<note>.md` — active projects with a deadline/outcome
29	- `wiki/areas/<area-name>/<note>.md` — ongoing responsibilities (no deadline)
30	- `wiki/resources/<topic>/<note>.md` — reference material, organized by topic
31	- `wiki/archives/<year>/<note>.md` — completed projects, sunsetted areas
32
33	When to use: workflow-heavy users, knowledge workers managing many projects, GTD-adjacent practitioners.
34
35	### Zettelkasten (Niklas Luhmann's slip-box)
36
37	Philosophy: atomic notes, unique IDs, dense bidirectional linking. No folders. Every note answers exactly one idea. Notes find each other by ID references.
38
39	Filing convention:
40	- `wiki/<YYYYMMDDHHMMSSffffff>-<slug>.md` — flat, timestamped IDs (20 digits = date + microseconds, collision-resistant)
41	- Every note has `id:`, `parent_id:` (optional), `child_ids:` (optional) in frontmatter
42	- No subdirectories; the wiki/ root is the whole vault
43
44	When to use: academics, researchers, long-term thinkers building permanent knowledge artifacts. Highest discipline; smallest filing surface.
45
46	### Generic (default — v1.7 behavior)
47
48	Filing convention: preserves the v1.6/v1.7 default — `wiki/sources/`, `wiki/entities/`, `wiki/concepts/`, `wiki/<domain>/`. No opinion imposed.
49
50	When to use: when you don't want to commit to a methodology, or you're migrating from v1.7 and want zero behavior change.
51
52	---
53
54	## How to set the mode
55
56	```bash
57	bash bin/setup-mode.sh
58	```
59
60	Interactive prompt: pick one of the 4 modes. Writes `.vault-meta/mode.json`. Optionally seeds template folders (LYT `mocs/`, PARA `projects/areas/resources/archives/`).
61
62	To check the current mode programmatically:
63
64	```bash
65	cat .vault-meta/mode.json \| python3 -c 'import json,sys; print(json.load(sys.stdin)["mode"])'
66	```
67
68	To switch modes later: re-run `setup-mode.sh`. Existing files are NOT auto-migrated; the new mode only affects newly-filed pages from that point. Migration is a manual operation (see [migration section](#migration-between-modes) below).
69
70	---
71
72	## Mode config schema (`.vault-meta/mode.json`)
73
74	```json
75	{
76	"schema_version": 1,
77	"mode": "lyt\|para\|zettelkasten\|generic",
78	"configured_at": "ISO-8601 timestamp",
79	"config": {
80	"lyt": {
81	"moc_folder": "wiki/mocs/",
82	"notes_folder": "wiki/notes/"
83	},
84	"para": {
85	"projects_folder": "wiki/projects/",
86	"areas_folder": "wiki/areas/",
87	"resources_folder": "wiki/resources/",
88	"archives_folder": "wiki/archives/"
89	},
90	"zettelkasten": {
91	"id_format": "YYYYMMDDHHMMSSffffff",

AgriciDanielPublisher · 206 listings

Preview

AgriciDaniel/claude-obsidian

# wiki-mode: Methodology Modes for the Compound Vault

The v1.6 + v1.7 vault structure was opinion-free — `wiki/sources/`, `wiki/entities/`, `wiki/concepts/`, and so on. That works for power-users with their own org

**v1.8 ships `wiki-mode` to close that gap.** A vault declares a mode (LYT, PARA, Zettelkasten, or Generic) in `.vault-meta/mode.json`; the other skills consult

**Per May 2026 compass artifact**: This was priority gap 5 of the 5 identified. Ideaverse Pro 2.0 ($200 paid vault) ships LYT as an opinionated structure; no Cl

RepoAgriciDaniel/claude-obsidian

LicenseMIT

TypeSkills

CategoryProductivity

UpdatedMay 2026

Repo stars9.8k

First seenJul 22, 2026

People who liked this also viewed

6 picks

Type