skills.rest
Prompt-or-Die-Labs
Prompt-or-Die-LabsOFFICIAL
Explore all skills by this author →
GitHub

create-memory

Create structured markdown memory files recording project learnings and decisions.

7|2|Updated Nov 9, 2025
Search Tags:#architecture#markdown#memory#traceability#project documentation#decision log#workflow standards
One-click install
npx skills add https://github.com/Prompt-or-Die-Labs/hyper-forge --skill create-memory-prompt-or-die-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-memory
Source: https://github.com/Prompt-or-Die-Labs/hyper-forge/tree/main/.claude/skills/create-memory
Command: npx skills add https://github.com/Prompt-or-Die-Labs/hyper-forge --skill create-memory-prompt-or-die-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents important project knowledge from being lost by creating structured memory notes that record learnings, decisions, and system changes for the team over time.

Core Features & Use Cases

  • Memory file creation and maintenance: Create new memory markdown files with consistent structure, or update existing ones when patterns evolve.
  • Decision traceability: Document major architectural and workflow decisions so future work can reference the why, not just the what.
  • Operational guidance for future runs: Link the memory to affected files and related skills/commands to reduce repeated investigation.

Quick Start

Ask an AI assistant to create a new memory file for an important topic, with the current date and marked status.

Frequently Asked Questions about create-memory

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

FAQPage Schema
How do I create project documentation for architecture decisions and learnings?▼

You create persistent memory files using a consistent markdown template under .claude/memory/ that records status, date, purpose, implementation details, pitfalls, and related commands. This captures important learnings, architectural decisions, and system changes for future team reuse.

What's the best way to maintain decision traceability in a software repository?▼

Maintaining decision traceability involves writing structured markdown notes that document major architectural choices and workflow standards. By linking memory files to affected project files and related commands, teams can reference the why behind decisions rather than just the what.

When do I need to record system changes and project patterns in memory files?▼

You should record system changes and project patterns when implementing major features, making architecture choices, discovering project patterns, or resolving complex bugs. Creating memory files at these moments prevents important learnings and decisions from being lost over time.

Can I update existing memory markdown files when workflow standards evolve?▼

Yes, you can update existing memory markdown files when project patterns and workflow standards evolve. Maintaining these structured notes ensures operational guidance remains accurate and reflects the latest architectural decisions and system changes for future runs.

Does creating a memory decision log require any specific dependencies?▼

Creating a memory decision log requires no external dependencies. It relies solely on generating structured markdown files within your software repository under .claude/memory/ to capture learnings, ensuring future work can reference architectural choices and workflow standards.

Related Skills

Explore More Software Engineering Skills→
SpillwaveSolutionsSpillwaveSolutions
46

project-memory

Initialize and maintain project memory files under docs/project_notes.

Official
Basic
DexploarerDexploarer
7

create-memory

Create structured Markdown memory files under .claude/memory/ with a fixed template.

Community
Basic
hungson175hungson175
3

Project Memory Store

Store project-specific insights into file-based episodic, procedural, and semantic memory.

Community
Intermediate
erikliebeneriklieben
7

meta-wrap-up

Review git changes, update daily memory logs, and identify documentation gaps.

Community
Advanced