Screenshot
Trigger Boundary
- •Use when visual proof is required for engineering decisions or review comments.
- •Do not use for DOM-level automation artifacts if browser tooling already captures equivalent evidence.
- •Do not use for source design extraction from Figma files.
Goal
Capture reproducible visual artifacts that make issues understandable without additional context.
Inputs
- •Capture target (display, app window, active window, region)
- •Evidence intent (regression proof, before/after comparison, bug report)
- •Storage path and sharing requirements
Outputs
- •Screenshot artifact set with stable naming
- •Capture metadata (what, where, when, and why)
- •Optional comparison pair for change validation
Workflow
- •Define the exact UI state that must be captured.
- •Capture at the smallest scope that still preserves diagnostic value.
- •Verify legibility of key evidence (labels, errors, version/state markers).
- •Store artifacts under predictable paths for PR/issue references.
- •For external sharing, attach capture context so reviewers can reproduce the same state.
Quality Gates
- •Captures include enough context to identify app state and scenario.
- •Local debug capture remains lightweight; apply masking only when artifacts are shared externally.
- •Artifact paths and names are consistent across updates.
- •Reviewer can map each screenshot to a concrete reproduction step.
Failure Handling
- •Stop when screen-capture permissions are unavailable.
- •Stop external sharing when required masking cannot be completed safely.