Skip to content

v1.3.0 — RAM, Multi-Session Memory, Git Push Directive, Zero Sycophancy

Choose a tag to compare

@superbasicstudio superbasicstudio released this 20 Feb 20:53
· 4 commits to main since this release

What's New

New Template: _RAM.md — Single-Session Volatile Memory

Like actual RAM in a computer. Holds the exact working state of the current session so that if the session is killed, context overflows, or work is interrupted, the next session can recover exactly where it left off.

  • Written to continuously throughout the session
  • Overwritten (not appended) — always reflects current state
  • Deleted at session end when work is committed/saved
  • Includes recovery checklist and template structure

Redefined: _SHORT-TERM-MEMORY.md — Multi-Session Context

Previously handled single-session crash recovery (now handled by _RAM.md). Redefined as multi-session temporary memory that persists across 4-10 sessions:

  • Active issues being debugged or improved
  • In-progress feature work spanning multiple sessions
  • Temporary decisions and cross-session context
  • Includes staleness rule: review entries older than 2 weeks

Three-Tier Memory Hierarchy

_RAM.md                    _SHORT-TERM-MEMORY.md       _LONG-TERM-MEMORY.md
 - Single session only      - Persists 4-10 sessions    - NEVER delete
 - Crash recovery           - Active issues & work       - Permanent knowledge
 - Written continuously     - Updated between sessions   - Accumulates over time
 - Deleted at session end   - Deleted when resolved      - Always available

New Golden Rules

Rule #5: Suggest Pushing After Major Fixes
After resolving significant bugs or completing iterated-on improvements, Claude suggests committing and pushing to the user's backup system (git, Gitea, GitHub, etc.). Suggest only — never auto-push.

Rule #6: Maintain _RAM.md Continuously
Claude must write session state to _RAM.md throughout every working session. Create when work begins, update after every meaningful action, write before risky operations.

Zero Sycophancy Rule (_VOICE-AND-TONE.md)

New core principle: every token spent flattering the user is a token NOT spent writing correct code. No "sick idea," no "brilliant," no "game-changing." Substance only.

  • Expanded Words & Phrases to AVOID with comprehensive ban list organized into categories
  • Core principles: never praise ideas, never editorialize about quality, spend 100% of output on substance

Updated Session Load Order

0. _RAM.md                       ← IF EXISTS: recover interrupted session
1. _SHORT-TERM-MEMORY.md         ← IF EXISTS: multi-session context
2. _VOICE-AND-TONE.md            ← Personality and language style
3-10. [rest of chain]
11. BEGIN conversation

Stats

  • 11 templates (up from 10)
  • 10 tests passing
  • Zero PII — all templates use generic placeholders

Full Changelog: v1.2.0...v1.3.0