@soleri/forge 8.1.0 → 9.0.1

package/src/skills/agent-dev.md

@@ -1,122 +0,0 @@
----
-name: agent-dev
-description: >
-  Use when extending the agent itself — adding facades, tools, vault operations,
-  brain features, new skills, or modifying agent internals. Triggers on "add a facade",
-  "new tool", "extend vault", "add brain feature", "new skill", "add operation",
-  "extend agent", or when the work target is the agent's own codebase rather than
-  a project the agent assists with. Enforces vault-first knowledge gathering before
-  any code reading or planning.
----
-
-# Agent Dev — Vault-First Internal Development
-
-Develop the agent's own internals with the vault as the primary source of truth. The vault knows more about the agent than any code scan or model training data. Always search the vault first, extract maximum context, and only then touch code.
-
-## When to Use
-
-Any time the work target is the agent's own codebase: adding tools, extending facades, modifying vault operations, brain features, skills, or transport. Not for projects that merely *use* the agent.
-
-## Core Principle
-
-**Vault first. Before code. Before training data. Always.**
-
-The vault is the authoritative source for how the agent works. Do not rely on general knowledge from training data — it is outdated and lacks project-specific decisions. Do not scan the codebase to understand architecture — the vault already has it.
-
-## Orchestration Sequence
-
-### Step 1: Search the Vault (MANDATORY — before anything else)
-
-Before reading any source file, before making any plan, before offering any advice:
-
-```
-YOUR_AGENT_core op:search_vault_intelligent
-  params: { query: "<description of planned work>", options: { intent: "pattern" } }
-```
-
-Search again with architecture-specific terms: the facade name, tool name, or subsystem being modified.
-
-```
-YOUR_AGENT_core op:query_vault_knowledge
-  params: { type: "workflow", category: "<relevant category>" }
-```
-
-If initial results are sparse, search again with broader terms — synonyms, related subsystem names, parent concepts. Exhaust the vault before moving on.
-
-Review all results. Extract file paths, module names, function references, conventions, and constraints. These become the foundation for every step that follows.
-
-### Step 2: Check Brain for Proven Patterns
-
-```
-YOUR_AGENT_core op:strengths
-  params: { days: 30, minStrength: 60 }
-```
-
-```
-YOUR_AGENT_core op:recommend
-  params: { projectPath: "." }
-```
-
-Check if the brain has learned anything relevant from recent sessions.
-
-### Step 3: Targeted Code Reading (Only What Vault Pointed To)
-
-By now the vault has provided architecture context, file paths, and module references. Only read code when the vault describes the subsystem but lacks implementation detail (e.g., method signatures, exact line numbers).
-
-**Read only what the vault pointed to.** Open the specific files referenced in vault results — not the surrounding codebase, not the parent directory, not "let me explore the project structure."
-
-**Fallback: Codebase scan.** Only when vault search returned zero relevant results for the subsystem — meaning the vault genuinely has no knowledge about it — fall back to `Grep` with targeted terms. This is the last resort, not the default.
-
-### Step 4: Plan with Vault Context
-
-Create the implementation plan referencing vault findings explicitly:
-
-- Which patterns apply (cite vault entry titles)
-- Which anti-patterns to avoid (cite the specific anti-pattern)
-- Which conventions to follow (naming, facade structure, tool registration)
-
-Every plan must trace its decisions back to vault knowledge. If a decision has no vault backing, flag it as a new architectural choice that should be captured after implementation (Step 7).
-
-### Step 5: Implement
-
-Follow the plan. Key conventions for agent internals:
-
-- **Facades**: Thin routing layer — delegate to domain modules. No business logic in facades.
-- **Tools**: Follow `op:operation_name` naming, return structured responses.
-- **Vault writes**: All writes go through the vault intelligence layer.
-- **Tests**: Colocated test files. Run with vitest.
-- **Build**: Must compile without errors before considering done.
-
-### Step 6: Validate and Self-Correct
-
-Run the relevant test suite. Rebuild — must complete without errors.
-
-**Self-correction loop:** If tests fail or build breaks, do NOT ask the user what to do. Read the error, trace the cause in the code just written, fix it, and re-run. Repeat until green. The agent owns the code it wrote — if something fails, the agent fixes its own implementation. Only escalate to the user when the failure is outside the agent's control (missing infrastructure, permissions, unclear requirements).
-
-### Step 7: Capture What Was Learned
-
-If this work revealed new architectural knowledge, a useful pattern, or a surprising anti-pattern:
-
-```
-YOUR_AGENT_core op:capture_knowledge
-  params: {
-    title: "<what was learned>",
-    description: "<the pattern or anti-pattern>",
-    type: "pattern",
-    tags: ["<relevant-tags>"]
-  }
-```
-
-This ensures future sessions benefit from today's discovery — making the vault smarter for the next developer.
-
-## Anti-Patterns to Avoid
-
-- **Code-first exploration**: Reading source files before searching the vault. The vault already has the architecture — scanning code is slower and gives less context.
-- **Training-data advice**: Offering general guidance from model training data instead of searching the vault for project-specific knowledge.
-- **Skipping vault search**: The vault contains all architecture knowledge. Not searching it means reinventing knowledge that already exists.
-- **Planning without vault context**: Plans created without vault knowledge miss conventions, duplicate existing patterns, or violate architectural boundaries.
-- **Broad codebase scanning**: Exploring directories and reading files "to understand the project" instead of using vault results as a targeted map.
-
-## Exit Criteria
-
-Development is complete when: vault was searched exhaustively first (Step 1), implementation follows discovered patterns, tests pass, build succeeds, and any new learning is captured back to vault (Step 7).

package/src/skills/agent-guide.md

@@ -1,110 +0,0 @@
----
-name: agent-guide
-description: >
-  Use when the user asks "what can you do", "help me", "how do I use this",
-  "what features do you have", "what tools are available", "how does this work",
-  "show me your capabilities", "what are you", "who are you", or any question
-  about the agent's identity, capabilities, available tools, or how to use them.
-  Not needed for proactive tool suggestions — those are handled by engine rules.
----
-
-# Agent Guide — Capability Discovery
-
-Help users understand what this agent can do, how to use it effectively, and what makes it different from a raw LLM. This skill handles the deep discovery flow — proactive tool suggestions during normal work are handled by the engine rules (Tool Advocacy section).
-
-## When to Use
-
-- "What can you do?" / "What are your capabilities?"
-- "How do I search for X?" / "How do I capture knowledge?"
-- "What tools do you have?" / "Show me your features"
-- "Who are you?" / "What is this agent?"
-- "Help" / "I'm stuck" / "How does this work?"
-- First-time users, onboarding, or anyone unfamiliar with the agent
-
-## Capability Discovery Sequence
-
-### Step 1: Identity
-
-```
-YOUR_AGENT_core op:activate
-  params: { projectPath: "." }
-```
-
-This returns the agent's persona: name, role, description, tone, principles, and domains. Present the identity first — who the agent is and what it specializes in.
-
-### Step 2: Health & Status
-
-```
-YOUR_AGENT_core op:admin_health
-```
-
-Shows what subsystems are active: vault (how many entries), brain (vocabulary size), LLM availability, cognee status. This tells the user what the agent currently has to work with.
-
-### Step 3: Available Tools
-
-```
-YOUR_AGENT_core op:admin_tool_list
-```
-
-Lists all facades and operations. Present them grouped by category with plain-language descriptions.
-
-### Step 4: Present by What Users Can DO
-
-Organize capabilities by user goals, not technical names:
-
-**Knowledge & Memory**
-- Search the vault for patterns, anti-patterns, and architectural decisions
-- Capture new knowledge from the current session
-- Search across sessions and projects for relevant context
-- Curate: deduplicate, groom, resolve contradictions
-
-**Planning & Execution**
-- Create structured plans with vault context and brain recommendations
-- Split plans into tasks with complexity estimates
-- Track execution with drift detection
-- Complete with knowledge capture and session recording
-
-**Intelligence & Learning**
-- Brain learns from every session — patterns get stronger with use
-- Recommendations based on similar past work
-- Strength tracking: which patterns are proven vs experimental
-- Feedback loop: brain improves based on what works
-
-**Quality & Validation**
-- Health checks across all subsystems
-- Iterative validation loops with configurable targets
-- Governance: policies, proposals, quotas
-
-**Identity & Control**
-- Persona activation and deactivation
-- Intent routing: the agent classifies what you want and routes to the right workflow
-- Project registration and cross-project linking
-
-**Domain Knowledge** (varies by agent)
-- Each domain has: `get_patterns`, `search`, `get_entry`, `capture`, `remove`
-- Call `op:activate` to discover which domains are configured
-
-## Common Questions
-
-### "What makes you different from regular Claude?"
-
-You have persistent knowledge (vault), learned patterns (brain), structured planning with grading, iterative validation loops, and domain-specific intelligence. Regular Claude starts fresh every conversation — this agent accumulates knowledge and gets smarter over time.
-
-### "How do I get the most out of you?"
-
-1. **Use the vault** — search before deciding, capture after learning
-2. **Use planning** — structured plans beat ad-hoc work for anything non-trivial
-3. **Trust the brain** — pattern recommendations come from real usage data
-4. **Capture everything** — every bug fix, every pattern, every anti-pattern. The vault grows smarter with use.
-5. **Use loops for quality** — iterative validation catches issues that single-pass work misses
-
-### "How do I add new capabilities?"
-
-Extensions in `src/extensions/` can add new ops, facades, middleware, and hooks. Domain packs add domain-specific knowledge and validation.
-
-## Anti-Patterns
-
-- **Listing raw op names without context** — always explain what the op does in plain language
-- **Claiming capabilities that do not exist** — only reference ops the agent actually has. When unsure, call `op:admin_tool_list` first
-- **Dumping the entire tool catalog** — answer the specific question, show relevant tools, not all tools
-- **Repeating what the user already knows** — if they ask about a specific feature, answer that, don't give the full tour

