mem-forever

Solid

Every AI tool forgets you. This one doesn't. Ever. Auto-generates your profile from conversation, saves decisions and lessons, applies your preferences across every session. Works with Claude Code, Cursor, Codex, Copilot, Gemini CLI. Use this skill at session start to load memory, and throughout the session to save new observations.

AI & Automation 2 stars 0 forks Updated today MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%

Recency 20%

100

Frontmatter 20%

Documentation 15%

100

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

# mem-forever ::GENE{mem-forever|v:1.0|spec:ilang-v3.0} T:this_repo_is_user_memory T:read_soul_and_memory_before_work T:update_memory_after_significant_work T:onboard_if_soul_empty T:one_question_at_a_time T:never_expose_internal_format T:commit_push_immediately_after_every_update T:check_unsaved_changes_on_startup A:skip_memory_read⇒context_loss A:overwrite_memory⇒append_or_merge A:ask_multiple_questions⇒one_only A:batch_saves_to_session_end⇒commit_each_update ## Session Start 1. Check for uncommitted changes in `.ilang/`. If found → commit and push immediately. These are unsaved memories from a previous session. 2. Read `.ilang/soul.md`. If empty or only template → run onboarding (see below). 3. Read `.ilang/memory.md`. Resume context from last session. 4. Do whatever the user asks. Apply preferences from soul.md to all output. ## Onboarding (soul.md empty) ::ACTIVATE{onboarding|if:.ilang/soul.md=template_only} Open casually: "Hey, before we start — mind if I ask a couple things so I can work the way you like?" Ask ONE question per message. Wait for answer. Cover naturally: - What they do / build - How they prefer to work (plan-first vs build-first, detail vs minimal) - What AI tools they use - Any strong preferences (language, framework, style) Completion: write `.ilang/soul.md` when you have role + work style + one clear preference. Don't wait for perfection. Fill gaps later from observed behavior. Say: "Saved some notes so things go smoot...

Details

Author: Whistlegenusvincetoxicum446
Repository: Whistlegenusvincetoxicum446/Mem-Forever
Created: 2 months ago
Last Updated: today
Language: N/A
License: MIT

Integrates with

Next.js · Frontend

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

memesh

Use MeMesh to remember, recall, and manage AI knowledge across sessions. Triggers when the user asks to remember something, recall past decisions, forget outdated info, learn from mistakes, or analyze work patterns. Also triggers proactively when you make important decisions, fix bugs, or learn lessons worth preserving.

14 Updated yesterday

PCIRCLE-AI

AI & Automation Solid

memory-manager

Standardized workflow for discovering, reading, writing, and compacting the project's memory file (memory.instructions.md) to persist context across AI chat sessions, with a permanent Knowledge Base for cross-session decisions and lessons learned.

41 Updated today

GulajavaMinistudio

AI & Automation Listed

bettermemory

Verification-grade memory between sessions. Use bettermemory's MCP tools (memory_search, memory_show, memory_write, memory_verify, memory_record_use, etc.) instead of writing to files when the user asks you to "remember" something or references shared context from a past session. Default is to NOT call memory_search; only retrieve when the user references context you don't have ("my project", "the script we wrote") or a request is ambiguous in a way stored preferences could resolve. Every hit carries a staleness_verdict (calendar + path-drift + commit-drift); when it isn't "fresh", spot-check a claim before relying and call memory_verify to attest. Every use should record a claim_excerpt so retrievals stay auditable.

0 Updated today

0Mattias