dominds 1.3.1 → 1.4.2

package/dist/tools/prompts/memory/en/errors.md

@@ -1,155 +0,0 @@
-# memory Error Handling
-
-## Template (Errors)
-
-### Error Chain (required)
-
-1. Trigger Condition
-2. Detection Signal
-3. Recovery Steps
-4. Success Criteria
-5. Escalation Path (optional)
-
-## Error Codes
-
-### MEMORY_ALREADY_EXISTS
-
-**Description:** Path already exists, cannot use `add_memory` to create new memory.
-
-**Cause:**
-
-- The path you're trying to add is already occupied by another memory
-
-**Solution:**
-
-- Use `replace_memory` to update existing memory
-- Or use a different path to create new memory
-
-**Example:**
-
-```
-Error:
-status: error
-error_code: MEMORY_ALREADY_EXISTS
-message: Path "project/todo" already exists, please use replace_memory to update
-```
-
-### MEMORY_NOT_FOUND
-
-**Description:** Path does not exist, cannot perform operation.
-
-**Cause:**
-
-- The memory path you're trying to access doesn't exist
-- The path was deleted or never created
-
-**Solution:**
-
-- For update/delete operations, first use `add_memory` to create
-- Check if the path is correct
-
-**Example:**
-
-```
-Error:
-status: error
-error_code: MEMORY_NOT_FOUND
-message: Path "project/todo" does not exist, please use add_memory to create first
-```
-
-### MEMORY_PATH_INVALID
-
-**Description:** Path format is invalid.
-
-**Cause:**
-
-- Path contains illegal characters
-- Path length exceeds limit
-
-**Solution:**
-
-- Ensure path only contains letters, numbers, underscores, slashes
-- Path length should not exceed 255 characters
-
-**Example:**
-
-```
-Error:
-status: error
-error_code: MEMORY_PATH_INVALID
-message: Path "project/*invalid*" contains illegal characters
-```
-
-### MEMORY_CONTENT_TOO_LARGE
-
-**Description:** Memory content is too large.
-
-**Cause:**
-
-- Single memory content exceeds 1MB limit
-
-**Solution:**
-
-- Compress content
-- Split into multiple memories
-- Use external storage (e.g., files)
-
-**Example:**
-
-```
-Error:
-status: error
-error_code: MEMORY_CONTENT_TOO_LARGE
-message: Content size 1.2MB exceeds 1MB limit
-```
-
-### MEMORY_STORAGE_ERROR
-
-**Description:** Storage error.
-
-**Cause:**
-
-- Insufficient disk space
-- Permission issues
-- File system error
-
-**Solution:**
-
-- Check disk space
-- Check file permissions
-- Retry operation
-
-**Example:**
-
-```
-Error:
-status: error
-error_code: MEMORY_STORAGE_ERROR
-message: Cannot write to storage, insufficient disk space
-```
-
-## Frequently Asked Questions
-
-### Q: Does memory auto-save?
-
-A: Yes, all memory operations are immediately persisted to disk. No manual save is needed.
-
-### Q: Is there a limit on the number of memories?
-
-A: There's no strict limit, but it's recommended to keep the number of memories reasonable (less than 100 recommended).
-
-### Q: Can other members see my memories?
-
-A: No, memory is a personal memory tool, only the current agent can access it. If you need to share with team members, please use team_memory.
-
-### Q: Will clear_memory delete all memories?
-
-A: Yes, `clear_memory` will delete all personal memories, this operation is irreversible. Please use with caution.
-
-### Q: Do memories expire?
-
-A: No, memories are permanently saved until explicitly deleted.
-
-### Q: How do I view all current memories?
-
-A: The agent can access all personal memories during response generation. You can directly ask the agent what memories it currently has.

package/dist/tools/prompts/memory/en/index.md