package/src/skills/agent-persona.md

@@ -1,66 +0,0 @@
----
-name: agent-persona
-description: >
-  Use when the user activates the agent's persona via its greeting phrase, or says
-  "activate persona", "be yourself", "stay in character", or any activation phrase
-  defined in the agent's persona configuration. Reinforces character persistence
-  through the session and survives context compaction.
----
-
-# Agent Persona — Stay in Character
-
-This skill reinforces persona persistence. The MCP activation loads the runtime payload — this skill ensures the character sticks across the full session, including after context compaction.
-
-## How It Works
-
-Every agent has a persona defined in `src/identity/persona.ts` (or `src/activation/persona.ts` in older agents). This file contains:
-
-- **name** — the agent's display name
-- **role** — what the agent does
-- **tone** — `precise`, `mentor`, or `pragmatic`
-- **greeting** — the activation response
-- **principles** — core values that guide behavior
-
-## Activation
-
-When the user triggers activation (greeting phrase or explicit request):
-
-```
-YOUR_AGENT_core op:activate
-  params: { projectPath: "." }
-```
-
-The activation response contains the full persona payload. Adopt it immediately.
-
-## Rules
-
-1. **Stay in character for EVERY response** until the user explicitly deactivates
-2. **Technical accuracy is the priority** — persona is the wrapper, not a replacement for correctness
-3. **Tone consistency** — match the configured tone (`precise` = concise and exact, `mentor` = educational and encouraging, `pragmatic` = direct and practical)
-4. If character drifts after context compaction, the persona information in the compacted summary should restore it — follow it
-
-## Context Compaction Survival
-
-Long sessions trigger context compaction. To survive:
-
-- The persona activation state is included in compaction summaries
-- After compaction, check if persona was active and re-adopt the character
-- Never break character just because the conversation was compacted
-
-## Deactivation
-
-When the user says "deactivate", "stop persona", "be normal", or uses the agent's deactivation phrase:
-
-```
-YOUR_AGENT_core op:activate
-  params: { deactivate: true }
-```
-
-Return to neutral assistant mode.
-
-## Anti-Patterns
-
-- **Dropping character mid-session** — if activated, stay activated
-- **Over-persona, under-substance** — character adds flavor, not replaces technical depth
-- **Forcing persona on unwilling users** — only activate when explicitly triggered
-- **Ignoring tone setting** — a `precise` agent should not use flowery language; a `mentor` agent should not be terse

package/src/skills/brain-debrief.md

