Project Memory
Use when a project spans many sessions. Docs that stay true.
Install
npx skills add SamueleBassoli/hermes-fleet-apps --skill project-memorygit clone --depth 1 https://github.com/SamueleBassoli/hermes-fleet-apps.git /tmp/hermes-fleet-apps
mkdir -p ~/.claude/skills
cp -r /tmp/hermes-fleet-apps/roles/coder/skills/project-memory ~/.claude/skills/project-memoryPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Project Memory For projects that run across many sessions with the context deliberately reset each time. The repo itself has to carry the memory: `handoff` moves one session to the next, this skill keeps a project true to itself for months. The failure this prevents: a fresh session opens a page, believes it, and builds on a claim that stopped being true three sessions ago. ## The three-file split — one fact, one home ``` _private/wiki/ what the project IS shape, settled decisions, measured numbers _private/ROADMAP.md what is LEFT ordered phases, small steps, ticks _private/wiki/log.md what HAPPENED dated, append-only ``` The split is the whole point. Development steps in the wiki, or architecture in the roadmap, means one fact lives in two files — and two copies drift. **State the precedence, not only the split.** The log is dated history: its entries describe what was true on their date, not what is true now, so where it disagrees with the roadmap or a concept page, those win and the log stays as written. Put that beside the read order in `AGENTS.md` — a fresh session sent to read the last 20 log entries will otherwise treat the newest one it finds as current state. **When content moves between these files, leave a pointer, never a copy.** "The plan lives in ROADMAP.md, currently Phase 1" — not a restated step list. Keep the roadmap out of the wiki proper: no wiki frontmatter, not in the wiki index, not
Details
- Skill name
project-memory- Repository
- SamueleBassoli/hermes-fleet-apps
- Path
roles/coder/skills/project-memory/SKILL.md- License
- MIT
- Repo updated
- 31 October 2026
FAQ
What does the Project Memory skill do?
Use when a project spans many sessions. Docs that stay true.
How do I install the Project Memory skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add SamueleBassoli/hermes-fleet-apps --skill project-memory. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Project Memory popular?
It lives in SamueleBassoli/hermes-fleet-apps, which has 44 GitHub stars and 0 forks.
Related skills
Agent Facing CLI
44SamueleBassoli/hermes-fleet-apps
Use when an agent will drive a CLI. Contract test first.
Agent Fleet Design
44SamueleBassoli/hermes-fleet-apps
Use when adding, backing up, or driving the agent fleet.
Agent Identity Setup
44SamueleBassoli/hermes-fleet-apps
Use when setting up or resetting agent SOUL, memory, skills.
Resend Integration Skills
23gocallum/nextjs16-agent-skills
Integrate Resend email service via MCP protocol for AI agents to send emails with Claude Desktop, GitHub Copilot, and Cursor. Set up transactional and marketing emails, configure sender verification, and use AI to automate email workflows.
PRD Mastery: Context Aware, Expert Driven, and Token Efficient Refinement
23gocallum/nextjs16-agent-skills
A skill that blends the wisdom of top industry experts, ensures token-efficient PRDs, and organizes outputs in a clear folder structure.
Creator Productivity
48frankxai/claude-skills-library
Task management and workspace memory for creative work sessions. Manages a TASKS.md file for project tracking, a two-tier memory system (CREATOR.md + creator-memory/), and a daily sprint structure. Use when organizing creative projects, tracking content tasks, or starting a focused work session.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.