letter-for-my-future-self-marketplace

Letter to Myself

A Claude Code plugin for context persistence between sessions.

When sessions end, chats get compacted, or days pass between work blocks, Claude forgets everything. This plugin solves that by writing structured "handoff letters" to a local .memory/ folder that Claude reads on startup.

Result: Less re-explaining, fewer repeated mistakes, smoother "back into flow" experience.

---

Features

Core: Session Memory

Save structured session summaries with a single command:

• What we did (high-signal summary)
• Why we did it (decisions + reasoning)
• Pain Log (critical errors, root causes, workarounds)
• State that matters (variables, constraints, risks)
• Next steps (actionable, ranked)

Letter to Blog Pipeline

Automatically transform session memories into public-ready blog posts via GitHub Actions + Claude API. Perfect for "building in public" with zero friction.

---

Quick Start

1. Install the Plugin

git clone https://github.com/mrwind-up-bird/letter-for-my-future-self.git
cd letter-for-my-future-self
chmod +x install_agents.sh
./install_agents.sh

Or install as a local plugin:

claude plugin install . --scope user

2. Add to Your Project

Copy the template to your project:

cp /path/to/letter-for-my-future-self/CLAUDE_TEMPLATE.md /path/to/your-project/CLAUDE.md

If you already have a CLAUDE.md, merge the relevant sections.

3. Save Your First Checkpoint

Start Claude Code in your project:

cd /path/to/your-project
claude

When ending a session, run:

/checkpoint

Or say "wrap up", "exit", or "end session".

A memory file appears in .memory/letter_YYYYMMDDHHMMSS.md.

4. Resume Next Session

claude

Claude reads the latest letter and picks up where you left off.

---

Commands

Command	Description
/checkpoint	Save a session memory to .memory/
/letter-init	Set up the Letter to Blog CI/CD pipeline

blog_gen.py CLI

Flag	Description
--file, -f	Convert a specific memory file (filename or path)
--setup	Configure global API key (~/.config/letter-for-my-future-self/)
--setup-project	Configure project-specific API key (.letter-config.json)
--status	Show current API key configuration status

---

Letter to Blog Pipeline

Transform private session memories into polished blog posts automatically.

How It Works

.memory/letter_03.md  →  GitHub Actions  →  Claude API  →  drafts/blog_2026-01-29_letter_03.md

1. You work normally — Claude saves memories to .memory/
2. Git push triggers — GitHub Actions detects .memory/** changes
3. Claude transforms — blog_gen.py calls Anthropic API
4. PR created — Generated blog post appears in drafts/
5. You review & publish — Edit if needed, then merge

Setup

Initialize the pipeline:

/letter-init

This creates:

• .github/scripts/blog_gen.py — Python generator script
• .github/scripts/vibe_requirements.txt — Dependencies
• .github/workflows/vibe_publisher.yml — GitHub Actions workflow
• drafts/ — Output directory

Add your API key to GitHub Secrets:

1. Go to Settings → Secrets and variables → Actions
2. Add secret named ANTHROPIC_API_KEY
3. Value: Your key from https://console.anthropic.com

Commit and push:

git add .github/ drafts/
git commit -m "feat: add letter to blog pipeline"
git push

See LETTER_TO_BLOG.md for full documentation.

---

Memory File Format

Each checkpoint creates a file like .memory/letter_20260130143200.md:

# Letter to Myself (Session Handoff)

**Date:** 2026-01-30 14:32

## 1. Executive Summary
* **Goal:** Building a REST API for user authentication
* **Current Status:** Stopped at JWT refresh token implementation

## 2. The "Done" List (Context Anchor)
* Implemented user registration endpoint in `src/routes/auth.ts`
* Added password hashing with bcrypt
* Created PostgreSQL schema in `migrations/001_users.sql`

## 3. The "Pain" Log (CRITICAL)
* **Tried:** jsonwebtoken library for JWT signing
* **Failed:** "Algorithm not supported" error with RS256
* **Workaround:** Switched to HS256 with environment secret
* *Note:* Do not retry RS256 without proper key configuration.

## 4. Active Variable State
* PORT=3000, DATABASE_URL in .env
* Test user: [email protected] / password123

## 5. Immediate Next Steps
1. [ ] Implement refresh token rotation
2. [ ] Add rate limiting to auth endpoints
3. [ ] Write integration tests

---

Git Versioning

Track .memory/ in Git to maintain a timeline of your project's decisions.

Basic Setup

mkdir -p .memory
git add .memory
git commit -m "chore(memory): start tracking session memory"

Team Workflow (Shared vs Private)