@jayjiang/byoao 0.2.0

package/src/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/src/assets/presets/common/AGENT.md.hbs

@@ -0,0 +1,29 @@
+# {{TEAM_NAME}} Workspace
+
+{{{AGENT_DESCRIPTION}}}
+
+## Navigation
+
+- Search by frontmatter: `type`, `status`, `team`, `tags`
+- Follow `[[wikilinks]]` to traverse knowledge graph
+- `Knowledge/` for domain reference
+- `People/` for team roster
+
+## Domain Knowledge
+
+- [[Glossary]] — centralized term reference (start here for any domain question)
+
+### Concept Notes (Knowledge/concepts/)
+
+Complex domain concepts with rich wikilinks. Created as terms graduate from the Glossary.
+
+{{{ROLE_SECTION}}}
+
+## Team (People/)
+
+{{{TEAM_TABLE}}}
+
+## Templates (Knowledge/templates/)
+
+Use Obsidian's template plugin (Ctrl/Cmd+T) to insert:
+{{{TEMPLATE_LIST}}}

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

@@ -0,0 +1,44 @@
+---
+title: "{{TEAM_NAME}} Domain Glossary"
+type: reference
+status: active
+date: {{date}}
+tags: [glossary, domain, reference]
+---
+
+# {{TEAM_NAME}} Domain Glossary
+
+Centralized quick-reference for all domain terms. This glossary uses a **two-tier terminology system**:
+
+- **Tier 1 (this file)**: Simple terms defined in one or two sentences — kept here in table rows.
+- **Tier 2 (concept notes)**: Complex terms that need detailed explanation, diagrams, or have multiple relationships — get their own note in `30-Knowledge/concepts/` and are linked from here.
+
+---
+
+## Core Terms
+
+| Term | Definition |
+|------|-----------|
+{{GLOSSARY_ENTRIES}}
+
+---
+
+## How to Add a New Term
+
+1. **Start here**: Add a row to the appropriate table above with a one-line definition.
+2. **Graduate if needed**: If a term grows beyond 2 sentences, has 3+ relationships to other terms, or has important gotchas, create a concept note:
+   - Create `30-Knowledge/concepts/Term Name.md`
+   - Replace the definition here with: `Brief intro — see [[Term Name]] for full details.`
+3. **Link generously**: Use `[[wikilinks]]` in definitions to connect related terms.
+
+### Graduation Rule
+
+A term should move from Tier 1 to Tier 2 when:
+- Its definition needs **more than 2 sentences**
+- It has **3+ relationships** to other notes (people, projects, systems)
+- It has **gotchas or edge cases** that people frequently get wrong
+- It requires **examples, diagrams, or data** to explain properly
+
+---
+
+*Maintenance: This file is the first stop for any domain question. Keep it alphabetized within sections. Review quarterly for stale or missing terms.*

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

@@ -0,0 +1,95 @@
+---
+title: Start Here
+type: reference
+status: active
+tags: [onboarding]
+---
+
+# Welcome to {{TEAM_NAME}} Workspace
+
+This is a **knowledge base** for the {{TEAM_NAME}} team, built in [Obsidian](https://obsidian.md). Everything here — notes, terms, people, projects — is connected through links and searchable properties.
+
+This guide teaches by doing. Each section uses the features it describes.
+
+---
+
+## 5 Essential Operations
+
+### 1. Follow a Wikilink
+
+See the double-bracket link below? Click it to jump to that note.
+
+> Try it: [[Glossary]]
+
+Every `[[link]]` in this vault connects two notes. These connections build a knowledge graph you can visualize (see operation 5).
+
+### 2. Quick Switch
+
+Press `Cmd+O` (Mac) or `Ctrl+O` (Windows) to open the quick switcher. Start typing any note name.
+
+> Try it: `Cmd+O` → type any project name
+
+### 3. Insert a Template
+
+Press `Cmd+T` to insert a template into the current note. Templates live in `Knowledge/templates/` and give you consistent structure.
+
+> Try it: Create a new note (`Cmd+N`), then `Cmd+T` → choose "Meeting Notes"
+
+### 4. Search by Property
+
+Every note has **frontmatter** — the YAML block between `---` at the top. You can search by any property.
+
+> Try it: Open search (`Cmd+Shift+F`) → type `[type: feature]` to find all feature docs
+
+Common properties: `type`, `status`, `team`, `project`, `stakeholders`, `tags`.
+
+### 5. Graph View
+
+Press `Cmd+G` to see how all notes connect visually. Nodes are notes, edges are wikilinks.
+
+> Try it: `Cmd+G` → zoom into the cluster around [[{{TEAM_NAME}} Team]]
+
+---
+
+## Quick Win: See AI in Action
+
+Want to see what BYOAO can do? Try this in OpenCode:
+
+1. Create a new note in `Inbox/` — paste any messy text (meeting notes, brainstorm, etc.)
+2. Run `/enrich-document` in OpenCode
+3. Watch: frontmatter appears, wikilinks connect to existing notes, structure emerges
+
+This is the core loop — write freely, let AI structure it.
+
+---
+
+## Your First 10 Minutes
+
+1. Open [[Glossary]] — scan the term tables to orient yourself on domain language
+2. Pick any project in `Projects/` — follow links to people and concepts
+3. Open Graph View (`Cmd+G`) — see the full knowledge map
+4. Create a Daily Note (`Cmd+T` → Daily Note) — start capturing your own notes
+5. Read `AGENT.md` to see how AI agents navigate this vault
+
+---
+
+## Folder Map
+
+| Folder | Purpose |
+|--------|---------|
+| `Inbox` | Drop zone for unprocessed notes |
+| `Projects` | One note per active project |
+| `Sprints` | Sprint handoff documents |
+| `Knowledge` | Domain reference, glossary, concept notes, templates |
+| `People` | One note per team member + team index |
+| `Systems` | Codebase explanations (generated by AI agents) |
+| `Archive` | Completed or deprecated notes |
+| `Daily` | Daily notes (auto-created by template) |
+
+> **Note:** Folders are suggestions, not structure. Feel free to reorganize — the real knowledge graph lives in frontmatter and wikilinks.
+
+---
+
+## For AI Agents
+
+This vault is designed for both humans and AI agents. See `AGENT.md` (or `CLAUDE.md`) at the vault root for routing instructions, project index, and team roster.

package/src/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/src/assets/presets/common/obsidian/daily-notes.json

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

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

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

package/src/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/src/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/src/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/src/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/src/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/src/assets/presets/pm-tpm/preset.json

@@ -0,0 +1,12 @@
+{
+  "name": "pm-tpm",
+  "displayName": "PM / TPM",
+  "description": "Project tracking, sprint cycles, stakeholder management",
+  "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"]
+}

