mindlore 0.2.1 → 0.3.0

package/skills/mindlore-ingest/SKILL.md

@@ -9,6 +9,14 @@ allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch]
 
 Add a new knowledge source to the `.mindlore/` knowledge base.
 
+## Scope
+
+Determine target directory using `getActiveMindloreDir()` logic:
+- If CWD has `.mindlore/` → write to project scope
+- Otherwise → write to global `~/.mindlore/`
+- `--global` flag: force write to `~/.mindlore/` even if project scope exists
+- Never hardcode `.mindlore/` path — always resolve dynamically
+
 ## Trigger
 
 User shares a URL, text, file, or says "kaynak ekle", "source ingest", "bu linki kaydet", "knowledge ingest".
@@ -17,8 +25,12 @@ User shares a URL, text, file, or says "kaynak ekle", "source ingest", "bu linki
 
 ### URL Mode
 1. Extract content from URL:
-   - If `markitdown` is available: `markitdown <url>` (best quality, zero tokens)
+   - If `markitdown` is available (`hasMarkitdown()`): `markitdown <url>` (best quality, zero tokens)
    - Else: use `WebFetch` or `ctx_fetch_and_index`
+   - **YouTube URL** detected (`youtube.com` or `youtu.be`):
+     1. markitdown installed → `markitdown <url>` (includes transcript)
+     2. Else youtube-transcript npm → `hasYoutubeTranscript()` check
+     3. Else → ask user to paste transcript manually
 2. Save raw capture to `.mindlore/raw/` with frontmatter:
    ```yaml
    ---
@@ -75,9 +87,12 @@ The sources/ file should contain:
 
 ## Quality Assessment
 
-- `high`: Primary source, authoritative, detailed, directly relevant
-- `medium`: Useful but secondary, partial coverage, or tangentially relevant
-- `low`: Reference only, outdated, or low signal-to-noise
+Assign quality automatically during ingest using this heuristic:
+- `high`: Official docs (anthropic, github docs, MDN), primary research, authoritative references
+- `medium`: Blog posts, tutorials, conference talks, X threads with substance
+- `low`: Raw notes, text pastes, quick captures, low signal-to-noise
+
+LLM may override the heuristic based on content analysis. Always set quality — never leave it null.
 
 ## Domain Update Rules
 

package/skills/mindlore-log/SKILL.md

@@ -2,6 +2,14 @@
 
 Session logging, pattern extraction, and wiki updates.
 
+## Scope
+
+Determine target using `getActiveMindloreDir()` logic:
+- If CWD has `.mindlore/` → write to project scope
+- Otherwise → write to global `~/.mindlore/`
+- Reflect mode: scans both project + global diary/ for patterns
+- Never hardcode `.mindlore/` path — always resolve dynamically
+
 ## Trigger
 
 `/mindlore-log <mode>` where mode is `log`, `reflect`, `status`, or `save`.
@@ -30,19 +38,28 @@ date: 2026-04-11
 
 ### reflect
 
-Scan old deltas, extract patterns, write to learnings/.
-
-**Flow (v0.2 — basic):**
-1. Read all non-archived delta files in `diary/` (no `archived: true` frontmatter)
-2. Present summary to user: "Found N unprocessed deltas spanning DATE1 to DATE2"
-3. For each delta, extract: repeated topics, recurring decisions, common file changes
-4. Propose learnings to user: "I found these patterns: ..."
-5. User approves → write to `learnings/{topic}.md` (append if exists, create if not)
-6. Format: `YAPMA:` / `BEST PRACTICE:` / `KRITIK:` prefixed rules
-7. Mark processed deltas: add `archived: true` to their frontmatter
-8. Append to `log.md`: `| {date} | reflect | {N} deltas processed, {M} learnings written |`
-
-**Important:** Do NOT auto-extract patterns. Present findings, user approves. This is v0.2 basic mode — automated pattern extraction deferred to v0.2.1.
+LLM-driven pattern extraction from diary deltas → persistent learnings.
+
+**Flow (v0.3 — LLM-driven):**
+1. Read last N non-archived delta files in `diary/` (no `archived: true` frontmatter)
+2. Present summary: "Found N unprocessed deltas spanning DATE1 to DATE2"
+3. LLM analyzes deltas for repeating patterns:
+   - Recurring topics/themes across sessions
+   - Repeated decisions (same choice made multiple times)
+   - Common mistakes or friction points
+   - Workflow patterns that worked well
+4. Categorize found patterns by topic (git, testing, architecture, etc.)
+5. Present findings to user with proposed learnings
+6. User approves → write to `learnings/{topic}.md` (append if exists, create if not)
+7. Format: `YAPMA:` / `BEST PRACTICE:` / `KRITIK:` prefixed rules
+8. Update relevant domain page if pattern relates to an existing domain
+9. Mark processed deltas: add `archived: true` to their frontmatter
+10. Append to `log.md`: `| {date} | reflect | {N} deltas processed, {M} learnings written |`
+
+**Rules:**
+- NEVER write learnings without user approval
+- Group related patterns into existing topic files (don't create one file per pattern)
+- Reflect scans both project + global diary/ in `--all` mode
 
 ### status
 

package/skills/mindlore-query/SKILL.md

@@ -2,6 +2,14 @@
 
 Search, ask, analyze, and retrieve knowledge from `.mindlore/`.
 
+## Scope
+
+Determine search scope using `getActiveMindloreDir()` / `getAllDbs()` logic:
+- Default (no flag): search project `.mindlore/` DB, fall back to global
+- `--global`: search only `~/.mindlore/` DB
+- `--all`: search both project + global DBs, project results first
+- Never hardcode `.mindlore/` path — always resolve dynamically
+
 ## Trigger
 
 `/mindlore-query <mode> [query]` where mode is `search`, `ask`, `stats`, or `brief`.

package/templates/SCHEMA.md

@@ -28,6 +28,18 @@ with YAML frontmatter. Search is powered by FTS5 (SQLite full-text search).
 └── mindlore.db     # FTS5 search database (SQLite)
 ```
 