@@ -1,47 +0,0 @@
-# memory Personal Memory Tools Manual
-
-## Template (Index)
-
-### One-line Positioning
-
-- <What this toolset is for, in one sentence>
-
-### Tool List
-
-- <Enumerate core tools or point to Tools/Schema section>
-
-### 30-Second Quickstart
-
-1. <call ...>
-2. <observe ...>
-3. <next step ...>
-
-### Navigation
-
-- principles / tools / scenarios / errors
-
-### Boundaries vs Other Toolsets
-
-- <When to use this vs a sibling toolset>
-
-memory is Dominds' **personal memory toolset** for managing an agent's private memory:
-
-- **Privacy**: Memory is only visible to the current agent, not shared with other members
-- **Persistence**: Memory is persisted to disk and retained after conversation restarts
-- **Structured**: Supports organizing memory by path for easy categorization and retrieval
-
-## Quick Navigation
-
-| Topic                         | Description                                     |
-| ----------------------------- | ----------------------------------------------- |
-| [principles](./principles.md) | Core concepts, memory lifecycle, best practices |
-| [tools](./tools.md)           | Complete tool list and interface contracts      |
-| [scenarios](./scenarios.md)   | Common usage scenarios (copy-paste ready)       |
-| [errors](./errors.md)         | Error codes and solutions                       |
-
-## Status
-
-- Status: Implemented
-- Main implementation files:
-  - Tool implementation: `dominds/main/tools/mem.ts`
-  - Toolset metadata: `dominds/main/tools/builtins.ts`, `dominds/main/tools/registry.ts`

package/dist/tools/prompts/memory/en/principles.md

@@ -1,87 +0,0 @@
-# memory Principles and Core Concepts
-
-## Template (Principles)
-
-### Design Goals
-
-- <Goal 1>
-- <Goal 2>
-
-### Contract Principles
-
-- <Input/Output contract rules>
-
-### Safety & Boundaries
-
-- <Access constraints / guardrails>
-
-### Failure & Recovery
-
-- <What to do when a call fails>
-
-### Glossary
-
-- <Toolset-specific terms>
-
-## Memory Model
-
-The memory toolset uses a **path key-value storage** model:
-
-- **Path**: Unique identifier for the memory, similar to a file system path, e.g., `project/todo` or `user/preferences/theme`
-- **Content**: Actual content of the memory, can be arbitrary text
-
-## Tool Overview
-
-| Tool           | Function                                     |
-| -------------- | -------------------------------------------- |
-| add_memory     | Create new memory (when path does not exist) |
-| replace_memory | Update existing memory (when path exists)    |
-| drop_memory    | Delete memory                                |
-| clear_memory   | Clear all personal memory (irrecoverable)    |
-
-## Memory Lifecycle
-
-1. **Create (add)**: Use `add_memory` to create new memory
-2. **Read**: Agent can read existing memory during response generation
-3. **Update (replace)**: Use `replace_memory` to update memory content
-4. **Delete (drop)**: Use `drop_memory` to delete specific memory
-
-## Best Practices
-
-### 1. Path Naming Conventions
-
-- Use descriptive paths: `project/architecture`, `user/preferences/language`
-- Use `/` to organize hierarchy (this is the recommended usage), with guardrails:
-  - Absolute paths are forbidden (must not start with `/`)
-  - Path traversal is forbidden (`..` is not allowed)
-  - Avoid `\\` (cross-platform readability; prefer `/`)
-- Keep paths _flat_: prefer a small number of topic files rather than a deep directory tree.
-
-### 2. Content Format
-
-- Treat personal memory as a **carry-along stable-facts memo**: enable **0 ripgrep** startup within your scope.
-- Store stable facts only: **anchor points (file/symbol) + 1-line meaning + key contracts/priorities (≤3)**.
-- Fewer memory files is better: group facts that will be updated together into one file; avoid adding extra “directory-of-directory” layers.
-- Do not store task progress or daily state here:
-  - Team-visible progress belongs in Taskdoc `progress`
-  - Short-term working set belongs in reminders
-
-### 3. Usage Scenarios
-
-- **Task persistence**: Save long-term task progress
-- **Context memory**: Save important information from conversation context
-- **Preference settings**: Save user preferences and configuration information
-
-> Note: If you find yourself using personal memory to store “current progress of this run”, it likely belongs in Taskdoc `progress` or reminders instead.
-
-## Relationship with Other Tools
-
-- **team_memory**: Team shared memory, visible to all members
-- **reminder**: Temporary reminder, session-level
-- **change_mind**: Update taskdoc (goals/constraints/progress)
-
-## Limitations and Notes
-
-1. Memory content has size limit (max 1MB per memory)
-2. Memory path cannot exceed 255 characters
-3. `clear_memory` will delete all memory, **irrecoverable**

