# Obsidian Structure

> Enforce PARA structure and tags in Obsidian vault properly

- Skill: `majiayu000/obsidian-structure` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add majiayu000/obsidian-structure`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/obsidian-structure/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/majiayu000/obsidian-structure

---


# Skill: obsidian-structure

## What I do

I provide expertise in architecting and maintaining an Obsidian vault using the PARA method (Projects, Areas, Resources, Archive). I specialise in defining folder hierarchies, tagging conventions, and linking patterns that ensure the vault remains navigable, scalable, and organised as it grows.

## When to use me

- When setting up a new vault or reorganising an existing one.
- When deciding whether to use a folder, a tag, or a link for a new piece of information.
- When creating a Map of Content (MOC) to provide a high-level entry point to a topic.
- When archiving completed projects to keep the active workspace clean and focused.

## Core principles

1. **Actionability-Based Sorting (PARA)** — Organise notes by their level of actionability: Projects (active), Areas (ongoing responsibilities), Resources (topics of interest), and Archive (completed or inactive).
2. **The MOC Pattern** — Use "Maps of Content" as non-linear indices to group related notes without relying solely on rigid folder structures.
3. **Flat over Deep** — Prefer shallower folder structures combined with robust linking and tagging to avoid losing notes in deep sub-folder hierarchies.
4. **Naming Consistency** — Use \`Title Case\` for note names and \`kebab-case\` for tags to maintain a professional and scannable interface.

## Patterns & examples

### PARA Folder Hierarchy
A standard top-level structure for the vault.
- \`1. Projects/\` — Active tasks with a deadline.
- \`2. Areas/\` — Ongoing responsibilities (e.g. Finances, Health).
- \`3. Resources/\` — Knowledge base, interests, and references.
- \`4. Archive/\` — Completed projects and inactive areas.
- \`Templates/\` — Reusable note structures.

### The Index Note (MOC)
A central hub for a specific resource area.
```markdown
# Obsidian Knowledge Base MOC
Index of all notes related to vault management.

## Core Components
- [[Obsidian Structure]]: PARA and organisation.
- [[Obsidian Frontmatter]]: Metadata standards.

## Advanced Scripting
- [[Obsidian Dataview Expert]]: Dynamic indexing.
- [[Obsidian CustomJS Expert]]: Reusable logic.
```

### Tagging Conventions
Hierarchical tags for multi-dimensional organisation.
- \`#status/in-progress\`
- \`#topic/git/workflow\`
- \`#type/permanent-note\`

## Anti-patterns to avoid

- ❌ **Folder Overload** — Creating a new folder for every minor sub-topic instead of using links or tags.
- ❌ **Tag Explosion** — Creating hundreds of unique tags that are only used once; this makes the tag cloud useless for filtering.
- ❌ **The Junk Drawer Folder** — Letting a "Misc" or "Inbox" folder grow indefinitely without regular processing and filing.
- ❌ **Ignoring the Archive** — Leaving finished projects in the active \`Projects\` folder, which creates visual clutter and mental load.

## KB Reference

`~/vaults/baphled/3. Resources/Knowledge Base/AI Development System/Skills/Session-Knowledge/Obsidian Structure.md`

## Related skills

- `obsidian-frontmatter` — For defining the metadata that supports structural organisation.
- `information-architecture` — For the underlying theory of knowledge organisation.
- `obsidian-consolidation` — For refining and merging notes as the vault structure evolves.
- `note-taking` — For capturing the atomic content that populates the PARA structure.
- `knowledge-base` — For querying the structural health of the vault.