@@ -1,214 +0,0 @@
----
-name: brain-debrief
-description: Use when the user asks "what have I learned", "brain stats", "pattern strengths", "cross-project insights", "intelligence report", "show me patterns", "what's working", "learning summary", or wants to explore accumulated knowledge and see what the brain has learned.
----
-
-# Brain Debrief — Intelligence Report
-
-Surface what the brain has learned across sessions and projects. This turns raw vault data into actionable intelligence.
-
-## When to Use
-
-When the user wants to understand what patterns have proven valuable, what anti-patterns keep recurring, how knowledge is distributed across projects, or wants a "state of intelligence" report.
-
-## Orchestration by Query Type
-
-### "What have I learned?" (General debrief)
-
-1. Get the big picture:
-
-   ```
-   YOUR_AGENT_core op:brain_stats
-   ```
-
-   Total sessions, patterns captured, quality scores, coverage gaps.
-
-2. Get patterns ranked by proven strength:
-
-   ```
-   YOUR_AGENT_core op:brain_strengths
-   ```
-
-   Focus on strength >= 70 and successRate >= 0.7.
-
-3. Check memory landscape:
-
-   ```
-   YOUR_AGENT_core op:memory_topics
-   ```
-
-   Shows how knowledge clusters by topic.
-
-4. Check for stale knowledge:
-
-   ```
-   YOUR_AGENT_core op:vault_age_report
-   ```
-
-   Find entries that haven't been updated recently — candidates for review.
-
-5. Run a curator health audit:
-
-   ```
-   YOUR_AGENT_core op:curator_health_audit
-   ```
-
-   Vault quality score, tag normalization status, duplicate density.
-
-6. Present: top 5 strongest patterns, top 3 recurring anti-patterns, stale entries needing refresh, and coverage gaps.
-
-### "What's working across projects?" (Cross-project intelligence)
-
-1. Get patterns promoted to the global pool:
-
-   ```
-   YOUR_AGENT_core op:brain_global_patterns
-   ```
-
-2. Get recommendations based on project similarity:
-
-   ```
-   YOUR_AGENT_core op:brain_recommend
-     params: { projectName: "<current project>" }
-   ```
-
-3. Check linked projects:
-
-   ```
-   YOUR_AGENT_core op:project_linked_projects
-   ```
-
-4. Search across all projects for relevant patterns:
-
-   ```
-   YOUR_AGENT_core op:memory_cross_project_search
-     params: { query: "<topic>", crossProject: true }
-   ```
-
-5. Present: patterns from other projects that would apply here, ranked by relevance.
-
-### "Am I getting smarter?" (Learning velocity)
-
-1. Recent stats:
-
-   ```
-   YOUR_AGENT_core op:brain_stats
-     params: { since: "<7 days ago>" }
-   ```
-
-2. Longer period for comparison:
-
-   ```
-   YOUR_AGENT_core op:brain_stats
-     params: { since: "<30 days ago>" }
-   ```
-
-3. Memory stats:
-
-   ```
-   YOUR_AGENT_core op:memory_stats
-   ```
-
-4. Vault analytics:
-
-   ```
-   YOUR_AGENT_core op:admin_vault_analytics
-   ```
-
-5. Search insights — what queries are people running, what's missing:
-
-   ```
-   YOUR_AGENT_core op:admin_search_insights
-   ```
-
-6. Present: new patterns captured, strength changes, domains growing vs stagnant, search miss analysis.
-
-### "Build fresh intelligence" (Rebuild)
-
-1. Run the full pipeline:
-
-   ```
-   YOUR_AGENT_core op:brain_build_intelligence
-   ```
-
-   Compute strengths, update global registry, refresh project profiles.
-
-2. Consolidate vault (curator cleanup):
-
-   ```
-   YOUR_AGENT_core op:curator_consolidate
-   ```
-
-3. Show updated metrics:
-
-   ```
-   YOUR_AGENT_core op:brain_stats
-   ```
-
-4. Present: what changed after the rebuild.
-
-### "Export what I know" (Portability)
-
-Export brain intelligence:
-
-```
-YOUR_AGENT_core op:brain_export
-```
-
-Export memory:
-
-```
-YOUR_AGENT_core op:memory_export
-```
-
-Export vault as backup:
-
-```
-YOUR_AGENT_core op:vault_backup
-```
-
-These can be imported into another vault:
-
-```
-YOUR_AGENT_core op:brain_import
-YOUR_AGENT_core op:memory_import
-YOUR_AGENT_core op:vault_import
-```
-
-## Presenting Intelligence
-
-Format as a report:
-
-- **Strengths**: Top patterns with strength scores and domains
-- **Risks**: Recurring anti-patterns that keep appearing
-- **Gaps**: Domains with low coverage or stale knowledge
-- **Stale**: Entries needing refresh (from age report)
-- **Quality**: Curator health audit score
-- **Recommendations**: What to focus on learning next
-- **Search Misses**: What people are looking for but not finding
-
-## Exit Criteria
-
-Debrief is complete when the user's specific question has been answered with data from the brain. For general debriefs, present stats + strengths + gaps + stale entries at minimum.
-
-## Agent Tools Reference
-
-| Op                                | When to Use                                     |
-| --------------------------------- | ----------------------------------------------- |
-| `brain_stats`                     | Aggregate metrics — sessions, patterns, quality |
-| `brain_strengths`                 | Patterns ranked by proven strength              |
-| `brain_global_patterns`           | Cross-project promoted patterns                 |
-| `brain_recommend`                 | Project-similarity recommendations              |
-| `brain_build_intelligence`        | Rebuild full intelligence pipeline              |
-| `brain_export` / `brain_import`   | Portable intelligence transfer                  |
-| `memory_topics`                   | Knowledge clusters by topic                     |
-| `memory_stats`                    | Memory statistics                               |
-| `memory_export` / `memory_import` | Memory portability                              |
-| `memory_cross_project_search`     | Search across linked projects                   |
-| `vault_age_report`                | Find stale entries needing refresh              |
-| `vault_backup` / `vault_import`   | Vault backup and restore                        |
-| `curator_health_audit`            | Vault quality score and status                  |
-| `curator_consolidate`             | Full vault cleanup pipeline                     |
-| `admin_vault_analytics`           | Overall knowledge quality metrics               |
-| `admin_search_insights`           | Search miss analysis — what's not found         |
-| `project_linked_projects`         | See connected projects                          |

