agentleFS
IgorGanapolskyIgorGanapolsky/mac-yolo-safeguards/.cursor/rules/obsidian-teammate-collaboration.mdc

mac-yolo-safeguards / rules

Cursor rule3 starsChanged 3 days agoMITView on GitHub

Teammates collaborate via the shared AI-Agent-Sync Obsidian vault across all projects

The file

We split this obsidian-teammate-collaboration.mdc into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    User directive: All teammates from multiple projects collaborate on one shared Obsidian vault.

    line 8
  2. Very specific:

    Refresh: After major plan.md changes in mac-yolo-safeguards, run node tools/agent-sync-brief.js --vault ~/Documents/AI-Agent-Sync.

    line 14

≈ “Common” is an estimate: at least 1 in 5 of the 6,809 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
obsidian-teammate-collaboration.mdc
---
description: Teammates collaborate via the shared AI-Agent-Sync Obsidian vault across all projects
alwaysApply: true
---

# Obsidian teammate collaboration

**User directive:** All teammates from multiple projects collaborate on **one shared Obsidian vault**.

- **Canonical vault:** `~/Documents/AI-Agent-Sync` (`IgorGanapolsky/AI-Agent-Sync`) — git pull/push, not Obsidian Sync.
- **Cross-project index:** `Projects/README.md` in the vault lists all projects and links to each repo's `plan.md`.
- **Per-repo ownership:** `plan.md` stays in each project repo; vault holds people, handoffs, decisions, and `Project-Reports/`.
- **Onboarding:** GitHub repo access → clone vault → `bash ~/Documents/AI-Agent-Sync/scripts/bootstrap_central_vault.sh` → open vault in Obsidian.
- **Refresh:** After major `plan.md` changes in mac-yolo-safeguards, run `node tools/agent-sync-brief.js --vault ~/Documents/AI-Agent-Sync`.

Detail: [OBSIDIAN.md](../../OBSIDIAN.md), vault [ORGANIZATIONAL_MEMORY.md](file:///Users/igorganapolsky/Documents/AI-Agent-Sync/ORGANIZATIONAL_MEMORY.md).

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.