---
name: vault-structure
description: Build or repair Obsidian vault structure, including hubs, folder notes, navigation links, naming consistency, and canonical note placement.
---

# Vault Structure

Use this skill when the vault needs better navigation, cleaner hierarchy, or repaired structure.

## MCP

Use the `obsidianVaultFilesystem` MCP server for all vault reads and writes.

- call `list_allowed_directories` first when the allowed vault root is unclear
- use absolute vault paths such as `$HOME/Documents/Obsidian Vault/...`; relative paths resolve against the MCP process working directory, not the vault root
- respect configured retrieval roots and exclusions while gathering context
- apply structural edits only after checking affected paths
- before the first Vault file operation, call `get_vault_status` on `obsidianVaultFilesystem`; if it is not `ready`, call `configure_vault` so the user can select and connect a local Vault in the MCP App UI; do not use `Md.obsidian Integration`, Computer Use, or open Obsidian for setup; if MCP remains unavailable, stop and explain that the Vault was not checked

## Workflow

1. Identify the area that should become canonical.
2. Use the `vault-context` relevance workflow for that area. Inspect its hubs, folder notes, and linked entry points before looking elsewhere in the vault.
3. Propose the smallest structural change that improves navigation.
4. Update links consistently if a note moves or is renamed.
5. Keep similar content together inside the same area.

## Output

- structure proposal
- affected folders and notes
- link migration notes

## Rules

- prefer stable hub notes for each area
- do not create duplicate canonical notes
- do not rename or move without link awareness