Workflows that make Memo indispensable

Copy-paste these into your next session. Each one is a single prompt.

Luminaria Memo tools used

luminaria_contextluminaria_searchluminaria_sessionsluminaria_insightluminaria_tag

§ 01 · THE WORKFLOW

Step by step.

1Pick a workflow from below that matches your situation.
2Copy-paste the prompt into your Claude session.
3Memo automatically pulls the right context.
4Claude gives you a structured response you can act on immediately.

§ 02 · EXAMPLE PROMPTS

Try these in Claude.

>Pull context from my last session and any open tasks. Summarize where I left off and what I should work on next.

>Search my sessions from the last 7 days. Summarize what I worked on, decisions made, and open items.

>Load all context about the payments project. I need you to understand the architecture, past decisions, and current state before we start.

§ 03 · EXAMPLE OUTPUT

What you get back.

## Morning briefing

**Last session:** "API rate limiting" (yesterday, 3:42 PM)
You implemented token bucket rate limiting for /api/v2/*.
Tests passing. Not yet deployed.

**Open tasks (3):**
- [ ] Deploy rate limiter to staging
- [ ] Write load test for rate limit thresholds
- [ ] Update API docs with rate limit headers

**Suggested focus:** Deploy to staging first. It's blocking
the QA team.

A. Morning context load

Start every session with full context.

>Pull context from my last session and any open tasks. Summarize where I left off and what I should work on next.

B. Weekly review

See everything you accomplished.

>Search my sessions from the last 7 days. Summarize what I worked on, decisions made, and open items.

## Week of March 17-23

**Sessions:** 12 (8 Claude Code, 4 Claude Chat)
**Total messages:** 847

### Completed
- Auth middleware refactor (3 sessions)
- Payment webhook integration (2 sessions)
- CI/CD pipeline fix (1 session)

### Decisions made
- Chose Stripe over Paddle for payments (March 18)
- Switched to Vitest from Jest (March 20)

### Open items
- Payment webhook retry logic not tested
- CI takes 8 min (goal was under 5)
- Auth refresh token edge case on mobile

C. Onboarding a new project

Give Claude full project context from day one.

>Load all context about the payments project. I need you to understand the architecture, past decisions, and current state before we start.

D. Pre-PR review

Check your work against past decisions before opening a PR.

>Search for any architectural decisions or patterns we established for this module. I want to make sure my changes are consistent before I open a PR.

E. Debug with history

Find if you've encountered this bug before.

>Search my history for anything related to "connection timeout" or "ETIMEDOUT". Have I fixed this before?

Found 2 relevant sessions:

1. "Fix ETIMEDOUT in production" (Feb 28)
   Root cause: Connection pool exhaustion. Fixed by setting
   max connections to 20 and adding idle timeout of 30s.

2. "Database connection issues" (March 5)
   Different issue: DNS resolution timeout. Fixed by
   switching to IP-based connection string.

The current error matches pattern #1. Check your connection
pool settings.

F. Knowledge transfer

Prepare a handoff document from your session history.

>Synthesize everything about the auth system into a handoff document. Include architecture, decisions, open items, and gotchas. Someone else is taking over this module.

G. End-of-day capture

Save context before you forget.

>Save an insight about today's work: "The WebSocket reconnection needs exponential backoff with jitter. Naive retry causes thundering herd when the server recovers." Tag this session as "websocket" and "architecture".

Works with: Claude Code CLI, Claude Desktop (Chat + Code mode), claude.ai browser (via Connectors).

Try it now →