2.1 KiB
Tier: Static Screenshots
Capture individual PNG screenshots. No animation, no stitching.
Best for: Fallback when other tools are unavailable, library demos, or features where animation doesn't add value. Output: PNG files Label: "Screenshots" Required tools: Varies (agent-browser for web, silicon for CLI, or native screenshot)
Secrets rule applies here too. For browser captures, do not open DevTools, do not screenshot URLs carrying tokens, and avoid pages that display unmasked credentials. For CLI captures, render output that was already free of credentials — no env-var dumps, no --api-key flag values, no auth headers in error traces. Scan each PNG before uploading; if anything credential-like appears, discard and recapture.
Capture by Project Type
Web app or desktop app (agent-browser available)
If agent-browser is not installed, inform the user: "agent-browser is not installed. Run /ce-setup to install required dependencies." Then skip to the CLI or fallback sections below.
agent-browser open [URL]
agent-browser wait 2000
agent-browser screenshot [RUN_DIR]/screenshot-01.png
Capture 1-3 screenshots: before state, feature in action, result state.
CLI tool (silicon available)
Run the command, capture its output to a text file, then render with silicon:
silicon [RUN_DIR]/output.txt -o [RUN_DIR]/screenshot-01.png --theme Dracula -l bash --pad-horiz 20 --pad-vert 20
CLI tool (no silicon)
Run the command and capture the raw terminal output. Include the output as a code block in the PR description instead of an image. Label it as "Terminal output", never "Screenshot".
Library
Run example code that exercises the new API. Capture the output as above (silicon if available, code block if not).
Upload
Each PNG is uploaded individually. Proceed to references/upload-and-approval.md for each file, or upload all and present them together for approval.
For multiple screenshots, the markdown embed uses multiple image lines:
## Screenshots
