skills.rest
giang6283623
giang6283623COMMUNITY
Explore all skills by this author →
GitHub

memento

Maintain persistent project context across AI coding sessions via MEMENTO.md.

4|Updated Jun 24, 2026
Search Tags:#workflow#documentation#productivity#memory#persistence#session
One-click install
npx skills add https://github.com/giang6283623/minimal-vibe-coding-kit --skill memento-giang6283623
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: memento
Source: https://github.com/giang6283623/minimal-vibe-coding-kit/tree/main/.cursor/skills/memento
Command: npx skills add https://github.com/giang6283623/minimal-vibe-coding-kit --skill memento-giang6283623

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of context loss during multi-day coding tasks by providing a structured, persistent memory mechanism that survives session gaps.

Core Features & Use Cases

  • Session Continuity: Maintains a MEMENTO.md file to track goals, milestones, blockers, and traps across different work sessions.
  • Context Preservation: Ensures that critical project knowledge, such as dead ends and next steps, is explicitly documented rather than lost when an AI agent is reset.
  • Use Case: When working on a complex feature that spans several days, use this skill to summarize your progress and blockers before closing your IDE, ensuring you can resume exactly where you left off the next day.

Quick Start

Invoke the memento skill to wrap up your current session and save your progress to the repository root.

Frequently Asked Questions about memento

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain AI coding session context across multiple days?▼

To maintain session context, use a centralized MEMENTO.md file at the repository root to store goals, milestones, blockers, and next steps, ensuring progress documentation survives across multi-day development workflows.

What is the best way to save progress and blockers before closing my IDE?▼

The best way to save progress is invoking a session wrap-up that summarizes current blockers and milestones into a MEMENTO.md file, allowing you to resume exactly where you left off the next day.

Do I need a specific file structure to track long-term development workflows?▼

Yes, long-term workflow tracking requires a MEMENTO.md file present at the repository root to store and retrieve session-specific state information for your project.

Can I preserve critical project knowledge when an AI agent is reset?▼

Yes, you can preserve critical project knowledge when an AI agent is reset by explicitly documenting dead ends, traps, and next steps into a persistent MEMENTO.md file rather than losing them.

What are the limitations of using a markdown file for persistent project memory?▼

A limitation of using a markdown file for persistent memory is that the MEMENTO.md file must exist at the repository root, and you must manually wrap up your session to save progress.

Related Skills

Explore More Software Engineering Skills→
jinglemansweepjinglemansweep

jp-setup

Create a .plans directory with a .gitkeep file at the repository root.

Community
Basic
drvossdrvoss
42

cross-session-memory

Resume past Copilot CLI sessions and retrieve prior context from SQLite.

Community
Intermediate
swarm-ai-safetyswarm-ai-safety
39

session-close

Summarize session changes, update memory logs, and commit code with Git.

Official
Intermediate
jonnymuirjonnymuir
1

nap

Compress agent history files and prune stale logs in the .squad/ directory.

Community
Basic