package/dist/tools/prompts/memory/en/scenarios.md

@@ -1,174 +0,0 @@
-# memory Usage Scenarios
-
-## Template (Scenarios)
-
-### Scenario Format
-
-- Goal
-- Preconditions
-- Steps
-- Expected Signal
-- Failure Branch
-- Completion Criteria
-
-## Scenario 1: Task Progress Tracking
-
-### Scenario Description
-
-In long-running tasks, you need to persist task progress to continue after restart.
-
-### Example
-
-**Add Task List**
-
-```typescript
-add_memory({
-  path: 'project/i18n-tasks',
-  content:
-    '## TODO\n\n- [ ] Create ws_mod manual\n- [ ] Create team_mgmt manual\n- [ ] Create memory manual\n- [ ] Create control manual\n\n## In Progress\n- [ ] Create ws_mod manual [100%]',
-});
-```
-
-**Update Task Progress**
-
-```typescript
-replace_memory({
-  path: 'project/i18n-tasks',
-  content:
-    '## TODO\n\n- [ ] Create team_mgmt manual\n- [ ] Create memory manual\n- [ ] Create control manual\n\n## Completed\n- [x] Create ws_mod manual\n\n## In Progress\n- [ ] Create team_mgmt manual [50%]',
-});
-```
-
-## Scenario 2: User Preferences Storage
-
-### Scenario Description
-
-Save user preferences, such as programming language, theme, etc.
-
-### Example
-
-**Save User Preferences**
-
-```typescript
-add_memory({
-  path: 'user/preferences',
-  content:
-    '## User Preferences\n\n- Programming Language: TypeScript\n- Code Style: strict\n- Theme: dark\n- Auto Save: true',
-});
-```
-
-**Update Preferences**
-
-```typescript
-replace_memory({
-  path: 'user/preferences',
-  content:
-    '## User Preferences\n\n- Programming Language: TypeScript\n- Code Style: strict\n- Theme: light\n- Auto Save: true',
-});
-```
-
-## Scenario 3: Context Information Preservation
-
-### Scenario Description
-
-In complex tasks, save important context information to avoid repeated queries.
-
-### Example
-
-**Save API Information**
-
-```typescript
-add_memory({
-  path: 'context/api-endpoints',
-  content:
-    '## API Endpoints\n\n- User Login: POST /api/auth/login\n- Get User Info: GET /api/user/info\n- Update User Settings: PUT /api/user/settings\n\n## Authentication\n- Use Bearer Token\n- Validity: 24 hours',
-});
-```
-
-**Save Tech Stack**
-
-```typescript
-add_memory({
-  path: 'context/tech-stack',
-  content:
-    '## Tech Stack\n\n- Frontend: React + TypeScript\n- Backend: Node.js + Express\n- Database: PostgreSQL\n- Cache: Redis',
-});
-```
-
-## Scenario 4: Meeting Notes
-
-### Scenario Description
-
-Save meeting highlights and decisions.
-
-### Example
-
-```typescript
-add_memory({
-  path: 'meeting/2024-01-15',
-  content:
-    '## Meeting Notes: 2024-01-15\n\n### Participants\n- @fullstack\n- @i18n\n- @ux\n\n### Agenda\n1. i18n manual creation plan\n2. man function UX improvements\n\n### Decisions\n- Prioritize creating ws_mod and team_mgmt manuals\n- man function supports fuzzy matching\n\n### TODO\n- @i18n: Create memory manual\n- @fullstack: Optimize man function',
-});
-```
-
-## Scenario 5: Knowledge Base
-
-### Scenario Description
-
-Build a personal knowledge base and save learning notes.
-
-### Example
-
-```typescript
-add_memory({
-  path: 'knowledge/typescript-tips',
-  content:
-    '## TypeScript Tips\n\n### 1. Type Inference\nconst x = 1; // Type inferred as number\n\n### 2. Interface vs Type\n- Interface: Extensible, suitable for object types\n- Type: Supports union types, intersection types\n\n### 3. Strict Mode\nEnabling strict mode provides better type safety',
-});
-```
-
-## Scenario 6: Temporary Notes
-
-### Scenario Description
-
-Temporarily save information to process later.
-
-### Example
-
-```typescript
-add_memory({
-  path: 'scratchpad/temp-notes',
-  content:
-    '## Temporary Notes\n\n- TODO: Check team.yaml configuration\n- TODO: Verify man function types\n- TODO: Update taskdoc progress',
-});
-```
-
-**Delete after processing**
-
-```typescript
-drop_memory({
-  path: 'scratchpad/temp-notes',
-});
-```
-
-## Scenario 7: Cleaning Up Outdated Memory
-
-### Scenario Description
-
-Regularly clean up memories that are no longer needed.
-
-### Example
-
-```typescript
-// View all current memories (agent can read)
-// Delete unnecessary memories one by one
-drop_memory({
-  path: 'project/old-feature',
-});
-```
-
-Or use `clear_memory` to clear all memories (use with caution):
-
-```typescript
-clear_memory({});
-```

