phase-10i-chat-detail-research — Claude Code prompt: chat audit
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.
Apache-2.0 ★ 1,497 updated 2026-06-16
.claude/commands/phase-10i-chat-detail-research.mdWhat phase-10i-chat-detail-research does
The prompt directs Claude Code to assess how Phantom presents long-running agent work, collapsed tool cards, and generated files or pages. The report should also cover small visual details, icon choices, risks, acceptance criteria, and screenshot-based Playwright checks.
It names project files to read and asks for relevant pattern research in Pi web UI. The report goes to /Users/truffle/work/phantom-murph-hardening/research/chat-experience/phase-10i-chat-detail-research.md. Application code must stay untouched.
The task depends on access to the listed local paths and calls for Playwright screenshots. Recommendations should follow existing React, Tailwind, and lucide patterns, while avoiding hidden reasoning and sensitive tool output. This is a project-specific review of Phantom, not a general chat-interface prompt.
What it helps with
- Show meaningful agent activity during long-running work
- Identify useful details missing from collapsed tool cards
- Plan chat views for generated files and pages
- Order interface changes into the next PRs
- Define Playwright screenshot checks for each slice
Example prompts for the agent
- Audit Phantom’s chat using the files named in the prompt and save your report to the specified Markdown path.
- Review collapsed tool cards and file previews without editing application code.
- Write acceptance criteria and a Playwright screenshot plan for the proposed changes.
How to install phase-10i-chat-detail-research
Manually: put the files in place
.claude/commands/phase-10i-chat-detail-research.mdHow to use
Paste the text at the start of a chat or into project instructions
Questions about phase-10i-chat-detail-research
How do I install phase-10i-chat-detail-research in Claude Code?
Add the command file at .claude/commands/phase-10i-chat-detail-research.md.
What does phase-10i-chat-detail-research do?
It asks Claude Code to inspect Phantom’s chat interface and produce findings, an ordered implementation plan, and visual verification steps.
What does the prompt need to run?
Claude Code needs access to the listed local Phantom project files. The requested visual checks use Playwright screenshots.
Source text
phase-10i-chat-detail-research.md · Apache-2.0
ultrathink. ultrathink. ultrathink. You are a principal engineer, principal architect, and principal product manager at Anthropic, all three at once. You are researching the next best-in-class chat detail slice for Phantom. 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. ## Mission Audit Phantom chat with obsessive product detail and propose the next implementation slices for: 1. Long-running agent activity that never feels dead. 2. Tool cards that are collapsed by default but useful at a glance. 3. First-class files, pages, and artifacts. 4. Minor visual details: borders, spacing, icons, copy/open affordances, markdown, empty/loading/error states. 5. User-visible memory and agent-visible memory surfaces. Write your report to: `/Users/truffle/work/phantom-murph-hardening/research/chat-experience/phase-10i-chat-detail-research.md` Do not edit application code. ## Required Reading Read these files directly: 1. `/Users/truffle/.claude/AGENTS.md` 2. `/Users/truffle/.claude/CLAUDE.md` 3. `/Users/truffle/work/phantom-murph-hardening/CLAUDE.md` 4. `/Users/truffle/work/phantom-murph-hardening/research/chat-experience/phase-10h-product-direction.md` 5. `/Users/truffle/work/phantom-murph-hardening/research/chat-experience/phase-10h-live-verification.md` 6. `/Users/truffle/work/phantom-murph-hardening/research/chat-experience/phase-10h-phantom-chat-review.md` 7. `/Users/truffle/work/phantom-murph-hardening/chat-ui/src/components/message-list.tsx` 8. `/Users/truffle/work/phantom-murph-hardening/chat-ui/src/components/run-activity-row.tsx` 9. `/Users/truffle/work/phantom-murph-hardening/chat-ui/src/components/tool-call-card.tsx` 10. `/Users/truffle/work/phantom-murph-hardening/chat-ui/src/components/assistant-message.tsx` 11. `/Users/truffle/work/phantom-murph-hardening/chat-ui/src/components/user-message.tsx` 12. `/Users/truffle/work/phantom-murph-hardening/chat-ui/src/components/chat-input.tsx` 13. `/Users/truffle/work/phantom-murph-hardening/chat-ui/src/components/markdown.tsx` 14. `/Users/truffle/work/phantom-murph-hardening/chat-ui/src/lib/chat-activity.ts` 15. `/Users/truffle/work/phantom-murph-hardening/chat-ui/src/lib/chat-store.ts` 16. `/Users/truffle/work/phantom-murph-hardening/src/chat/run-timeline.ts` 17. `/Users/truffle/work/phantom-murph-hardening/src/ui/tools.ts` 18. `/Users/truffle/work/phantom-murph-hardening/src/ui/preview.ts` Also inspect Pi web UI patterns in `/Users/truffle/work/pi-mono/packages/web-ui/src` where relevant. ## Questions To Answer 1. What should be fixed next for the user to feel the agent is alive during long work? 2. What tool-card collapsed information is missing today? 3. How should generated pages/files be rendered in chat without requiring raw JSON reading? 4. Which icons should be used from `lucide-react` for memory, transcript search, artifacts, files, pages, tool states, and progress? 5. What minor border/spacing/layout issues are visible from the current code and screenshots? 6. What should be built in the next one or two PRs, and what should wait? 7. How should we visually verify each slice with Playwright screenshots? ## Design Constraints - Use existing React/Tailwind/lucide patterns. - Do not build a landing page or marketing layer. - Avoid one-note color changes. Keep visual changes restrained and practical. - Do not use emojis as primary UI primitives. - Do not expose hidden reasoning or sensitive tool output. - Prefer feature-complete small slices over broad partial redesigns. ## Deliverable Format Write: 1. Executive recommendation. 2. Current UI findings by component. 3. Concrete next slices, in order. 4. Visual acceptance criteria. 5. Playwright verification plan. 6. Risks and edge cases. ultrathink. The target is a chat surface people choose because it feels alive, legible, and trustworthy.
© ghostwright · Apache-2.0 · ghostwright/phantom