Skip to content
cccskills
FreePublished on GitHub

browser-tester-playbook

Working playbook preloaded into the browser-tester helper; the coach updates its Lessons after each round. Use only when acting as browser-tester or coaching it. NOT for general UI work (use matrx-frontend's browser-testing doc).

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md4.6 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

<!-- SYNCED COPY — do not edit here. Canonical: common-docs/skills/browser-tester-playbook/SKILL.md This file is distributed to every consuming repo by common-docs/meta/scripts/sync_skills.py. Edit the canonical, run the sync, and commit each repo. Edits made here are overwritten and lost. -->

browser-tester playbook

You test; you never fix. Your product is a defect list another agent can fix from without re-testing. Full harness rules: matrx-frontend docs/official/browser-testing.md — read the section you need, not the whole file.

Setup (once, before any test step)

  1. Site: the LIVE site, https://www.aimatrx.com (server https://server.app.matrxserver.com). Checks and sign-offs never run on localhost (Arman, 2026-10-18); live has every pushed change within one release, about 30 minutes, so a change not yet released is tested after it ships. Only when the brief calls the walk a rapid fix-and-look loop on UI being changed right now: in matrx-frontend run pnpm preview:status, reuse the running server or pnpm preview:start, open only the hostname it prints (never bare localhost), never start a second dev server.
  2. Tab: use the tab id the brief names, or open your own and pass its tab id on every call. Never act in another tab.
  3. Viewport: new tabs are 0×0 — resize_window with explicit width/height (1280×800) first. computer needs the tab fronted (tabs_select).
  4. Sign in as admin@admin.com with node scripts/real-tests/pw.mjs <run> signin (a private headless browser); never type a password into a page, never use Arman's Chrome. 🚨 The built-in browser pane on www.aimatrx.com is usually signed in as ARMAN: read-only there — never create, type, save or submit anything in his account (policies/test-data-looks-real.md). In the local fix-and-look loop only: pnpm dev-login /<route> and open the URL it prints.
  5. Local fix-and-look loop only: warm the route with curl first; first compiles take 45–60 s, longer than a tool timeout. Live needs no warm-up.
  6. AI test mode: when the brief tests screens or plumbing, not the AI, open the first URL with ?ai_test_mode=stand_in (saved answers, no spend). When the brief tests the AI itself, never. Results badged "Baseline replay" / "Stand-in" are saved answers, never report them as AI output. ai-test-mode.
  7. AI replies: never test through General Chat (it is for people who chat; owner's words). Any test that needs an AI reply uses Test Reply (agent 8a4b7c8e-144f-4391-b5f0-3d2cd2ecee0f, the cheapest plumbing model). The test seats (admin@admin.com, test@test.com) already default a new chat to it through a user binding of chat.default_new_chat; for any other seat open /ai?agent=8a4b7c8e-144f-4391-b5f0-3d2cd2ecee0f or pass that agent id. Send a short message such as "ok"; one reply proves the point.
  8. Smoke check: one click, confirm the screen changed. Two environment failures (hidden pane, dead input, server down, login loop) → stop, return BLOCKED_ENV naming what failed.

Testing

  • Walk what the brief names as a real user would. Prefer read_page/get_page_text over screenshots; screenshot only to prove a visual defect.
  • Inputs: form_input (React-safe). computer type appends and Backspace does not clear. Refresh refs with read_page after any navigation or re-render.
  • Check console and network (read_console_messages, read_network_requests) after reloading once the tab is attached.
  • Do not wait more than 5 minutes for anything. A wait that long → note it and move on.

The defect list (your report file)

One entry per defect, numbered:

  • Where: URL and the control.
  • Steps: the exact clicks/inputs from a fresh page.
  • Expected / Actual: one line each; actual quotes the error text if any.
  • Evidence: console/network line, row id, or screenshot path.
  • Severity: broken · wrong · rough. Then a line per brief item that PASSED with its evidence. No fix proposals, no code reading beyond naming the component if obvious.

Lessons (maintained by the coach — newest first, keep under 30 lines)

  • (none yet)

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Admin debug system wiring for the floating AdminIndicator's live debug data and Copy Full Context. Use when adding debug visibility to a route or feature, wiring useDebugContext or the debug panel, capturing console errors, or enabling the copy-context workflow for a page.

The English summary is being prepared. Showing the original description.

armanisadeghi/ai-matrx4Updated Oct 23, 2026

Compact two-icon Copy / Copy-for-AI controls (components/agent-copy). Use when adding copy buttons to a row, card, list, or record; merging duplicate Copy/JSON/AI controls; continuing the copy rollout; or writing a Copy-for-AI payload. NOT for markdown content actions (use rich-document-actions).

The English summary is being prepared. Showing the original description.

armanisadeghi/ai-matrx4Updated Oct 23, 2026

Disclosing a surface's existing fixed AI jobs in the shell's top Agents menu. Use when a page, panel, overlay, or window already runs a mandate behind a button, assist, automatic action, or mode; when the agent-disclosure guard names a file; or during a surface check.

The English summary is being prepared. Showing the original description.

armanisadeghi/ai-matrx4Updated Oct 23, 2026

The method for getting a cheaper model to match an agent's big-model answers by fixing instructions, inputs and setup. Use when asked to move an agent to a smaller or cheaper model, prove one model beats another, or compare models on an agent's test cases.

The English summary is being prepared. Showing the original description.

armanisadeghi/ai-matrx4Updated Oct 23, 2026

The watch-fix-rerun method for making an existing platform agent or automated process efficient and correct: baseline its ledger, run one unit yourself, fix the class behind every wasted call, rerun, record. Use when asked to improve, optimize, watch, or 'make efficient' an agent, a sandbox session, a sync job, or any recurring automated process.

The English summary is being prepared. Showing the original description.

armanisadeghi/ai-matrx4Updated Oct 23, 2026

Redux state for agent execution and firing agent shortcuts. Use when editing features/agents/redux/, building agent UI, creating a conversation, touching assembleRequest or NDJSON stream state, wiring agent-state selectors, adding a per-conversation capability, or triggering a shortcut from a button, menu, or code (useShortcutTrigger, launchAgentExecution).

The English summary is being prepared. Showing the original description.

armanisadeghi/ai-matrx4Updated Oct 23, 2026

See all skills by armanisadeghi

Report a problem with this skill