create-memory

Store architecture decisions and debugging notes into Gemini's knowledge base.

4|Updated Aug 22, 2023
One-click install
npx skills add https://github.com/Lira-tron/dotfiles --skill create-memory-lira-tron
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-memory
Source: https://github.com/Lira-tron/dotfiles/tree/main/home/.gemini/skills/create-memory
Command: npx skills add https://github.com/Lira-tron/dotfiles --skill create-memory-lira-tron

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stores essential context, decisions, and learnings into Gemini's knowledge base for future reference.

Core Features & Use Cases

  • Stores architecture decisions, debugging notes, and implementation details during active work sessions.
  • Automatically organizes entries by project and time, enabling cross-workspace search.

Quick Start

Use the create-memory skill to store a note about a recent design decision.

Frequently Asked Questions about create-memory

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

FAQPage Schema
How do I store architecture decisions and debugging notes in Gemini's knowledge base?

You can store architecture decisions in Gemini's knowledge base by capturing essential context during active work sessions, which automatically indexes entries under ~/.gemini/knowledge/memory for future reference.

What is the best way to retain implementation details across different workspaces?

Retaining implementation details across workspaces is achieved by saving learnings into a centralized knowledge base that automatically organizes entries by project and time for cross-workspace search.

Do I need external setup to save notes and learnings into Gemini's memory?

No external setup is required to save learnings into Gemini's memory beyond the standard Gemini memory integration, allowing you to immediately capture notes when they arise.

How does automatic indexing work for project notes and decisions?

Automatic indexing for project notes works by storing entries directly into the local knowledge base directory at ~/.gemini/knowledge/memory, organizing them by project and time for retrieval.

When do I need to save context to a knowledge base during a work session?

You need to save context to a knowledge base when architecture decisions, debugging notes, or implementation details arise during active work sessions, preserving learnings for future reference.