[gsdevme]

Summary

Adds a browser-qa.md topic telling agents to QA user-visible UI changes in a real browser and attach before/after screenshots to the tracking artefact.

• Trigger: any change with a user-visible surface rendered in a browser (anything you would cover with UI or e2e tests). Backend-only and CLI changes are exempt.
• Tooling: phrased as generic browser automation so Codex can follow it too. claude-in-chrome is named as the Claude Code example; other agents use what they have (e.g. Playwright).
• Screenshots: capture before on the base branch prior to the change and after at the same pages/viewport; name as <area>-before.png / <area>-after.png; keep them out of the working tree; cover default, loading/empty/error, and mobile width where relevant.
• Attachment: always in the GitHub PR description under a "Before / After" heading; also on the GitHub Issue or Jira ticket when that is the tracking record. Do both when a project tracks in Jira but reviews in GitHub.
• Honesty: no faking, cropping, or retouching; say when a state can't be reproduced.

The topic is registered in the Makefile TOPIC_FILES list (appended after code-comments.md), the README layout tree, and the three explicit enumerations in tests/apply.bats.

Test plan

• make test — all 13 Bats tests pass
• make apply — ~/.claude/CLAUDE.md imports browser-qa.md and .agents/AGENTS.md contains the topic text

🤖 Generated with Claude Code