メニュー
Search, create, and manage notes in the Obsidian vault with wikilinks and index notes. Use when user wants to find, create, or organize notes in Obsidian.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Break a PRD into independently-grabbable issues using tracer-bullet vertical slices. Use when user wants to convert a PRD to issues, create implementation tickets, or break down a PRD into work items.
Create a detailed refactor plan with tiny commits via user interview, then file it as a issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.
Triage a bug or issue by exploring the codebase to find root cause, then create a issue with a TDD-based fix plan. Use when user reports a bug, wants to file an issue, mentions "triage", or wants to investigate and plan a fix for a problem.
Create a PRD through user interview, codebase exploration, and module design, then submit as a issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.
GitHub operations via `gh` CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available), bulk operations across many repos (script with gh api), or when gh auth is not configured.
Guide for conducting security audits of C++ and Rust dependencies. Use when reviewing Cargo.toml, CMakeLists.txt, or evaluating third-party library security for supply chain risk assessment.
| name | obsidian-vault |
| description | Search, create, and manage notes in the Obsidian vault with wikilinks and index notes. Use when user wants to find, create, or organize notes in Obsidian. |
/home/nthorne/repos/notes/
These are the most important folders in the vault that you are most likely to interact with:
0.inbox - for new notes to be processed and organized. This is typically where new notes are created before being moved to the appropriate topic or index.
1.projects - for notes related to specific personal or work projects (sorted into the respective subfolder).
2.knowledge - for general knowledge notes. Work specific knowledge notes go into the work subfolder, while personal knowledge notes go into the personal subfolder. General knowledge notes that don't fit into work or personal can go directly in 2.knowledge.
4.archive - for old notes that are no longer actively referenced but may be useful for historical context or future reference. Think JIRA tickets that are closed but may be useful to keep for reference.
7.study - for notes related to learning and skill development. This can include notes on specific topics, concepts, or skills being studied.
I use a Zettlekasten structure so name notes like YYYYMMDDHHmm Note title.md , where "Note title" is a descritive title and the date prefix is the creation date. Also add below frontmatter at the top of each note (example follows file name example):
---
id: YYYYMMDDHHmm Note title
aliases:
- Note title
tags: []
---
[[wikilinks]] syntax: [[Note Title]]# Search by filename
find "/home/nthorne/repos/notes/" -name "*.md" | grep -i "keyword"
# Search by content
grep grep -rl "keyword" "/home/nthorne/repos/notes/" --include="*.md"
Or use Grep/Glob tools directly on the vault path.
### Create a new note
1. Use **Natrual casing** for filename
2. Write content as a unit of learning (per vault rules)
3. Add `[[wikilinks]]` to related notes at the bottom
4. If part of a numbered sequence, use the hierarchical numbering scheme
### Find related notes
Search for `[[Note Title]]` across the vault to find backlinks:
```bash
grep grep -rl "\\[\\[Note Title\\]\\]" "/home/nthorne/repos/notes/"
### Find index notes
```bash
find find "/home/nthorne/repos/notes/" -name "*Index*"