@jayjiang/byoao 1.1.0 → 1.1.2

package/src/assets/obsidian-skills/byoao-conventions.md

@@ -1,6 +1,6 @@
 ---
 name: byoao-conventions
-description: Use when creating or modifying notes in a BYOAO-structured vault. Enforces frontmatter, directory placement, wikilinks, and naming conventions.
+description: Use when creating or modifying notes in a BYOAO-structured vault. Enforces frontmatter requirements, wikilinks, and naming conventions.
 ---
 
 # BYOAO Document Conventions
@@ -11,34 +11,19 @@ You MUST follow these conventions when creating or modifying any note in this va
 
 Before creating any note:
 
-1. Read `AGENT.md` — check the Document Conventions section for vault-specific rules
-2. Check `Knowledge/Glossary.md` — know the domain terminology before writing
-3. Identify the correct template — match your note type to a template below
-4. Verify the target directory — place the file according to its `type`
+1. Read `AGENTS.md` — check the knowledge base structure and note types
+2. Identify the note type: `fleeting` (raw input), `literature` (processed reference), or `permanent` (atomic concept)
+3. Use `obsidian create` to create notes — never use file write tools directly
 
 ## Creating Notes
 
-You MUST use `obsidian create` to create notes in the vault — never use
-file write tools directly. Obsidian CLI ensures the file is tracked by
-Obsidian and templates are applied correctly.
-
-When a matching template exists:
+You MUST use `obsidian create` to create notes in the vault:
 
 ```
-obsidian create name="Feature Name" template="Feature Doc" path="Projects/"
-obsidian create name="Sprint N Handoff" template="Sprint Handoff" path="Sprints/"
-obsidian create name="Meeting Title" template="Meeting Notes"
-obsidian create name="Investigation Title" template="Investigation"
-obsidian create name="Decision Title" template="Decision Record"
-obsidian create name="YYYY-MM-DD" template="Daily Note" path="Daily/"
+obsidian create name="Note Title" content="<frontmatter + content>" silent
 ```
 
-If no template matches, construct frontmatter manually. `date` MUST be
-today's actual date — never a placeholder, never omitted:
-
-```
-obsidian create name="Note Title" content="---\ntitle: \"Note Title\"\ntype: reference\nstatus: draft\ndate: 2026-04-02\ntags: []\n---\n\n# Note Title\n" silent
-```
+For multiline content use `\n` for newline and `\t` for tab.
 
 ## Required Frontmatter
 
@@ -47,36 +32,19 @@ Every note MUST have these fields:
 | Field | Values |
 |-------|--------|
 | `title` | Descriptive title |
-| `type` | `feature`, `sprint-handoff`, `meeting`, `investigation`, `decision`, `daily`, `reference`, `person` |
-| `status` | `draft`, `active`, `completed`, `archived` |
-| `date` | YYYY-MM-DD |
+| `note_type` | `fleeting`, `literature`, or `permanent` |
+| `type` | `meeting`, `idea`, `reference`, `daily`, `project`, `person`, etc. |
+| `date` | YYYY-MM-DD — today's date or extracted from content |
 | `tags` | Array of relevant tags |
 
-Additional fields by type:
+Additional fields (optional):
 
-| type | Additional Fields |
-|------|-------------------|
-| `feature` | `project`, `jira`, `stakeholders`, `priority` |
-| `sprint-handoff` | `sprint`, `sprint-dates`, `jira-board` |
-| `meeting` | `participants`, `meeting-type` |
-| `investigation` | `jira`, `hypothesis` |
-| `decision` | `decision`, `decided-by` |
-| `person` | `team`, `role` |
-
-## Directory Placement
-
-ALWAYS place files in the directory matching their type. Refer to the Document Conventions section in `AGENT.md` for the authoritative type-to-directory mapping for this vault.
-
-| type | Directory |
-|------|-----------|
-| `feature` | `Projects/` |
-| `sprint-handoff` | `Sprints/` |
-| `daily` | `Daily/` |
-| `reference` | `Knowledge/` |
-| `person` | `People/` |
-| `meeting` | Within relevant project or sprint folder |
-| `investigation` | Within relevant project folder |
-| `decision` | Within relevant project folder |
+| Field | Purpose |
+|-------|---------|
+| `domain` | Knowledge area (e.g. ai-agents, product-strategy) |
+| `references` | Related notes as wikilinks: `[[Note Name]]` |
+| `status` | `draft`, `active`, `completed`, `archived` |
+| `source` | URL to cloud origin (Confluence, Google Docs, etc.) |
 
 ## Wikilink Rules
 
