@jayjiang/byoao 1.1.0 → 1.1.2

package/dist/assets/obsidian-skills/obsidian-markdown.md

@@ -0,0 +1,196 @@
+---
+name: obsidian-markdown
+description: Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.
+---
+
+# Obsidian Flavored Markdown Skill
+
+Create and edit valid Obsidian Flavored Markdown. Obsidian extends CommonMark and GFM with wikilinks, embeds, callouts, properties, comments, and other syntax. This skill covers only Obsidian-specific extensions -- standard Markdown (headings, bold, italic, lists, quotes, code blocks, tables) is assumed knowledge.
+
+## Workflow: Creating an Obsidian Note
+
+1. **Add frontmatter** with properties (title, tags, aliases) at the top of the file. See [PROPERTIES.md](references/PROPERTIES.md) for all property types.
+2. **Write content** using standard Markdown for structure, plus Obsidian-specific syntax below.
+3. **Link related notes** using wikilinks (`[[Note]]`) for internal vault connections, or standard Markdown links for external URLs.
+4. **Embed content** from other notes, images, or PDFs using the `![[embed]]` syntax. See [EMBEDS.md](references/EMBEDS.md) for all embed types.
+5. **Add callouts** for highlighted information using `> [!type]` syntax. See [CALLOUTS.md](references/CALLOUTS.md) for all callout types.
+6. **Verify** the note renders correctly in Obsidian's reading view.
+
+> When choosing between wikilinks and Markdown links: use `[[wikilinks]]` for notes within the vault (Obsidian tracks renames automatically) and `[text](url)` for external URLs only.
+
+## Internal Links (Wikilinks)
+
+```markdown
+[[Note Name]]                          Link to note
+[[Note Name|Display Text]]             Custom display text
+[[Note Name#Heading]]                  Link to heading
+[[Note Name#^block-id]]                Link to block
+[[#Heading in same note]]              Same-note heading link
+```
+
+Define a block ID by appending `^block-id` to any paragraph:
+
+```markdown
+This paragraph can be linked to. ^my-block-id
+```
+
+For lists and quotes, place the block ID on a separate line after the block:
+
+```markdown
+> A quote block
+
+^quote-id
+```
+
+## Embeds
+
+Prefix any wikilink with `!` to embed its content inline:
+
+```markdown
+![[Note Name]]                         Embed full note
+![[Note Name#Heading]]                 Embed section
+![[image.png]]                         Embed image
+![[image.png|300]]                     Embed image with width
+![[document.pdf#page=3]]               Embed PDF page
+```
+
+See [EMBEDS.md](references/EMBEDS.md) for audio, video, search embeds, and external images.
+
+## Callouts
+
+```markdown
+> [!note]
+> Basic callout.
+
+> [!warning] Custom Title
+> Callout with a custom title.
+
+> [!faq]- Collapsed by default
+> Foldable callout (- collapsed, + expanded).
+```
+
+Common types: `note`, `tip`, `warning`, `info`, `example`, `quote`, `bug`, `danger`, `success`, `failure`, `question`, `abstract`, `todo`.
+
+See [CALLOUTS.md](references/CALLOUTS.md) for the full list with aliases, nesting, and custom CSS callouts.
+
+## Properties (Frontmatter)
+
+```yaml
+---
+title: My Note
+date: 2024-01-15
+tags:
+  - project
+  - active
+aliases:
+  - Alternative Name
+cssclasses:
+  - custom-class
+---
+```
+
+Default properties: `tags` (searchable labels), `aliases` (alternative note names for link suggestions), `cssclasses` (CSS classes for styling).
+
+See [PROPERTIES.md](references/PROPERTIES.md) for all property types, tag syntax rules, and advanced usage.
+
+## Tags
+
+```markdown
+#tag                    Inline tag
+#nested/tag             Nested tag with hierarchy
+```
+
+Tags can contain letters, numbers (not first character), underscores, hyphens, and forward slashes. Tags can also be defined in frontmatter under the `tags` property.
+
+## Comments
+
+```markdown
+This is visible %%but this is hidden%% text.
+
+%%
+This entire block is hidden in reading view.
+%%
+```
+
+## Obsidian-Specific Formatting
+
+```markdown
+==Highlighted text==                   Highlight syntax
+```
+
+## Math (LaTeX)
+
+```markdown
+Inline: $e^{i\pi} + 1 = 0$
+
+Block:
+$$
+\frac{a}{b} = c
+$$
+```
+
+## Diagrams (Mermaid)
+
+````markdown
+```mermaid
+graph TD
+    A[Start] --> B{Decision}
+    B -->|Yes| C[Do this]
+    B -->|No| D[Do that]
+```
+````
+
+To link Mermaid nodes to Obsidian notes, add `class NodeName internal-link;`.
+
+## Footnotes
+
+```markdown
+Text with a footnote[^1].
+
+[^1]: Footnote content.
+
+Inline footnote.^[This is inline.]
+```
+
+## Complete Example
+
+````markdown
+---
+title: Project Alpha
+date: 2024-01-15
+tags:
+  - project
+  - active
+status: in-progress
+---
+
+# Project Alpha
+
+This project aims to [[improve workflow]] using modern techniques.
+
+> [!important] Key Deadline
+> The first milestone is due on ==January 30th==.
+
+## Tasks
+
+- [x] Initial planning
+- [ ] Development phase
+  - [ ] Backend implementation
+  - [ ] Frontend design
+
+## Notes
+
+The algorithm uses $O(n \log n)$ sorting. See [[Algorithm Notes#Sorting]] for details.
+
+![[Architecture Diagram.png|600]]
+
+Reviewed in [[Meeting Notes 2024-01-10#Decisions]].
+````
+
+## References
+
+- [Obsidian Flavored Markdown](https://help.obsidian.md/obsidian-flavored-markdown)
+- [Internal links](https://help.obsidian.md/links)
+- [Embed files](https://help.obsidian.md/embeds)
+- [Callouts](https://help.obsidian.md/callouts)
+- [Properties](https://help.obsidian.md/properties)

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

@@ -0,0 +1,40 @@
+---
+name: vault-thinking
+description: Guide for recommending BYOAO vault analysis commands to users. Use when the user is reflecting, brainstorming, stuck on an idea, asking about patterns, or could benefit from a vault-powered thinking workflow.
+---
+
+# Vault Thinking Guide
+
+This vault has BYOAO thinking commands available. Suggest them when they match the user's intent — don't wait for an exact keyword match.
+
+## Available Commands
+
+| 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 |
+| `/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 |
+| `/ideas` | Deep scan to generate actionable ideas from vault content | User asks "what should I work on", wants brainstorming, or needs next steps |
+| `/challenge topic` | Pressure-test a belief against the vault's own history | User is making a decision, says "am I wrong", or wants to validate an assumption |
+| `/drift` | Compare stated intentions vs actual behavior over 30-90 days | User asks about follow-through, wonders where time went, or reviews goals |
+| `/diagnose` | Vault health check — orphans, broken links, frontmatter gaps | User notices broken links, asks "what's wrong with my vault", or after heavy editing |
+## When to Proactively Suggest
+
+- User is **reflecting on a topic** → suggest `/trace` to see how their thinking evolved
+- User is **brainstorming or feels stuck** → suggest `/emerge` or `/ideas`
+- User is **making a decision** → suggest `/challenge` to pressure-test it
+- User is **reviewing goals or progress** → suggest `/drift`
+- User **imported new notes** or mentions disorganization → suggest `/weave`
+- User asks about **connections between topics** → suggest `/connect`
+- User mentions **broken links or vault messiness** → suggest `/diagnose`
+
+## How to Suggest
+
+Mention the command naturally in conversation. For example:
+
+- "You could run `/trace data-mesh` to see how that idea has evolved across your notes."
+- "If you want to pressure-test that assumption, `/challenge` can find counter-evidence in your vault."
+- "After importing those files, `/weave` can add frontmatter and link them to your existing notes."
+
+Do not run these commands automatically — they read many vault files and can take several minutes. Always let the user decide when to invoke them.

package/{src/assets/presets/common/AGENT.md.hbs → dist/assets/presets/common/AGENTS.md.hbs}

@@ -1,16 +1,14 @@
 # {{KB_NAME}}
 
-{{#if OWNER_NAME}}This is {{OWNER_NAME}}'s personal knowledge base.{{else}}A personal knowledge base.{{/if}} It contains interconnected notes on work, ideas, projects, people, and domains of interest.
+{{#if OWNER_NAME}}This is {{OWNER_NAME}}'s personal knowledge base.{{else}}A personal knowledge base.{{/if}}
+
+Knowledge graph (frontmatter + wikilinks) is the source of truth, not folder structure.
 
 ## How to Navigate
 
-1. **Start with [[Glossary]]** — the entity dictionary for this knowledge base.
-   Every term is a key concept the owner cares about. Scan it first to
-   understand domain vocabulary.
-2. **Use frontmatter** to find relevant notes: `domain`, `type`, `tags`,
-   and `references` fields narrow down context quickly.
-3. **Follow wikilinks** — `[[links]]` connect related notes. Follow them
-   to build understanding of a topic.
+1. **Start with [[Glossary]]** — the entity dictionary. Every term is a key concept the owner cares about.
+2. **Search by frontmatter** — `domain`, `type`, `tags`, and `references` fields narrow context quickly.
+3. **Follow wikilinks** — `[[links]]` connect related notes. Follow them to build understanding.
 4. **Check backlinks** — discover related notes the user didn't mention.
 5. **Chain**: Glossary → domain notes → references → backlinks → details.
 
@@ -25,26 +23,24 @@
 | `references`| Related notes — follow for deeper context        |
 | `tags`      | Flexible categorization                          |
 | `status`    | draft / active / completed / archived            |
-| `source`    | (optional) URL to cloud origin — Confluence, Google Doc, etc. |
+| `source`    | (optional) URL to cloud origin — Confluence, Doc, etc. |
 
 {{{ROLE_SECTION}}}
 
 <!-- byoao:domains:start -->
 ## Key Domains
 
-(Auto-generated by /weave — run it to discover domains across vault notes)
+(Auto-generated by `/weave` — run it to discover domains across vault notes)
 
 <!-- byoao:domains:end -->
 
 <!-- byoao:conventions:start -->
 ## Conventions
 
-- Notes may or may not have frontmatter. Use /weave to enrich.
+- Notes may or may not have frontmatter. Use `/weave` to enrich.
 - Wikilinks are the primary connection mechanism.
-- No strict directory rules — notes live wherever the user puts them.
-- The knowledge graph (frontmatter + wikilinks) is the source of truth,
-  not the folder structure.
+- No strict directory rules — notes live wherever the user places them.
 - Use `/weave` to connect new notes into the graph.
 - Use `/diagnose` to check knowledge graph health.
 
-<!-- byoao:conventions:end -->
+<!-- byoao:conventions:end -->

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

@@ -0,0 +1,137 @@
+---
+title: Start Here
+type: reference
+status: active
+tags: [onboarding]
+---
+
+# Welcome to {{KB_NAME}}
+
+Your personal knowledge base. Curate what matters, and let AI
+connect the dots into a knowledge graph.
+
+## Choose Your Path
+
+### Path A: My docs are in the cloud
+
+If your knowledge lives in Confluence, Google Docs, Notion, or other
+cloud services — you are the curator. BYOAO does not auto-import;
+you decide what belongs in your local knowledge base.
+
+**How to bring content in:**
+
+1. **Export as Markdown** — Confluence and Google Docs both support
+   exporting pages as `.md` files. Download the ones that matter
+   and drop them into this vault folder.
+2. **Obsidian Web Clipper** — Install the browser extension to save
+   any web page directly into your vault as a clean markdown note.
+3. **Write summaries** — You don't need full copies. Create a local
+   note that captures the key insights and link back to the source:
+
+```yaml
+---
+title: "Migration Plan Q2"
+source: "https://confluence.example.com/pages/12345"
+---
+```
+
+> The `source` property keeps the connection between your local note
+> and the cloud original. Add it whenever a note originates from an
+> external document.
+
+**Once you have a few notes → run `/weave`** (see below).
+
+### Path B: I already have local notes
+
+If you have existing markdown files — whether organized or scattered:
+
+1. **Drop them in** — Copy or move your files into this vault folder.
+   (Or if you ran `byoao init --from`, they're already here.)
+2. **Don't worry about structure** — Your files don't need frontmatter,
+   wikilinks, or any particular organization yet.
+
+**Run `/weave` now** — it will scan your notes, add frontmatter
+metadata (including dates from file timestamps), discover connections,
+and build your [[Glossary]] from frequently mentioned concepts.
+
+### Path C: Starting fresh
+
+No existing notes? No problem.
+
+1. Press `Cmd+T` (Mac) or `Ctrl+T` (Windows) → choose "Daily Note".
+2. Write what's on your mind today. Don't worry about structure.
+3. After a few notes, run `/weave` to connect them.
+
+---
+
+## /weave — Where the Magic Happens
+
+Open your AI agent and type `/weave`. It will:
+
+- **Add frontmatter** — title, date, type, domain, tags
+- **Create wikilinks** — connect related notes automatically
+- **Build your Glossary** — extract key terms and concepts
+- **Suggest organization** — propose directory structure (with your approval)
+
+Watch: scattered files become a connected knowledge graph.
+
+After weaving, press `Cmd+G` (Mac) or `Ctrl+G` (Windows) to see your
+knowledge visualized. Every node is a note, every line is a connection.
+
+---
+
+## Obsidian Essentials
+
+| Shortcut | Action |
+|----------|--------|
+| `Cmd+O` | Quick Switch — jump to any note |
+| `Cmd+T` | Insert Template |
+| `Cmd+G` | Graph View |
+| `Cmd+N` | New note |
+| `Cmd+Shift+F` | Search across all notes |
+| `[[double brackets]]` | Create a link to another note |
+
+---
+
+## AI Commands
+
+| Command | What it does |
+|---------|-------------|
+| `/weave` | Connect your notes into a knowledge graph |
+| `/organize` | Reorganize vault directories using enriched metadata |
+| `/trace` | Track how an idea evolved over time |
+| `/emerge` | Discover patterns you haven't noticed |
+| `/connect` | Bridge two seemingly unrelated topics |
+| `/ideas` | Generate actionable ideas from your vault |
+| `/challenge` | Pressure-test a belief against your own notes |
+| `/drift` | Compare intentions vs actions over time |
+| `/diagnose` | Check knowledge graph health |
+
+{{#if HAS_MCP_SERVICES}}
+
+---
+
+## Connected Services
+
+Your AI agent can access external services configured during setup:
+{{#each MCP_SERVICES}}
+- **{{this.name}}** — {{this.description}}
+{{/each}}
+
+These services authenticate via your browser. If a connection expires,
+tell the agent: "reconnect to {service name}".
+
+{{/if}}
+---
+
+## Key Files
+
+- **[[Glossary]]** — Domain terms and key concepts
+- **AGENTS.md** — How AI agents navigate this vault
+
+---
+
+## For AI Agents
+
+See `AGENTS.md` at the vault root for navigation instructions
+and knowledge graph conventions.

package/dist/assets/presets/common/obsidian/core-plugins.json

@@ -0,0 +1,33 @@
+{
+  "file-explorer": true,
+  "global-search": true,
+  "switcher": true,
+  "graph": true,
+  "backlink": true,
+  "canvas": true,
+  "outgoing-link": true,
+  "tag-pane": true,
+  "footnotes": false,
+  "properties": true,
+  "page-preview": true,
+  "daily-notes": true,
+  "templates": true,
+  "note-composer": true,
+  "command-palette": true,
+  "slash-command": false,
+  "editor-status": true,
+  "bookmarks": true,
+  "markdown-importer": false,
+  "zk-prefixer": false,
+  "random-note": false,
+  "outline": true,
+  "word-count": true,
+  "slides": false,
+  "audio-recorder": false,
+  "workspaces": false,
+  "file-recovery": true,
+  "publish": false,
+  "sync": true,
+  "bases": true,
+  "webviewer": false
+}

package/dist/assets/presets/common/obsidian/daily-notes.json

@@ -0,0 +1,5 @@
+{
+  "folder": "Daily",
+  "format": "YYYY-MM-DD",
+  "template": "Knowledge/templates/Daily Note"
+}

package/dist/assets/presets/common/obsidian/templates.json

@@ -0,0 +1,3 @@
+{
+  "folder": "Knowledge/templates"
+}

package/dist/assets/presets/common/templates/Daily Note.md

@@ -0,0 +1,19 @@
+---
+title: "{{date}}"
+type: daily
+status: active
+date: {{date}}
+tags: [daily]
+---
+
+## Focus
+
+-
+
+## Notes
+
+-
+
+## Action Items
+
+- [ ]

package/dist/assets/presets/common/templates/Decision Record.md

@@ -0,0 +1,32 @@
+---
+title: ""
+type: decision
+status: draft
+date: {{date}}
+decision: ""
+decided-by: []
+alternatives-considered: []
+tags: [decision]
+---
+
+## Context
+
+What is the situation that requires a decision?
+
+## Decision
+
+What was decided.
+
+## Alternatives Considered
+
+| Option | Pros | Cons |
+|--------|------|------|
+|        |      |      |
+
+## Rationale
+
+Why this option was chosen over alternatives.
+
+## Consequences
+
+What changes as a result of this decision.

package/dist/assets/presets/common/templates/Investigation.md

@@ -0,0 +1,34 @@
+---
+title: ""
+type: investigation
+status: draft
+date: {{date}}
+jira: ""
+hypothesis: ""
+conclusion: ""
+tags: [investigation, spike]
+---
+
+## Question
+
+What are we trying to find out?
+
+## Hypothesis
+
+What we expect to find and why.
+
+## Method
+
+How we investigated (queries, tools, data sources).
+
+## Findings
+
+-
+
+## Conclusion
+
+Summary of what we learned. Does it confirm or refute the hypothesis?
+
+## Next Steps
+
+-

package/dist/assets/presets/common/templates/Meeting Notes.md

@@ -0,0 +1,25 @@
+---
+title: ""
+type: meeting
+status: active
+date: {{date}}
+participants: []
+meeting-type: ""
+tags: [meeting]
+---
+
+## Agenda
+
+1.
+
+## Notes
+
+-
+
+## Decisions
+
+-
+
+## Action Items
+
+- [ ] @person — task — due date

package/dist/assets/presets/minimal/preset.json

@@ -0,0 +1,28 @@
+{
+  "name": "minimal",
+  "displayName": "Personal Knowledge Base",
+  "description": "A minimal personal knowledge base — just Daily notes, templates, and Glossary. Add structure as you go.",
+  "directories": [],
+  "agentDescription": "Personal knowledge base. Notes are connected through wikilinks and frontmatter. Use /weave to discover and strengthen connections.",
+  "frontmatterExtras": {},
+  "templates": [],
+  "mcpServers": {},
+  "obsidianPlugins": {
+    "agent-client": {
+      "repo": "RAIT-09/obsidian-agent-client",
+      "version": "latest",
+      "config": {
+        "defaultAgentId": "opencode-acp",
+        "customAgents": [
+          {
+            "id": "opencode-acp",
+            "displayName": "OpenCode",
+            "command": "opencode",
+            "args": ["acp"],
+            "env": []
+          }
+        ]
+      }
+    }
+  }
+}

package/dist/assets/presets/pm-tpm/agent-section.hbs

@@ -0,0 +1,15 @@
+## Active Projects (Projects/)
+
+{{{PROJECTS}}}
+
+{{#if HAS_JIRA}}
+## JIRA
+
+- Host: {{JIRA_HOST}}
+- Project: {{JIRA_PROJECT}}
+{{/if}}
+
+## Sprint Cycle
+
+- 2-week sprints
+- Adjust dates and cadence to match your team

package/dist/assets/presets/pm-tpm/preset.json

@@ -0,0 +1,43 @@
+{
+  "name": "pm-tpm",
+  "displayName": "PM / TPM",
+  "description": "Project tracking, sprint cycles, stakeholder management, data analysis",
+  "directories": ["Projects", "Sprints"],
+  "agentDescription": "PM/TPM knowledge base",
+  "frontmatterExtras": {
+    "project": ["jira", "stakeholders", "priority"],
+    "sprint": ["sprint-dates", "jira-board"]
+  },
+  "templates": ["Feature Doc.md", "Sprint Handoff.md"],
+  "mcpServers": {
+    "atlassian": {
+      "type": "remote",
+      "url": "https://mcp.atlassian.com/v1/sse"
+    },
+    "bigquery": {
+      "type": "local",
+      "command": ["npx", "-y", "@toolbox-sdk/server", "--prebuilt=bigquery", "--stdio"],
+      "environment": {
+        "BIGQUERY_PROJECT": "${GCP_PROJECT_ID}"
+      }
+    }
+  },
+  "obsidianPlugins": {
+    "agent-client": {
+      "repo": "RAIT-09/obsidian-agent-client",
+      "version": "latest",
+      "config": {
+        "defaultAgentId": "opencode-acp",
+        "customAgents": [
+          {
+            "id": "opencode-acp",
+            "displayName": "OpenCode",
+            "command": "opencode",
+            "args": ["acp"],
+            "env": []
+          }
+        ]
+      }
+    }
+  }
+}