القائمة
Surface unnamed patterns from recent vault activity. Reads N days of notes and finds recurring themes you haven't explicitly named. The vault notices what you don't.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Vault argues back. Pulls your own history to challenge current thinking. Use when making decisions, proposing architecture, or before committing to a direction. The vault is not a yes-man -- it remembers what you've learned the hard way.
Bridge unrelated vault domains. Find structural analogues between different areas. The vault's link graph knows connections you haven't seen.
Promote scattered vault mentions into dedicated notes. When an idea, pattern, or concept reaches critical mass (3+ mentions across contexts), it deserves its own page. Graduate it from scattered references to first-class citizen.
Ingest external content and REWRITE existing vault pages with new context. Not just "add a note" -- one source touches 5-15 existing pages. Resolves contradictions, updates claims, creates synthesis pages. The vault grows by integration, not accumulation.
Save everything worth keeping from the current conversation to the Obsidian vault. Use when conversation produces decisions, research, tasks, project updates, or insights. Also triggers on session wrap-up ("done", "that's it", "thanks").
Load vault context progressively -- identity, navigation, current state. Use at session start or when context about the vault is needed. Token-budgeted: start light, go deeper only as needed.
| name | vault-emerge |
| description | Surface unnamed patterns from recent vault activity. Reads N days of notes and finds recurring themes you haven't explicitly named. The vault notices what you don't. |
Find patterns hiding in your vault that you haven't named yet.
Read _CLAUDE.md at vault root for folder map.
Collect raw material -- spawn parallel reader agents (one per major folder):
Pattern detection -- look for:
Present findings as named patterns:
## Emerged Patterns (last N days)
### 1. [Pattern Name] -- [one-line description]
**Evidence:** [3+ specific notes with dates]
**Frequency:** [how often, across what contexts]
**So what:** [why this matters -- actionable implication]
**Suggestion:** [formalize as protocol? create concept note? investigate deeper?]
Rank by signal strength -- more evidence + more diverse sources = higher rank.
Ask: "Any of these worth naming? I can create concept notes for them."
Append to log.md: ## [YYYY-MM-DD] emerge | [N] patterns surfaced from [days] days
_CLAUDE.md Language section). Translate ALL template headings and labels. E.g., Chinese user sees "## 浮现的模式", "### 1. [模式名]", "证据：", not English. Pattern names should be in the user's language. Evidence quotes stay in original language. Search in all languages present in the vault.