@@ -84,20 +52,25 @@ ALWAYS use wikilinks for:
 
 - People → `[[Person Name]]`
 - Projects → `[[Project Name]]`
-- Domain terms → check `[[Glossary]]` first, link if present
-- Teams → link to the team index note in `People/`
+- Domain concepts → `[[Concept Name]]`
+- Related notes → `[[Note Name]]`
+
+Rules:
+- Use `[[wikilinks]]` for internal vault connections
+- Use `[text](url)` for external URLs only
+- Use `[[Note Name#Heading]]` for specific section links
+- Use `[[Note Name\|Display Text]]` for custom display text
 
 ## File Naming
 
 - Use Title Case or kebab-case for file names
-- JIRA tickets: use the project key prefix (e.g., `PROJ-1234-Description.md`)
 - No special characters, no leading/trailing spaces
+- Daily notes: `YYYY-MM-DD` format
 
 ## Post-Creation Verification
 
 After creating or modifying a note, verify:
 
 1. All required frontmatter fields are present and correct
-2. File is in the correct directory for its type
-3. People and project mentions use `[[wikilinks]]`
-4. Domain terms reference `[[Glossary]]`
+2. People and project mentions use `[[wikilinks]]`
+3. Domain concepts are linked consistently

package/src/assets/obsidian-skills/vault-thinking.md

@@ -11,7 +11,7 @@ This vault has BYOAO thinking commands available. Suggest them when they match t
 
 | Command | What it does | Suggest when |
 |---------|-------------|--------------|
-| `/weave` | Enrich notes with frontmatter, wikilinks, Glossary entries, hub notes | User imports new files, asks to organize, or vault has many unlinked notes |
+| `/weave` | Enrich notes with frontmatter, wikilinks, suggest permanent concept notes | User imports new files, asks to organize, or vault has many unlinked notes |
 | `/trace topic` | Chronological timeline of how an idea evolved | User asks how something developed, wants history, or says "when did I start..." |
 | `/emerge` | Surface hidden patterns, clusters, contradictions across the vault | User asks "what am I missing", wants a big-picture review, or seems stuck |
 | `/connect A B` | Bridge two topics via the vault's link graph | User wonders if two areas are related, or wants cross-domain insight |

package/src/assets/presets/common/AGENTS.md.hbs

@@ -0,0 +1,25 @@
+# AI Agent Guide
+
+## 关于本知识库
+这是一个基于 Zettelkasten 理念构建的个人知识库。知识通过原子化的笔记和双向链接形成网络。你可以保留自己的目录组织习惯，笔记之间的关联由 Agent 通过 `/weave` 自动维护。
+
+## 从哪里开始
+知识图谱：运行 `/wiki` 生成 `INDEX.base` 后，从这里探索知识库的结构。
+
+## 笔记类型
+每条笔记通过 frontmatter 的 `note_type` 分为三类：
+- **fleeting** — 原始摄入，待处理
+- **literature** — 对某来源的整理笔记
+- **permanent** — 原子概念笔记
+
+## 操作规则
+**使用 Obsidian CLI 进行所有笔记操作**（`obsidian read`、`obsidian search`、`obsidian create` 等）。
+不要用 bash（`cat`、`grep`、`find`、`sed` 等）直接处理笔记文件——Obsidian CLI 能正确维护 wikilink、frontmatter 和文件关系。
+
+## 可用能力
+- **/weave** — 编织新笔记：提取概念、建立 wikilink、生成 frontmatter
+- **/wiki** — 生成 INDEX.base 知识图谱索引
+- **/organize** — 按需重组目录结构
+- **/ask** — 对知识库进行开放式问答
+- **Thinking Tools** — /trace、/emerge、/connect、/ideas、/challenge、/drift
+- **/diagnose** — 检查知识库健康状态，查看哪些笔记需要编织

package/src/assets/presets/common/Start Here.md.hbs

@@ -127,11 +127,11 @@ tell the agent: "reconnect to {service name}".
 ## Key Files
 
 - **[[Glossary]]** — Domain terms and key concepts
-- **AGENT.md** — How AI agents navigate this vault
+- **AGENTS.md** — How AI agents navigate this vault
 
 ---
 
 ## For AI Agents
 
-See `AGENT.md` at the vault root for navigation instructions
+See `AGENTS.md` at the vault root for navigation instructions
 and knowledge graph conventions.

package/src/skills/ask.md