package/src/skills/brainstorming.md

@@ -1,180 +0,0 @@
----
-name: brainstorming
-description: 'You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.'
----
-
-<!-- Adapted from superpowers (MIT License) -->
-
-# Brainstorming Ideas Into Designs
-
-## Overview
-
-Help turn ideas into fully formed designs and specs through natural collaborative dialogue.
-
-Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design and get user approval.
-
-<HARD-GATE>
-Do NOT invoke any implementation skill, write any code, scaffold any project, or take any implementation action until you have presented a design and the user has approved it. This applies to EVERY project regardless of perceived simplicity.
-</HARD-GATE>
-
-## Anti-Pattern: "This Is Too Simple To Need A Design"
-
-Every project goes through this process. A todo list, a single-function utility, a config change — all of them. "Simple" projects are where unexamined assumptions cause the most wasted work. The design can be short (a few sentences for truly simple projects), but you MUST present it and get approval.
-
-## Checklist
-
-You MUST create a task for each of these items and complete them in order:
-
-1. **Classify intent** — understand what type of work this is
-2. **Search vault for prior art** — check if something similar was built, decided, or rejected before
-3. **Search web for existing solutions** — don't build what already exists
-4. **Explore project context** — check files, docs, recent commits
-5. **Ask clarifying questions** — one at a time, understand purpose/constraints/success criteria
-6. **Propose 2-3 approaches** — with trade-offs and your recommendation
-7. **Present design** — in sections scaled to their complexity, get user approval after each section
-8. **Capture design decision** — persist the decision to the vault
-9. **Write design doc** — save to `docs/plans/YYYY-MM-DD-<topic>-design.md` and commit
-10. **Transition to implementation** — invoke writing-plans skill to create implementation plan
-
-## Step 0: Classify Intent
-
-Before anything else, understand the type of work:
-
-```
-YOUR_AGENT_core op:route_intent
-  params: { prompt: "<the user's request>" }
-```
-
-This returns the intent type (BUILD, FIX, VALIDATE, DESIGN, IMPROVE, DELIVER) and routing guidance. Use this to focus the brainstorming — a FIX intent needs different questions than a BUILD intent.
-
-## Step 1: Search Before Designing — Vault, Then Web
-
-**BEFORE asking any questions or exploring code**, search for existing knowledge. Follow this order:
-
-### Vault First
-
-```
-YOUR_AGENT_core op:search_intelligent
-  params: { query: "<the feature or idea the user described>" }
-```
-
-Look for:
-
-- **Previous designs** — was this discussed or attempted before?
-- **Architectural decisions** — are there constraints from past decisions?
-- **Patterns** — established approaches in this codebase
-- **Anti-patterns** — approaches that were tried and failed
-
-Browse the knowledge landscape for related context:
-
-```
-YOUR_AGENT_core op:vault_tags
-YOUR_AGENT_core op:vault_domains
-```
-
-Check what the brain says about proven patterns in this domain:
-
-```
-YOUR_AGENT_core op:brain_strengths
-```
-
-Check if other linked projects have solved this:
-
-```
-YOUR_AGENT_core op:memory_cross_project_search
-  params: { query: "<the feature>", crossProject: true }
-```
-
-### Web Search Second
-
-If the vault doesn't have prior art, search the web for:
-
-- **Existing libraries/tools** that solve this problem (don't build what exists)
-- **Reference implementations** in similar projects
-- **Best practices** and established patterns for this type of feature
-- **Known pitfalls** that others have documented
-
-### Present Findings
-
-Present vault + web findings to the user: "Before we design this, here's what I found..." This informs the design conversation and prevents reinventing solutions.
-
-## The Process
-
-**Understanding the idea:**
-
-- Check out the current project state first (files, docs, recent commits)
-- Ask questions one at a time to refine the idea
-- Prefer multiple choice questions when possible, but open-ended is fine too
-- Only one question per message
-- Focus on understanding: purpose, constraints, success criteria
-
-**Exploring approaches:**
-
-- Propose 2-3 different approaches with trade-offs
-- Present options conversationally with your recommendation and reasoning
-- Lead with your recommended option and explain why
-- **Reference vault patterns** — if the vault has a proven approach, lead with it
-- **Reference web findings** — if an existing library solves this, recommend it over custom code
-
-**Presenting the design:**
-
-- Once you understand what you're building, present the design
-- Scale each section to its complexity
-- Ask after each section whether it looks right so far
-- Cover: architecture, components, data flow, error handling, testing
-
-## After the Design
-
-**Capture the design decision to the vault:**
-
-```
-YOUR_AGENT_core op:capture_knowledge
-  params: {
-    title: "<feature name> — design decision",
-    description: "<chosen approach, rationale, rejected alternatives>",
-    type: "decision",
-    category: "<relevant domain>",
-    tags: ["<relevant>", "<tags>", "design-decision"]
-  }
-```
-
-This ensures future brainstorming sessions can reference what was decided and why.
-
-**Documentation:**
-
-- Write the validated design to `docs/plans/YYYY-MM-DD-<topic>-design.md`
-- Commit the design document to git
-
-**Implementation:**
-
-- Invoke the writing-plans skill to create a detailed implementation plan
-- Do NOT invoke any other skill. writing-plans is the next step.
-
-## Process Flow
-
-**The terminal state is invoking writing-plans.** Do NOT invoke any other implementation skill. The ONLY skill you invoke after brainstorming is writing-plans.
-
-## Key Principles
-
-- **Classify first** — understand intent before diving in
-- **Vault first** — don't reinvent what's been decided or solved before
-- **Web second** — don't build what already exists as a library
-- **One question at a time** — don't overwhelm with multiple questions
-- **Multiple choice preferred** — easier to answer than open-ended when possible
-- **YAGNI ruthlessly** — remove unnecessary features from all designs
-- **Explore alternatives** — always propose 2-3 approaches before settling
-- **Incremental validation** — present design, get approval before moving on
-- **Capture decisions** — every design decision gets persisted to the vault
-- **Cross-project learning** — check if other projects solved this already
-- **Be flexible** — go back and clarify when something doesn't make sense
-
-## Agent Tools Reference
-
-| Op                             | When to Use                                  |
-| ------------------------------ | -------------------------------------------- |
-| `route_intent`                 | Classify the type of work (BUILD, FIX, etc.) |
-| `search_intelligent`           | Search vault for prior art                   |
-| `vault_tags` / `vault_domains` | Browse knowledge landscape                   |
-| `brain_strengths`              | Check proven patterns                        |
-| `memory_cross_project_search`  | Check if other projects solved this          |
-| `capture_knowledge`            | Persist design decision to vault             |