phase-10m-chat-ui-polish-review — Claude Code prompt: what it does
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.
Apache-2.0 ★ 1,497 updated 2026-06-16
.claude/commands/phase-10m-chat-ui-polish-review.mdWhat phase-10m-chat-ui-polish-review does
The prompt puts the model in three seats at once — principal engineer, architect and product manager — and asks for a read-only pass over Phantom's Murph chat. It looks at running state, tool call cards, what collapses by default, progress and thinking, the run timeline, artifacts, markdown, file previews, mobile layout and recovery after a reload. Editing is off the table.
Six review questions sit inside, plus acceptance criteria, a list of anti-patterns and a fixed answer shape: five issues ranked by impact, evidence with file paths, one small next slice with tests and visual checks, and what should wait. Before any of that it walks through AGENTS.md, CLAUDE.md, the research notes in research/chat-experience/, chat components such as tool-call-card.tsx and run-activity-row.tsx, then the branch diff against origin/main.
Every path points at /Users/truffle/work/phantom-murph-hardening/. Point it at your own tree first, otherwise the model reads files that aren't there. A git checkout with origin/main is part of the deal too.
What it helps with
- Audit a long-running agent chat for UI flaws
- Split correctness bugs from product polish
- Decide what artifact cards still need
- Scope the next PR with tests and visual checks
- Check mobile layout and scroll behaviour
Example prompts for the agent
- Run
/phase-10m-chat-ui-polish-reviewon this branch and list the five worst UI issues with file paths. - Use
/phase-10m-chat-ui-polish-reviewto pick one next slice that fits in a single PR. - Go through
/phase-10m-chat-ui-polish-reviewand tell me which Playwright visual tests to add.
How to install phase-10m-chat-ui-polish-review
Manually: put the files in place
.claude/commands/phase-10m-chat-ui-polish-review.mdHow to use
Paste the text at the start of a chat or into project instructions
Questions about phase-10m-chat-ui-polish-review
How do I install phase-10m-chat-ui-polish-review in Claude Code?
Put the prompt file at .claude/commands/phase-10m-chat-ui-polish-review.md inside your project. It then shows up as the slash command /phase-10m-chat-ui-polish-review.
What does phase-10m-chat-ui-polish-review do?
It runs a read-only review of Phantom's chat UI against a fixed reading list and the branch diff. You get five issues ranked by impact, evidence with paths, a proposed next slice, and items to postpone.
Why does the prompt look for files that aren't in my repo?
The required reading list points at /Users/truffle/work/phantom-murph-hardening/. Rewrite those paths for your own tree before running it.
Source text
phase-10m-chat-ui-polish-review.md · Apache-2.0
ultrathink. ultrathink. ultrathink. # Phase 10M Review Prompt: Phantom Chat UI Polish You are a principal engineer, principal architect, and principal product manager at Anthropic, all three at once. You are reviewing Phantom's Murph chat experience for production-grade quality. This is read-only. 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. ## Product Bar Cheema wants Phantom chat to feel best in class, comparable in craft to the best coding-agent chat products. Every small detail matters: running state, tool cards, collapsed defaults, thinking/progress, durable run timeline, artifacts, markdown, file previews, mobile layout, reload recovery, and local build ergonomics. We are not building a marketing page. The chat is the product. ## Required Reading Read: 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-10d-chat-ui-polish-research.md` 5. `/Users/truffle/work/phantom-murph-hardening/research/chat-experience/phase-10b-durable-timeline-research.md` 6. `/Users/truffle/work/phantom-murph-hardening/research/chat-experience/phase-10h-product-direction.md` 7. `/Users/truffle/work/phantom-murph-hardening/research/chat-experience/phase-10k-page-artifact-ui.md` 8. `/Users/truffle/work/phantom-murph-hardening/chat-ui/src/components/tool-call-card.tsx` 9. `/Users/truffle/work/phantom-murph-hardening/chat-ui/src/components/run-activity-row.tsx` 10. `/Users/truffle/work/phantom-murph-hardening/chat-ui/src/components/message-list.tsx` 11. `/Users/truffle/work/phantom-murph-hardening/chat-ui/src/components/assistant-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/lib/chat-store.ts` 14. `/Users/truffle/work/phantom-murph-hardening/chat-ui/src/lib/tool-disclosure.ts` 15. `/Users/truffle/work/phantom-murph-hardening/chat-ui/src/index.css` Also inspect the latest PR branch diff against `origin/main`. ## Review Questions 1. What UI flaws remain after the current PR, especially ones visible in real long-running Murph tasks? 2. Are completed tool cards collapsed by default while still making evidence easy to inspect? 3. Does the run timeline explain activity during long tool calls, compaction, reload/replay, and post-run completion? 4. Are artifact cards useful enough, or should the next slice add richer previews, persistent artifact lists, or copy/open affordances? 5. Are there layout issues on desktop or mobile: borders, scroll behavior, truncation, nested cards, empty states, input footer, or typography? 6. What automated or Playwright visual tests should be added before this UI is considered shippable? ## Acceptance Criteria - Findings must cite real files and ideally lines. - Separate correctness bugs from product polish. - Recommend a small next implementation slice that can be built and visually verified in one PR. - Do not ask for broad redesign for its own sake. The next slice must improve real task usability. ## Anti-Patterns - Do not focus only on colors. - Do not propose hiding tool details for safety. The user owns the agent and needs inspectability, with reasonable redaction for secrets. - Do not introduce decorative UI that competes with the work. - Do not recommend a huge rewrite unless you can name a specific blocker that makes incremental work worse. ## Final Output Return: 1. Top five UI issues ranked by impact. 2. Evidence with file paths. 3. A proposed next slice with files, tests, and visual checks. 4. Things that should wait. ultrathink. ultrathink. ultrathink.
© ghostwright · Apache-2.0 · ghostwright/phantom