feat: show screenshots to user during QA and browse sessions (v0.5.0.1) (#129)

Add rule 11 to QA and Design methodologies in gen-skill-docs.ts
instructing Claude to Read screenshot PNGs after taking them.
This makes screenshots visible as clickable elements in Conductor
and other Claude Code UIs. Also added to browse and gstack SKILL
templates.

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Garry TanandClaude Opus 4.6 authored and GitHub committed 2026-03-17 10:30:19 -05:00
1 parent c8c2cbba33
commit 5f41cd9ad7
11 files changed
+23 -3

No files matched your search

+1
View File
@@ -111,6 +111,7 @@ If `NEEDS_SETUP`:
- NEVER use `mcp__claude-in-chrome__*` tools. They are slow and unreliable.
- Browser persists between calls — cookies, login sessions, and tabs carry over.
- Dialogs (alert/confirm/prompt) are auto-accepted by default — no browser lockup.
- **Show screenshots:** After `$B screenshot`, `$B snapshot -a -o`, or `$B responsive`, always use the Read tool on the output PNG(s) so the user can see them. Without this, screenshots are invisible.
## QA Workflows