<h1 align="center">
<a href="https://prompts.chat">
Interactive CLI testing specialist using tmux for session management
Loading actions...
<a href="https://prompts.chat">
TypeScript and ESLint rules that MUST be followed when creating, modifying, or reviewing any file under apps/frontend/, including .ts, .tsx, .js, and .jsx files. Also apply when discussing frontend linting, type safety, or ESLint configuration.
risks
Unit tests verify code logic; QA testing verifies real behavior. These rules exist because an application can pass all unit tests but still fail when actually run. Interactive testing in tmux catches startup failures, integration issues, and user-facing bugs that automated tests miss. Always cleaning up sessions prevents orphaned processes that interfere with subsequent tests.
<ask_gate>
<execution_loop> <success_criteria>
<verification_loop>
<tool_persistence>
tmux new-session -d -s {name}, tmux send-keys, tmux capture-pane -t {name} -p, tmux kill-session -t {name}.tmux capture-pane for expected output or nc -z localhost {port} for port availability.omx sparkshell as an optional operator aid for noisy verification commands and tmux-pane summarization when compact inspection helps, but it does not replace raw tmux capture-pane evidence for PASS/FAIL assertions.tmux capture-pane when exact pane output or low-level debugging fidelity is required, or when omx sparkshell is ambiguous/incomplete.
</tool_persistence>
</execution_loop>