{
 "schema_version": 1,
 "generated": "2026-10-20",
 "id": "avinash-jetwani-jevmem--share-project-memory-with-team-through-git",
 "repo": "Avinash-jetwani/jevmem",
 "repo_url": "https://github.com/Avinash-jetwani/jevmem",
 "repo_slug": "avinash-jetwani-jevmem",
 "title": "Share project decisions with your team through git",
 "page_title": "How to share project decisions with your team through git with Jevmem",
 "summary": "Commit JEVMEM.md so every teammate's agent gets the same saved decisions and rules.",
 "who": "A tech lead or team member whose colleagues each run Claude Code on the same repo and keep getting different answers.",
 "problem": "Decisions made in one person's chat stay in that chat, so teammates' agents do not know them.",
 "outcome": "JEVMEM.md is versioned in the repo, and each teammate's Claude Code session reads the same saved lines after a pull.",
 "steps": [
  "Run `jevmem setup` in the project folder once.",
  "Commit JEVMEM.md with your other project files.",
  "Ask teammates to run `npm install -g jevmem` and `jevmem setup` in their own clone.",
  "Pull the repo so each teammate has the current JEVMEM.md before starting a session."
 ],
 "agent_prompt": "In the jevmem-enabled repo at <project-folder>, confirm that JEVMEM.md is tracked by git with `git ls-files JEVMEM.md`. Expected output: the file name printed once. Verify after a teammate pulls that their Claude Code session receives the saved lines on their next prompt.",
 "agents": [
  "claude-code"
 ],
 "difficulty": "Intermediate",
 "time": "30 minutes",
 "basis": "readme",
 "caveat": "Each teammate still needs their own TypeSafe API key and the Jevmem CLI installed, because requests are billed to the key.",
 "category": "Software and DevOps",
 "tags": [
  "Software and DevOps"
 ],
 "lang": "typescript",
 "requirements": [
  "A TypeSafe API key from https://console.typesafe.ai/keys, which jevmem's requests are billed to",
  "Claude Code 2.1.273 or later",
  "npm, to install the jevmem CLI that the plugin runs",
  "A project folder in a git repo, so JEVMEM.md can be committed and shared"
 ],
 "risk": "none",
 "seen_in_the_wild": false,
 "mentioned_publicly": false,
 "risks": [],
 "best": false,
 "score": 0.8,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/avinash-jetwani-jevmem/share-project-memory-with-team-through-git/",
 "md": "https://dedupedai.com/use-cases/avinash-jetwani-jevmem/share-project-memory-with-team-through-git/index.md",
 "disclaimer": "Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked \"Seen in the wild\", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email hello@dedupedai.com and we will look at it promptly.",
 "api": "https://dedupedai.com/api/v1/usecases/avinash-jetwani-jevmem--share-project-memory-with-team-through-git.json",
 "api_version": "v1"
}