package/src/assets/presets/pm-tpm/templates/Feature Doc.md

@@ -0,0 +1,45 @@
+---
+title: ""
+type: feature
+status: draft
+date: {{date}}
+project: ""
+jira: ""
+stakeholders: []
+priority: ""
+tags: [feature]
+---
+
+## Overview
+
+Brief description of the feature and its business value.
+
+## Background
+
+Why this feature is needed. Link to relevant concept notes and people using `[[wikilinks]]`.
+
+## Requirements
+
+### Functional
+
+-
+
+### Non-Functional
+
+-
+
+## Design
+
+Link to design specs or prototypes.
+
+## Dependencies
+
+-
+
+## Success Metrics
+
+-
+
+## Open Questions
+
+-

package/src/assets/presets/pm-tpm/templates/Sprint Handoff.md

@@ -0,0 +1,38 @@
+---
+title: ""
+type: sprint-handoff
+status: draft
+date: {{date}}
+sprint: ""
+sprint-dates: ""
+jira-board: ""
+tags: [sprint, handoff]
+---
+
+## Sprint Goals
+
+1.
+
+## Completed Work
+
+| Ticket | Title | Status | Notes |
+|--------|-------|--------|-------|
+|        |       | Done   |       |
+
+## Carry-Over
+
+| Ticket | Title | Reason | Priority |
+|--------|-------|--------|----------|
+|        |       |        |          |
+
+## Risks & Blockers
+
+-
+
+## Key Decisions
+
+-
+
+## Next Sprint Plan
+
+-

package/src/assets/web-clipper/confluence-page.json

@@ -0,0 +1,63 @@
+{
+  "schemaVersion": "0.1.0",
+  "name": "BYOAO — Confluence Page",
+  "behavior": "create",
+  "noteContentFormat": "text",
+  "properties": [
+    {
+      "name": "title",
+      "value": "{{title|safe_name}}",
+      "type": "text"
+    },
+    {
+      "name": "type",
+      "value": "confluence-clip",
+      "type": "text"
+    },
+    {
+      "name": "source",
+      "value": "{{url}}",
+      "type": "text"
+    },
+    {
+      "name": "author",
+      "value": "{{selector:.contributor-list a|wikilink}}",
+      "type": "text"
+    },
+    {
+      "name": "space",
+      "value": "{{selector:#breadcrumb-nav a:first-child}}",
+      "type": "text"
+    },
+    {
+      "name": "labels",
+      "value": "{{selector:.label-list a}}",
+      "type": "multitext"
+    },
+    {
+      "name": "last-modified",
+      "value": "{{selector:.last-modified time}}",
+      "type": "text"
+    },
+    {
+      "name": "clipped-date",
+      "value": "{{date}}",
+      "type": "date"
+    },
+    {
+      "name": "status",
+      "value": "inbox",
+      "type": "text"
+    },
+    {
+      "name": "tags",
+      "value": "[confluence-clip, {{\"Based on this Confluence page content, suggest 3 relevant topic tags as comma-separated values (no # prefix, lowercase, hyphenated). Output ONLY the tags, nothing else.\"|prompt}}]",
+      "type": "multitext"
+    }
+  ],
+  "noteNameFormat": "{{date}} — {{title|safe_name|truncate:80}}",
+  "path": "00-Inbox",
+  "triggers": ["atlassian.net/wiki", "confluence"],
+  "context": "{{content}}",
+  "body": "## Summary\n\n{{\"Summarize the key points of this Confluence page in 3-5 bullet points. Focus on decisions, action items, and important context. Be concise.\"|prompt}}\n\n---\n\n## Original Content\n\n{{content}}"
+}