← ClaudeAtlas

wiki-schemalisted

Vault knowledge schema for the obsidian-llm-wiki plugin. Defines the three-layer source model, page types, frontmatter schemas, tag rules, cross-linking conventions, and the format of _index.md, _log.md, _manifest.json, and hot.md. Read this before any wiki operation (ingest, scan, query, save, lint, hot, tags-refresh). Triggers on: wiki schema, wiki conventions, wiki structure, wiki rules.
ihudak/ihudak-claude-plugins · ★ 2 · AI & Automation · score 68
Install: claude install-skill ihudak/ihudak-claude-plugins
# Wiki Schema — obsidian-llm-wiki Vault knowledge schema for the wiki layer. All wiki skills read this file before operating. This is the single source of truth for conventions, boundaries, and formats. All `/wiki-*` slash commands follow these conventions identically across both Claude Code and GitHub Copilot. --- ## Critical Boundary Rule Wiki operations (ingest, scan, query, save, lint, hot, tags-refresh) MUST NEVER write to or delete files from: - `Meetings/` - `Daily/` - `Projects/` - `Customers/` - `People/` - `Clippings/` - `Research/` These are Layer 1 — read-only knowledge sources. The wiki reads them; it never modifies them. The wiki layer includes two task-management commands (`/wiki-task` and `/wiki-tasks-extract`) that intentionally write outside the wiki directory — to `Projects/` and `Tasks.md`. These commands follow the task-creation rules in `_shared/task-rules.md`. All other wiki operations remain wiki-directory-only. --- ## Three-Layer Source Model ``` Layer 1 — Sources (read-only for wiki): Meetings/ ← meeting notes (primary knowledge source) Daily/ ← daily notes — extract ## Notes and ## Worklog sections only; skip Dataview task queries (they are not content) Projects/ ← project context, decisions, tech stack includes Products/, Data Generators/, Jira/ subdirs Customers/ ← customer notes People/ ← person/team notes Clipping