Skip to main content
prompt GP ChatGPT

phase-10m-artifact-memory-architecture — Claude Code prompt

phase-10m-artifact-memory-architecture is a Claude Code prompt for designing agent memory, artifact storage, and continuity across long sessions after context compaction, without editing files.

Apache-2.0 ★ 1,497 updated 2026-06-16

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/phase-10m-artifact-memory-architecture.md
Open on GitHub

What phase-10m-artifact-memory-architecture does

This prompt puts Claude Code into the role of a principal architect and engineer to design long-running agent session workflows. The main goal is handling session state smoothly after context compaction so the agent does not lose created artifacts, file paths, or recent operational facts. Work runs in read-only mode with no file edits permitted.

The prompt establishes a structural separation: durable user memory, agent continuity facts, and searchable historical transcripts. Claude analyzes whether to create a chat_artifacts table, how to expose artifacts via MCP tools or injected context, and what minimal slice should ship first.

Execution relies directly on local repository files referenced in the prompt, such as src/memory/system.ts and schema.ts. Without access to those specific paths, the model cannot provide exact file and line citations.

What it helps with

  • design agent continuity across context compaction events
  • isolate durable user preferences from ephemeral run state
  • determine the schema for chat_artifacts and evaluate MCP tool integration
  • produce an architectural test plan without writing code changes

Example prompts for the agent

  • Run the phase-10m-artifact-memory-architecture analysis on the current codebase
  • /phase-10m-artifact-memory-architecture

How to install phase-10m-artifact-memory-architecture

Manually: put the files in place

.claude/commands/phase-10m-artifact-memory-architecture.md

Questions about phase-10m-artifact-memory-architecture

How to install phase-10m-artifact-memory-architecture in Claude Code?

Place the prompt file into .claude/commands/phase-10m-artifact-memory-architecture.md inside your workspace. Claude Code will pick it up as a custom slash command.

What does phase-10m-artifact-memory-architecture do?

It forces a thorough read-only architectural evaluation of agent memory layers, artifact tracking, and post-compaction transcript retrieval.

Does this prompt modify source files?

No, the prompt explicitly forbids file edits and limits the output to architectural decisions, trade-offs, and testing plans.

Source text

phase-10m-artifact-memory-architecture.md · Apache-2.0
ultrathink. ultrathink. ultrathink.

# Phase 10M Architecture Prompt: Artifacts, User Memory, Agent Continuity

You are a principal engineer, principal architect, and principal product
manager at Anthropic, all three at once. This is read-only architecture work.
Do not edit files.

No context anxiety. No token limits. No time pressure. No cost anxiety. No
"v2" thinking. There is no v2. Build it right. Take as long as you need.

## Context

Cheema wants Phantom on Murph to handle long-running sessions like a serious
agent product. After compaction, the agent should continue smoothly. It should
not forget created pages, confuse magic-login links with artifacts, lose file
paths, or make the user repeat prior context.

He also raised an architectural split:

- User memory: durable user-visible facts and preferences.
- Agent continuity: operational facts for the current or recent runs, such as
  created files, page URLs, task status, failures, and transcript-search
  pointers.
- Historical transcript: searchable prior chat records for recovery after
  compaction.

Your job is to decide what should exist in Phantom versus Murph, what should
be MCP tools versus built-in server state, and what the next shippable slice is.

## Required Reading

Read:

1. `/Users/truffle/.claude/AGENTS.md`
2. `/Users/truffle/.claude/CLAUDE.md`
3. `/Users/truffle/work/murph/AGENTS.md`
4. `/Users/truffle/work/murph/VISION.md`
5. `/Users/truffle/work/murph/ARCHITECTURE.md`
6. `/Users/truffle/work/murph/PROGRESS.md`
7. `/Users/truffle/work/phantom-murph-hardening/CLAUDE.md`
8. `/Users/truffle/work/phantom-murph-hardening/docs/memory.md`
9. `/Users/truffle/work/phantom-murph-hardening/src/memory/system.ts`
10. `/Users/truffle/work/phantom-murph-hardening/src/chat/continuity-context.ts`
11. `/Users/truffle/work/phantom-murph-hardening/src/chat/transcript-search.ts`
12. `/Users/truffle/work/phantom-murph-hardening/src/chat/run-timeline.ts`
13. `/Users/truffle/work/phantom-murph-hardening/src/agent/in-process-reflective-tools.ts`
14. `/Users/truffle/work/phantom-murph-hardening/src/ui/tools.ts`
15. `/Users/truffle/work/phantom-murph-hardening/src/db/schema.ts`
16. Relevant notes under `/Users/truffle/work/notes-main`.