package/dist/tools/prompts/memory/en/tools.md

@@ -1,129 +0,0 @@
-# memory Tool Reference
-
-## Template (Tools)
-
-### How to Read
-
-- The schema-generated "Tool Contract (Schema)" section is canonical for parameters/returns.
-
-### Per-Tool Fields (order)
-
-1. Purpose
-2. Call Signature
-3. Parameters (refer to schema)
-4. Preconditions
-5. Success Signal
-6. Failure/Errors
-7. Copy-Ready Example
-8. Common Misuse
-
-## Tool List
-
-### 1. add_memory
-
-Create new memory (when path does not exist).
-
-**Parameters:**
-
-- `path` (required): Unique identifier for the memory
-- `content` (required): Memory content
-
-**Returns:**
-
-- Success: a short plain-text message in the work language (e.g. `Added`).
-- Failure: a plain-text error message (often starts with `Error:`) with an actionable next step (e.g. use `replace_memory`).
-
-**Errors:**
-
-- `MEMORY_ALREADY_EXISTS`: Path already exists, use `replace_memory` to update
-
-### 2. replace_memory
-
-Update existing memory (when path exists).
-
-**Parameters:**
-
-- `path` (required): Unique identifier for the memory
-- `content` (required): New memory content
-
-**Returns:**
-
-- Success: a short plain-text message in the work language (e.g. `Updated`).
-- Failure: a plain-text error message (often starts with `Error:`) with an actionable next step (e.g. use `add_memory`).
-
-**Errors:**
-
-- `MEMORY_NOT_FOUND`: Path does not exist, use `add_memory` to create
-
-### 3. drop_memory
-
-Delete specified memory.
-
-**Parameters:**
-
-- `path` (required): Memory path to delete
-
-**Returns:**
-
-- Success: a short plain-text message in the work language (e.g. `Deleted`).
-- Failure: a plain-text error message (often starts with `Error:`).
-
-**Errors:**
-
-- `MEMORY_NOT_FOUND`: Path does not exist
-
-### 4. clear_memory
-
-Clear all personal memory.
-
-**Warning:** This operation is irreversible!
-
-**Parameters:** None
-
-**Returns:**
-
-- Success: a short plain-text message in the work language (e.g. `Cleared`). If there is nothing to clear, returns a message like `No personal memory to clear.`
-- Failure: a plain-text error message.
-
-**Errors:**
-
-- None (returns success even if no memories exist)
-
-## Usage Examples
-
-### Add New Memory
-
-```typescript
-add_memory({
-  path: 'project/todo',
-  content: '- Complete i18n docs\n- Write test cases\n- Update README',
-});
-```
-
-### Update Existing Memory
-
-```typescript
-replace_memory({
-  path: 'project/todo',
-  content: '- Complete i18n docs [DONE]\n- Write test cases [IN PROGRESS]\n- Update README',
-});
-```
-
-### Delete Memory
-
-```typescript
-drop_memory({
-  path: 'project/todo',
-});
-```
-
-### Clear All Memory
-
-```typescript
-clear_memory({});
-```
-
-## Output and Language
-
-- Output is **plain text**, not structured JSON/YAML.
-- The message language follows the current **work language**.