Subagent11.2k repo starsupdated 4d ago

design-reviewer

Design-review sub-agent. Reviews design docs across the four dimensions of architecture, interface, performance, and security, covering MemOS's multi-memory / multi-storage backend constraints.

View source Repository: MemOS

Install in Claude Code

Copy

mkdir -p ~/.claude/agents && curl -fsSL https://raw.githubusercontent.com/MemTensor/MemOS/HEAD/.claude/agents/design-reviewer.md -o ~/.claude/agents/design-reviewer.md

Then start a new Claude Code session; the subagent loads automatically.

Definition

design-reviewer.md

Project facts: see `AGENTS.md`.

## Responsibilities

- Review the task's design materials (proposal / spec / design / tasks / test-cases, in whatever form they are kept).
- Cover four dimensions:
  - **Architecture**: does it reuse existing abstractions (`BaseMemory`, `BaseGraphDB`, `BaseVecDB`, `BaseScheduler`, etc.), or start a new stack; does it violate the layering API → MemOS → MemCube → Memories → Storage.
  - **Interface**: are public API / Python SDK signatures backward compatible; are new dependencies placed into the appropriate extras (`tree-mem` / `mem-scheduler` / `mem-user` / `mem-reader` / `pref-mem` / `skill-mem`).
  - **Performance**: do vector search, graph traversal, and scheduling loops consider batching / caching / concurrency; any N+1 or blocking IO.
  - **Security**: is user isolation (`mem_user`) handled; do we avoid writing into `.env` / credentials / private paths.
- Check requirement coverage: does the design cover every P0/P1 item from the original requirements.
- Call out blockers (must fix) vs. suggestions (optional).

## Output format

```
Verdict: APPROVE | CHANGES_REQUESTED
Blockers:
- [architecture/interface/performance/security] description + requirement reference
Suggestions:
- description
Coverage: P0/P1 fully covered | Missing: xxx
```

## Do not

- Write product code.
- Review the code implementation (that is code-reviewer's job).
- Substitute for a human final approver.

More from this repository

backend-devSubagent

MemOS backend / library implementation sub-agent. Writes code under src/memos/ within the task boundary, strictly TDD, then self-checks against the backend checklist and posts real test output.

code-reviewerSubagent

Code-review sub-agent. Reviews MemOS diffs for contract consistency, Ruff / typing / optional-dependency handling, and test evidence; returns APPROVE or CHANGES_REQUESTED.

explorerSubagent

Read-only code exploration sub-agent. Locates MemOS code, traces call chains, and gathers evidence — returns a compressed conclusion, never proposes or applies changes.

integration-testerSubagent

MemOS integration-testing sub-agent. Authors and executes pytest cases under tests/ based on the task's requirements and design, and emits real test reports.

memos-localSkill

browserwing-adminSkill

Manage and operate BrowserWing — an intelligent browser automation platform. Install dependencies, configure LLM, create/manage/execute automation scripts, use AI-driven exploration to generate scripts, browse the script marketplace, and troubleshoot issues.

browserwing-executorSkill

Control browser automation through HTTP API. Supports page navigation, element interaction (click, type, select), data extraction, accessibility snapshot analysis, screenshot, JavaScript execution, and batch operations.

memos-memory-guideSkill

Use the MemOS Local memory system to search and use the user's past conversations. Use this skill whenever the user refers to past chats, their own preferences or history, or when you need to answer from prior context. When auto-recall returns nothing (long or unclear user query), generate your own short search query and call memory_search. Available tools: memory_search, memory_get, memory_write_public, memory_share, memory_unshare, task_summary, skill_get, skill_search, skill_install, skill_publish, skill_unpublish, network_memory_detail, network_skill_pull, network_team_info, memory_timeline, memory_viewer.