メニュー
Obsidian project note conventions — base files, embeds, Dataview, frontmatter fields, folder notes. USE WHEN creating project notes, checking project compliance, or working with Project.base views.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Resolve Obsidian Base files (.base) to see what the user sees in Obsidian. USE WHEN the user asks about Base views, queries vault notes, wants to see what a .base file shows, or needs filtered/sorted vault data. Wraps the obsidian-base CLI.
Vault conventions for wikilinks, frontmatter and tags. USE WHEN working with Obsidian vault files.
Obsidian template management — dual-tree creation, editing, rendering, frontmatter schemas, dynamic query blocks, Templater config updates. USE WHEN creating templates, editing templates, rendering templates, modifying template schemas, updating Templater folder mappings, adding query blocks, or checking template compliance.
Validate vault files against .mdschema files — structural checks on frontmatter, headings, and required sections. USE WHEN validate vault, check vault, vault lint, schema check, validate journals, validate memory.
Add [[wikilinks]] to a markdown document by matching terms against existing vault notes — body links and frontmatter keywords/related enrichment. USE WHEN a document needs wikilinks, terms should link to vault notes, knowledge graph needs enrichment, or enrich keywords.
[DEPRECATED] Use /ObsidianCLI instead. Obsidian Actions URI — atomic frontmatter props-set, rename with backlink updates, create notes, open notes. USE WHEN Obsidian Actions, actions URI, property set, rename note.
| name | ProjectConventions |
| version | 0.1.0 |
| description | Obsidian project note conventions — base files, embeds, Dataview, frontmatter fields, folder notes. USE WHEN creating project notes, checking project compliance, or working with Project.base views. |
Obsidian project note conventions — base files, embeds, Dataview integration, and frontmatter field definitions.
Templates/PARA/Project.md — the canonical project template (static).
Templates/PARA/Project.js.md — the Templater version.
Every project note must include these embeds in order:
![[Assets.base]]
---
![[Project.base#Resources]]
---
![[Project.base#Events]]
> [!tasks]- Tasks
>
> ```dataviewjs
> await dv.view("Scripts/Dataview/views/logs");
> await dv.view("Scripts/Dataview/views/tasks");
> ```
## Work log
### [[YYYY-MM-DD]]
- {One-liner per work item. Wikilink people, projects, technologies.}
The Base file provides three filtered views of backlinked notes:
| View | Shows | Filter |
|---|---|---|
| Resources | All linked notes except projects, journals, events | Grouped by root, sorted by name |
| Events | Notes tagged type/event | Sorted by name |
| Journals | Notes tagged type/journal with backlink | List format, comma-separated |
project.status — scalar: planned, active, on-hold, completedproject.priority — scalar: Critical, High, Medium, Lowcollection: "[[Projects]]" — standard collection linkkeywords — wikilinks to topics, technologies, systems (never tags)related — wikilinks to related projects or notesproject.team — wikilinks to people involvedproject.objectives — short text objectives for the projectEvery project lives in Projects/<Name>/<Name>.md. The folder note IS the project note. Associated files (plans, designs, references) live alongside in the same folder. The Folder Notes plugin renders the note when clicking the folder in the sidebar.