maz-works-knowledge-vault / rules
Cursor rule0 starsChanged 3 months agoMITView on GitHub
Maz Works Knowledge Vault — cross-project memory and Obsidian knowledge workflows.
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,144 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- autoresearchSkill
- canvasSkill
- defuddleSkill
- obsidian-basesSkill
- obsidian-markdownSkill
- saveSkill
- thinkSkill
- wiki-cliSkill
- wiki-foldSkill
- wiki-ingestSkill
- wiki-lintSkill
- wiki-modeSkill
- wiki-querySkill
- wiki-retrieveSkill
- wikiSkill
The file
We split this maz-works-knowledge-vault.mdc into the rules it gives an agent
7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Read the relevant wiki/projects/{project}/ context first.
- Very specific: line 17
Use wiki/hot.md for recent cross-project context.
- Very specific: line 18
Treat .raw/ as immutable source material.
- Distinctive: line 19
Use Obsidian wikilinks for internal knowledge links.
- Very specific: line 20
Keep wiki/log.md append-only and refresh wiki/hot.md at session end.
- Very specific: line 21
Read a selected skill's complete skills/<name>/SKILL.md before applying it.
- Distinctive: line 22
Never store credentials, private client information, or private spiritual content.
≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
---
description: Maz Works Knowledge Vault — cross-project memory and Obsidian knowledge workflows.
globs:
- "wiki/**/*.md"
- ".raw/**/*"
- "skills/**/SKILL.md"
alwaysApply: true
---
# Maz Works Knowledge Vault
This is Manazir Hussain's shared knowledge system for Maz Works projects, client work, research, experiments, and agent handoffs.
## Work from shared truth
- Read the relevant `wiki/projects/{project}/` context first.
- Use `wiki/hot.md` for recent cross-project context.
- Treat `.raw/` as immutable source material.
- Use Obsidian wikilinks for internal knowledge links.
- Keep `wiki/log.md` append-only and refresh `wiki/hot.md` at session end.
- Read a selected skill's complete `skills/<name>/SKILL.md` before applying it.
- Never store credentials, private client information, or private spiritual content.
The canonical repository is <https://github.com/manazoid4/maz-works-knowledge-vault>. Upstream provenance is documented in `ATTRIBUTION.md`.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.