+### Global Scope (v0.3)
+
+Mindlore supports two scopes:
+- **Project scope:** `.mindlore/` in the current working directory (project-specific knowledge)
+- **Global scope:** `~/.mindlore/` in the user's home directory (cross-project knowledge)
+
+Rules:
+- `getActiveMindloreDir()` resolves scope: project if exists, otherwise global
+- Search is layered: project results first, global results second
+- Skills accept `--global` (force global) and `--all` (both scopes) flags
+- `npx mindlore init --global` creates `~/.mindlore/` with git repo for auto-sync
+
 ### Directory Rules
 
 - Each directory corresponds to exactly one frontmatter `type` value
@@ -143,7 +155,7 @@ Discover unexpected connections between sources. Cross-reference analysis.
 - Max results: 3 per query (BM25 ranking)
 - Hook injects: file path + first 2 headings
 
-### FTS5 Columns (9-col schema, v0.2)
+### FTS5 Columns (10-col schema, v0.3)
 
 | Column | Indexed | Source |
 |--------|---------|--------|
@@ -155,7 +167,8 @@ Discover unexpected connections between sources. Cross-reference analysis.
 | `title` | Yes | Frontmatter title or first heading |
 | `content` | Yes | Markdown body (sans frontmatter) |
 | `tags` | Yes | Frontmatter tags (comma-separated) |
-| `quality` | UNINDEXED | Frontmatter quality (NULL until 50+ sources) |
+| `quality` | UNINDEXED | Frontmatter quality (high/medium/low) |
+| `date_captured` | UNINDEXED | Frontmatter date_captured or date |
 
 ### Search Flow (UserPromptSubmit hook)