agentleFS
Sign inStart free
me-cedricme-cedric/agent-compass/skills/project-memory/SKILL.md

project-memory

Skill3 starsChanged 27 days agoMITView on GitHub

Read and write durable project memory with projectmem. Use before non-trivial work, and after a decision, a failed attempt, a fix or a finding.

24 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never commit a projection.

    line 25
  2. Very specific:

    Write a committed ADR in {{ADR_DIR}} for each durable architecture decision.

    line 45
  3. Very specific:

    If projectmem is not available, continue the task.

    line 53

“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “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
SKILL.md

project-memory

Before work

pjm regenerate   # after a pull or merge: fold the shared events of teammates into the log
pjm brief
pjm precheck

For a non-trivial task, also search the memory for the files, modules, libraries and errors that the task touches.

Shared and local

events.jsonl is the committed source of truth. It merges as a union. The projections (summary.md, PROJECT_MAP.md, AI_INSTRUCTIONS.md, issues/) are git-ignored. pjm regenerate rebuilds them. Never commit a projection. A committed summary overwrites the work of teammates.

During work

Log each of these when it happens:

  • A failed attempt.
  • An important finding.
  • A fragile file or a risky area.
  • A library or tooling gotcha that other people can reuse.

After work

Log these items:

  • Decisions and fixes.
  • Files changed.
  • Validation commands and their results.
  • Remaining risks.

Write a committed ADR in {{ADR_DIR}} for each durable architecture decision. Use the skill adr. One file for each decision merges cleanly.

Never log

  • Secrets, tokens or credentials.
  • Personal data or raw customer data.
  • Temporary brainstorming.

If projectmem is not available, continue the task. Report memory logging as not run, with the reason.

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.

Check your setup, free