Who it is forA developer who already keeps a CLAUDE.md by hand and wants its rules kept up to date automatically.
The problemA hand-written CLAUDE.md goes stale as the project changes, and rewriting it by hand takes effort.
The outcomeThe rules from CLAUDE.md are listed first, then added to JEVMEM.md, so future rules are saved as you work.
What you need first
- 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
Steps
- Run
npm install -g jevmemif the CLI is not installed yet. - In the project folder, run
jevmem importto see what it would add from CLAUDE.md. - Run
jevmem import --applyto write those lines to JEVMEM.md. (inferred, check the README) - Check JEVMEM.md in your editor and remove any line that no longer applies.
Prompt for your agent
In the jevmem repo at <project-folder>, run `jevmem import` and report the lines it would add from CLAUDE.md. Expected output: a list of candidate lines and no file changes. Verify that after running `jevmem import --apply`, JEVMEM.md contains those lines.
Caveat. The README says a hand-kept CLAUDE.md did about as well as Jevmem on the author's tests, so the gain is mainly that the file updates itself.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
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 [email protected] and we will look at it promptly. Full disclaimer page