@@ -0,0 +1,132 @@
+---
+name: ask
+description: Open-ended Q&A against the knowledge base. Agent reads INDEX.base to locate relevant notes, synthesizes answers with citations. Use when the user asks questions about vault content like "what is X", "why did we decide", "explain Y", or wants to query their accumulated knowledge.
+---
+
+# /ask — Knowledge Q&A
+
+You are a knowledge assistant. Your job is to answer questions by navigating the vault's knowledge graph, reading relevant notes, and synthesizing evidence-based answers — always citing sources with wikilinks.
+
+## Prerequisites Check
+
+**Before doing anything else**, verify Obsidian CLI is available:
+
+```bash
+obsidian --version
+```
+
+If this fails, STOP and display the Obsidian CLI availability message (see /weave for the full error text).
+
+## Parameters
+
+- **question** (required): The question to answer.
+- **output** (optional): Save the answer as a note at this path.
+
+## Process
+
+### Step 1: Understand the Question
+
+Identify the key concepts, entities, and intent in the user's question.
+
+### Step 2: Locate Relevant Notes
+
+If `INDEX.base` exists, read it first to understand the vault structure:
+
+```bash
+obsidian read "INDEX"
+```
+
+Then search for relevant notes:
+
+```bash
+obsidian search "<key concept>"
+```
+
+Search for each key concept mentioned in the question. Combine results across concepts.
+
+### Step 3: Read Relevant Notes
+
+For each promising result, read the full content:
+
+```bash
+obsidian read "<note name>"
+```
+
+Prioritize:
+- Notes with `note_type: permanent` (atomic concepts)
+- Highly linked notes (many backlinks)
+- Recent notes (last 30 days)
+
+### Step 4: Synthesize Answer
+
+Combine evidence from all relevant notes into a clear, structured answer:
+
+- **Direct answer first** — address the question directly
+- **Supporting evidence** — cite specific notes with wikilinks and brief quotes
+- **Context** — explain how the evidence connects
+- **Uncertainties** — flag gaps where the vault doesn't have enough information
+
+Every claim must be backed by at least one vault note. Do not use general knowledge to answer — ground everything in the vault.
+
+### Step 5: Present Answer
+
+```markdown
+## Answer
+
+<Direct answer to the question>
+
+## Evidence
+
+- **[[Note A]]**: "<relevant quote>"
+- **[[Note B]]**: "<relevant quote>"
+- **[[Note C]]**: "<relevant quote>"
+
+## Context
+
+<Brief paragraph connecting the evidence and explaining the bigger picture>
+
+## Gaps
+
+<What the vault doesn't cover that would help answer more completely>
+
+## Related Questions
+
+- Consider exploring: "..."
+- Run `/trace topic="X"` to see how this evolved
+- Run `/connect from="A" to="B"` to understand the relationship
+```
+
+### Step 6: Save (Optional)
+
+At the end of your answer, ask:
+
+> "Would you like me to save this as a note?"
+
+If the user confirms, save the answer with frontmatter:
+
+```yaml
+---
+title: "Answer: <topic>"
+note_type: literature
+type: reference
+domain: <inferred>
+date: <today>
+tags: [qa, <topic>]
+---
+```
+
+Use `obsidian create` to save:
+
+```bash
+obsidian create name="Answer: <topic>" content="<frontmatter + content>" silent
+```
+
+Ask the user where they'd like it saved (root or a specific directory).
+
+## Key Principles
+
+- **Evidence-based**: Every answer must cite vault notes. No general knowledge answers.
+- **Direct first**: Answer the question before providing supporting detail.
+- **Acknowledge gaps**: If the vault doesn't have enough information, say so.
+- **Respect scope**: Only answer based on vault content, not external knowledge.
+- **Save on request**: Always offer to save the answer as a note for future reference.

package/src/skills/challenge.md

@@ -147,18 +147,24 @@ Based on the evidence gathered, rate the belief:
 
 ### Step 6: Save (Optional)
 
-If the user requested output, save with frontmatter:
+At the end of your challenge, ask:
+
+> "Would you like me to save this as a note?"
+
+If the user confirms, save with frontmatter:
 
 ```yaml
 ---
 title: "Challenge: {Belief}"
+note_type: literature
 type: analysis
 date: <today>
 tags: [challenge, critical-thinking]
-status: active
 ---
 ```
 
+Use `obsidian create` to save. Ask the user where they'd like it saved.
+
 ## Key Principles
 
 - **Fair, not adversarial**: Always present supporting evidence first. The goal is clear thinking, not winning an argument.

package/src/skills/connect.md

@@ -183,11 +183,16 @@ If you believe these topics are related, consider:
 
 ### Step 7: Save (Optional)
 
