screenshot
Screenshot
Overview
Use this skill to capture reproducible screenshot evidence that is easy to review and trace back to exact system state.
Scope Boundaries
- Bugs or regressions need visual evidence for triage.
- Before/after comparison is required for implementation validation.
- QA or review comments require precise state capture.
Templates And Assets
- Screenshot evidence template:
assets/screenshot-evidence-template.md
Inputs To Gather
- Capture intent (bug, regression, implementation proof).
- Exact target state (environment, route, data fixture, viewport, locale).
- Storage location and sharing audience.
Deliverables
- Screenshot set with stable names and reproducible capture context.
- Metadata log (state, environment, timestamp, operator).
- Optional before/after pair for direct comparison.
Workflow
- Define the minimum state required to prove the target issue or behavior.
- Set deterministic capture conditions (viewport, theme, locale, seed data).
- Capture screenshots at the smallest useful scope while preserving diagnostic context.
- Verify key evidence is legible (labels, errors, indicators, timestamps if relevant).
- Store artifacts under predictable naming and attach reproduction steps.
Quality Standard
- Reviewers can reproduce the captured state from metadata.
- Artifact names encode purpose and scenario.
- Sensitive data is masked before external sharing.
- Comparison captures use consistent viewport and state conditions.
Failure Conditions
- Stop when screenshot permissions are unavailable.
- Stop when required masking cannot be completed safely.
- Escalate when capture conditions are non-deterministic and evidence is unreliable.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9