nimarsagi

Personal Claude Assistant Template — Development skill for Claude Code

Development community

Give Claude Code a memory that learns.

How to install Personal Claude Assistant Template

This entry records only its repository, not the path inside it, so there is no exact command to give. Open nimarsagi/Personal-Claude-Assistant-Template and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Personal Claude Assistant Template does

Give Claude Code a memory that learns. Every session boots knowing who you are; your work gets journaled, corrections become standing rules, hard-won solutions become reusable skills, and a weekly gardener keeps it all tidy. Nothing saved without your yes — plain markdown you own, versioned with git.

Alternatives in Development

/diagnose — Vérifie l'état de l'environnement RTK et suggère des corrections 25.5k ★
Cashclaw — An autonomous agent that takes work, does work, gets paid, and gets better at it 973 ★
AgentHandover — What if OpenClaw, Claude Code, Codex etc. knew how to do your work without you saying it 600 ★

README

personal-claude-assistant-template

**My Claude Assistant** is a memory for Claude Code that you approve, prune, and carry between projects.

Claude Code already keeps notes of its own, under `~/.claude/projects//memory/`. Those are keyed to the directory you opened — start the same project one folder deeper and it's a different memory — they get written without asking you, and they accumulate with no pass that clears out what has gone stale.

This is the other kind, and it differs on exactly those points. It loads in every session in every folder, so what Claude knows about you doesn't depend on where you started it. Nothing enters it without your explicit yes: background work runs freely but only ever produces drafts and offers, and the moment something would be written it stops and asks. What does get in is filed to the narrowest home that fits — a fact about you, a rule for one area of your work, a convention belonging to one project — and a weekly pass proposes what to prune, merge, or promote, because the files that load at boot have hard size caps. The whole thing is a git repo you own, so every change to your own memory has a diff and a way back. Where the two disagree about something, this one wins and says so.

It also learns rather than just recording. A correction becomes a standing rule; a problem you've now solved the hard way twice becomes a skill.

Additionally, the memory is stored locally, so that it becomes easy to switch vendors.

Install

The clone IS the install: this checkout becomes the live assistant, and git versions your memory over time. Your copy will hold personal data, so it must stay private.

Do NOT fork this repo on GitHub. Forks of public repos are public and can never be made private — your interview answers and journal would end up on the open internet. Clone locally instead.
Optional but recommended — off-machine backup: local commits don't survive a dead disk. Create your own empty PRIVATE repo