-If the user requested output, save with frontmatter:
+At the end of your analysis, ask:
+
+> "Would you like me to save this as a note?"
+
+If the user confirms, save with frontmatter:
 
 ```yaml
 ---
 title: "Connect: {From} ↔ {To}"
+note_type: literature
 type: analysis
 date: <today>
 references:
@@ -197,6 +202,8 @@ tags: [connect, bridge]
 ---
 ```
 
+Use `obsidian create` to save. Ask the user where they'd like it saved.
+
 ## Key Principles
 
 - **Evidence-based**: Every claimed connection must cite specific notes and quotes.

package/src/skills/diagnose.md

@@ -1,6 +1,6 @@
 ---
 name: diagnose
-description: Diagnose knowledge graph health — find missing frontmatter, orphan notes, broken wikilinks, and AGENT.md drift. Use when the user says "check my vault", "find broken links", "vault health", "what's wrong with my notes", or wants a health check on their knowledge base.
+description: Diagnose knowledge graph health — find missing frontmatter, orphan notes, broken wikilinks, and AGENTS.md drift. Use when the user says "check my vault", "find broken links", "vault health", "what's wrong with my notes", or wants a health check on their knowledge base.
 ---
 
 # /diagnose — Knowledge Graph Health Check
@@ -11,18 +11,21 @@ You are a vault health assistant. Your job is to diagnose issues in an Obsidian
 
 ### Step 1: Locate Vault
 
-Ask the user for their vault path, or detect it from the current working directory (look for AGENT.md in the cwd or parent directories).
+Ask the user for their vault path, or detect it from the current working directory (look for AGENTS.md in the cwd or parent directories).
 
 ### Step 2: Run Diagnosis
 
 Call `byoao_vault_doctor` with the vault path. This runs 5 checks:
 
 1. **Missing frontmatter** — notes without any YAML frontmatter
-2. **Missing type/tags** — notes with frontmatter but no `type` or `tags` field
-3. **AGENT.md drift** — AGENT.md references people or projects that don't have notes
+2. **Missing note_type** — notes without `note_type` field (not yet woven)
+3. **Missing type/tags** — notes with frontmatter but no `type` or `tags` field
 4. **Orphan notes** — notes with no incoming or outgoing wikilinks
 5. **Broken wikilinks** — links that point to non-existent notes
 
+Additionally, if `INDEX.base` exists:
+6. **INDEX.base accuracy** — verify note counts match actual vault state
+
 ### Step 3: Present Results
 
 Format the report by severity:
@@ -33,7 +36,7 @@ Format the report by severity:
   - Projects/demo-notes.md
   - Knowledge/api-overview.md
 
-! AGENT.md lists [[Kent]] but no People/Kent.md found
+! AGENTS.md lists [[Kent]] but no People/Kent.md found
 
 i 2 orphan notes (no incoming or outgoing wikilinks)
   - Archive/old-draft.md
@@ -49,21 +52,17 @@ For each issue category, suggest a concrete next action:
 | Issue | Suggested Fix |
 |-------|--------------|
 | Missing frontmatter | "Run `/weave` on these files to add structure" |
+| Missing note_type | "Run `/weave` to classify and connect these notes" |
 | Missing type/tags | "Run `/weave` to fill in metadata" |
-| AGENT.md drift | "Create the missing note? I can run `byoao_add_person` or `byoao_add_project`" |
 | Orphan notes | "Consider adding `[[wikilinks]]` to connect them, or archive if unused" |
 | Broken wikilinks | "Create the target note, or fix the link name" |
+| INDEX.base stale | "Run `/wiki` to regenerate the knowledge index" |
 
 **Always ask for user confirmation before making changes.** Do not auto-fix.
 
-### Step 5: Update AGENT.md Timestamp
-
-After fixes are applied, **ask the user** before updating AGENT.md. If confirmed, append or update a `Last Scanned` line at the bottom of AGENT.md:
+### Step 5: Update INDEX.base Timestamp
 
-```markdown
----
-_Last scanned by /diagnose: 2026-03-27_
-```
+If `INDEX.base` exists and significant changes were made during fixes, suggest running `/wiki` to regenerate the index. If the user confirms, run `/wiki`.
 
 ## Key Principles
 

package/src/skills/drift.md

@@ -196,18 +196,24 @@ These questions are for your consideration — not judgments:
 
 ### Step 6: Save (Optional)
 
-If the user requested output, save with frontmatter:
+At the end of your analysis, ask:
+
+> "Would you like me to save this as a note?"
+
+If the user confirms, save with frontmatter:
 
 ```yaml
 ---
 title: "Drift Analysis: {period}"
+note_type: literature
 type: analysis
 date: <today>
 tags: [drift, reflection]
-status: active
 ---
 ```
 
