memory

Manage knowledge as structured markdown files in a filesystem.

1|1|Updated Jan 18, 2025
One-click install
npx skills add https://github.com/Project-X-Vietnam/landing-page --skill memory-project-x-vietnam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory
Source: https://github.com/Project-X-Vietnam/landing-page/tree/main/.claude/skills/memory
Command: npx skills add https://github.com/Project-X-Vietnam/landing-page --skill memory-project-x-vietnam

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured way to manage and retrieve knowledge directly within your filesystem, treating source code as the single source of truth for decisions, patterns, and context.

Core Features & Use Cases

  • Decision Recording: Document architectural choices and their justifications.
  • Pattern Documentation: Capture and store recurring development patterns.
  • Contextual Notes: Save the reasoning behind specific implementations.
  • Use Case: When making a significant architectural decision, use the 'Remember' operation to store the decision, the context, and the technical details in a markdown file within the docs/technical/ directory.

Quick Start

Use the memory skill to remember a new architectural decision by providing the topic title and details.

Frequently Asked Questions about memory

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

FAQPage Schema
How do I manage technical documentation and knowledge directly in the filesystem?

Filesystem knowledge management stores technical, feature, and API documentation as structured markdown files, enabling you to record decisions, patterns, and context for easy retrieval.

What's the best way to record architectural decisions in markdown?

Recording architectural decisions in markdown involves saving the choice, context, and technical justification as a structured file in a technical documentation directory.

How do I store recurring development patterns for future reference?

Storing recurring development patterns requires capturing implementation logic in structured markdown files, allowing future retrieval to maintain consistency across technical projects.

Can I use filesystem directories to organize API documentation?

Yes, you can organize API documentation by saving structured markdown files into dedicated documentation directories to maintain context and technical reasoning.

How does markdown knowledge management work without a database?

Markdown knowledge management works by treating the filesystem as the source of truth, using structured markdown files to store and retrieve decisions and context without external databases.