## Questions

1. Should created pages/files become a durable `chat_artifacts` table, or can
   run timelines plus stream events carry enough for now?
2. If we add artifacts, what exact schema is minimal but future-proof:
   type, title, URL, path, MIME, size, preview kind, safety metadata,
   retention, source tool, source message, source run?
3. Should artifacts be exposed to the agent through an MCP tool, injected
   continuity context, or both?
4. How should user memory stay separate from operational run continuity?
5. How should historical transcript search be presented to the agent after
   compaction without raw replay bloat?
6. What is the smallest next slice that improves real post-compaction behavior
   and user-visible UI without prematurely building a full artifact system?

## Acceptance Criteria

- Cite file paths and line references.
- Make a clear recommendation.
- Include tradeoffs for MCP tool versus built-in server state versus UI-only.
- Identify migration and testing requirements if a schema change is proposed.
- Explicitly state what belongs in Murph and what belongs in Phantom.

## Anti-Patterns

- Do not put Phantom-specific artifact logic into Murph.
- Do not make TypeScript reason about user intent when an agent prompt/tool
  can do it better.
- Do not store secrets, magic-login tokens, raw screenshots, or giant payloads
  as continuity facts.
- Do not replace transcript search with raw transcript injection.

## Final Output

Return:

1. Recommended architecture.
2. Minimal next slice.
3. Schema or no-schema decision.
4. Agent-facing tool/context decision.
5. Test plan.
6. Risks and non-goals.

ultrathink. ultrathink. ultrathink.

© ghostwright · Apache-2.0 · ghostwright/phantom

Similar prompts

All prompts for Agent setup: memory, context, orchestration →

From the same set38

The whole set →
phase-10j-tool-card-collapse-research phase-10j-tool-card-collapse-research is a prompt for Claude Code and ChatGPT that examines Phantom tool cards: collapsing completed calls while keeping errors and blocked work visible. GP ChatGPT ★ 1,497repo stars phase-10i-transcript-search-research phase-10i-transcript-search-research guides an architectural study for historical chat transcript search in Phantom after Murph compaction. Useful when planning agent context retrieval. GP ChatGPT ★ 1,497repo stars phase-10a-activity-correctness-reviewer The phase-10a-activity-correctness-reviewer prompt asks Claude Code to review Phantom’s Phase 10A patch and report concrete findings with file and line references. It targets changes in the named project. GP ChatGPT ★ 1,497repo stars phase-10m-chat-ui-polish-review phase-10m-chat-ui-polish-review — a read-only review prompt for Phantom's Murph chat UI: it walks the components, the run timeline and artifact cards, then ranks what to fix next. GP ChatGPT ★ 1,497repo stars phase-10i-chat-detail-research The phase-10i-chat-detail-research prompt asks Claude Code to examine Phantom’s chat UI and recommend the next implementation slices. Use it to shape a focused interface plan and Playwright checks. GP ChatGPT ★ 1,497repo stars phase-10i-memory-architecture-research phase-10i-memory-architecture-research — a Claude slash command that researches how Phantom chat should keep user-facing memory apart from the agent's working memory, then writes a report with a plan. GP ChatGPT ★ 1,497repo stars phase-10a-murph-pi-event-research phase-10a-murph-pi-event-research is a Claude Code prompt that audits Murph and Pi runtime events to surface agent progress, compaction, and tool calls in Phantom chat. GP ChatGPT ★ 1,497repo stars phase-10a-product-experience-research The phase-10a-product-experience-research prompt guides research into Phantom’s long-running agent chat, from run status to tool details and error states. Use it to shape an interface proposal and a phased build plan. GP ChatGPT ★ 1,497repo stars

Project sponsors

Companies that keep this analytics open