+Use `obsidian create` to save. Ask the user where they'd like it saved.
+
 ## Key Principles
 
 - **Descriptive, not judgmental**: "You said X and did Y" is fine. "You failed to do X" is not. Drift is information, not failure.

package/src/skills/emerge.md

@@ -141,17 +141,24 @@ Analyzed {N} notes across {M} domains.
 
 ### Step 7: Save (Optional)
 
-If the user requested output, save with frontmatter:
+At the end of your findings, ask:
+
+> "Would you like me to save this as a note?"
+
+If the user confirms, save with frontmatter:
 
 ```yaml
 ---
 title: "Emerge: Vault Patterns"
+note_type: literature
 type: analysis
 date: <today>
 tags: [emerge, patterns]
 ---
 ```
 
+Use `obsidian create` to save. Ask the user where they'd like it saved.
+
 ## Key Principles
 
 - **Show, don't tell**: Always cite specific notes and quotes. Never claim a pattern exists without evidence.

package/src/skills/ideas.md

@@ -47,7 +47,7 @@ Read notes across domains, prioritizing:
 - Recent notes (last 30 days) — what the user is actively thinking about
 - Highly connected notes (many backlinks) — central concepts
 - Notes with `status: active` — current work
-- Glossary — the user's core vocabulary
+- `INDEX.base` if it exists — for knowledge structure overview
 
 For each domain, read 5-10 representative notes to understand the landscape.
 
@@ -145,18 +145,24 @@ Rank the three highest-impact, most immediately actionable ideas:
 
 ### Step 7: Save (Optional)
 
-If the user requested output, save with frontmatter:
+At the end of your ideas, ask:
+
+> "Would you like me to save this as a note?"
+
+If the user confirms, save with frontmatter:
 
 ```yaml
 ---
 title: "Ideas: {focus}"
+note_type: literature
 type: analysis
 date: <today>
 tags: [ideas, proactive]
-status: active
 ---
 ```
 
+Use `obsidian create` to save. Ask the user where they'd like it saved.
+
 ## Key Principles
 
 - **Actionable over interesting**: Every idea must have a concrete next step. "Interesting observation" is not an idea.

package/src/skills/organize.md

@@ -52,10 +52,9 @@ Never move or suggest moving:
 
 | Pattern | Reason |
 |---------|--------|
-| `AGENT.md` | BYOAO-managed root file |
+| `AGENTS.md` | BYOAO-managed root file |
+| `INDEX.base` | Knowledge graph index — do not move |
 | `Start Here.md` | BYOAO onboarding file |
-| `Knowledge/Glossary.md` | BYOAO Glossary |
-| `Knowledge/templates/*` | Template files |
 | `.obsidian/`, `.git/`, `.byoao/` | System directories |
 | `.opencode/`, `.cursor/`, `.claude/` | Tool config directories |
 | `.env`, `credentials.*`, `*.key` | Sensitive files |
@@ -92,7 +91,7 @@ For each file with a `type` property, determine if it should move based on this
 | `feature` | `Projects/<project>/` | Use `project` frontmatter field |
 | `project` | `Projects/` | Top-level project notes |
 | `sprint-handoff` | `Sprints/` | |
-| `reference` | `Knowledge/` | General reference material |
+| `reference` | `Knowledge/` or user's preferred reference location | General reference material |
 | `person` | `People/` | |
 | `investigation` | Project folder if `project` field exists, else `Knowledge/` | |
 | `idea` | `Knowledge/` | |

package/src/skills/trace.md

@@ -40,7 +40,7 @@ obsidian search "<topic>"
 ```
 
 Also check:
-- Glossary entry for the topic
+- `INDEX.base` if it exists, for domain and note_type classification
 - Backlinks to `[[<topic>]]` if a note exists for it
 - Tag variations: `#<topic>`, `#<topic-kebab-case>`
 
@@ -125,12 +125,17 @@ Consider tracing these connected topics:
 
 ### Step 6: Save (Optional)
 
-If the user requested output, save the trace as a note with frontmatter:
+At the end of your trace, ask:
+
+> "Would you like me to save this as a note?"
+
+If the user confirms, save the trace with frontmatter:
 
 ```yaml
 ---
 title: "Trace: {Topic}"
-type: trace
+note_type: literature
+type: reference
 domain: <inferred from topic>
 date: <today>
 references:
@@ -140,6 +145,8 @@ tags: [trace, <topic-tag>]
 ---
 ```
 
+Use `obsidian create` to save. Ask the user where they'd like it saved.
+
 ## Key Principles
 
 - **Chronological accuracy**: Always verify dates. Don't guess — if a note has no date, say "undated."