actual-chat

Debug the VirtualList component — enable the on-demand consistency checker, drain its violations to a file via the watchdog, and reason about WHY a violation happened. Use when the chat-view (or sidebar) list jumps while scrolling, shows a blank/empty screen, gets stuck (can't reach the bottom / shows endless skeletons), or over-scroll-and-catch-up misbehaves. Also the canonical reference for the list's invariants (anchoring, the no-jump rule, the three reset cases). Pairs with /server-loop (server side) and /debug-ui (browser side).

CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Three modes: SCOPE EXPANSION (dream big), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials).

Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations.

Report-only QA testing. Systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa instead.

Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only.

Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas.

Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues.

Drive the Voxt UI from Codex — chrome-devtools MCP setup, debugUI helpers, fast multi-user sign-in

Stream and search iOS device logs. Use proactively when debugging iOS issues or when user asks to check device logs.

Build, deploy and start iOS app on device. Use proactively when user asks to test, run, or deploy iOS changes.

Create a GitHub issue, assign to current user, and set status to In Progress

Build and start the Mac Catalyst app on this Mac. Use proactively when user asks to test, run, or deploy macOS (Mac Catalyst) changes.

Find orphan processes holding the server port

Show status of all running ActualChat servers

Stop the ActualChat server

Debug the VirtualList component — enable the on-demand consistency checker, drain its violations to a file via the watchdog, and reason about WHY a violation happened. Use when the chat-view (or sidebar) list jumps while scrolling, shows a blank/empty screen, gets stuck (can't reach the bottom / shows endless skeletons), or over-scroll-and-catch-up misbehaves. Also the canonical reference for the list's invariants (anchoring, the no-jump rule, the three reset cases). Pairs with /server-loop (server side) and /debug-ui (browser side).

Answer questions about Voxt — its features, what shipped and when, and how to use it — grounded in three sources: the public "Voxt Announcements" chat, the Landing pages, and the user guide. Use when asked things like "what features shipped this year", "list new features", "how do I use <feature>", "what is Voxt", or any product/usage question about Voxt. Answers are cited to the source.

CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Three modes: SCOPE EXPANSION (dream big), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials).

Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations.

Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas.

Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues.