Workspace
Save project-specific memories to the local .mematrix/ directory. Use when user invokes /mematrix:workspace, or asks to "save project context", "remember this for the project", "workspace memory", "save project notes", or wants to persist project architecture, conventions, or setup info alongside the code.From its SKILL.md
npx -y skills add themarchrain/mematrix --skill workspaceAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
3 things to look at
- 27 days oldThe repository was created 27 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.4 KB, 461 tokens by cl100k_base, as published. Nobody here has run it
Mematrix Workspace — Project-level memory
Capture project-specific context into .mematrix/ in the project root.
These memories live with the code — separate from personal user memories.
What goes here vs user-level
Store in .mematrix/ (workspace) | Store in ~/.mematrix/ (remember) |
|---|---|
| Architecture decisions & rationale | Personal tech stack & skills |
| Project-specific conventions | Communication preferences |
| Setup quirks & environment details | Life context & schedule |
| Troubleshooting notes for this project | Cross-project patterns & learnings |
| Code patterns unique to this codebase | General preferences |
Workspace memories are project-scoped facts. They should NOT contain personal user information.
Procedure
1. Scan the conversation
Review the current conversation for project-relevant information worth persisting:
- Architecture decisions and why they were made
- Project-specific conventions (naming, patterns, structure)
- Environment setup, dependencies, build quirks
- Bugs encountered and their solutions (specific to this codebase)
- Design patterns used and rationale
2. Create directory
Create .mematrix/ in the current project root if it doesn't exist.
3. Write memories
Use descriptive filenames. Choose based on what's being captured:
| File | When to use |
|---|---|
architecture.md | Architecture decisions, patterns, why things are structured this way |
conventions.md | Naming, code style, patterns specific to this project |
setup.md | Environment, dependencies, build/run commands, quirks |
troubleshooting.md | Bugs encountered and how they were fixed |
project-context.md | For smaller projects — put everything in one file |
4. Dedup
Apply the same dedup strategy as remember:
- High similarity → SKIP
- Related but adds detail → MERGE
- New → WRITE
- Uncertain → WRITE (conservative)
5. Note
Workspace memories are automatically included in future /mematrix:recall
operations when the working directory is this project. The recall skill
reads .mematrix/*.md as part of its default scope.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.