Results for “screenshot-proof”

Capture a visual demo reel (GIF, terminal recording, screenshots) for PR descriptions. Use when shipping UI changes, CLI features, or any work with observable behavior that benefits from visual proof. Also use when asked to add a demo, record a GIF, screenshot a feature, show what changed visually, create a demo reel, capture evidence, add proof to a PR, or create a before/after comparison.

Structured visual QA verdict for screenshot-to-reference comparisons

Structured visual QA verdict for screenshot-to-reference comparisons

Captures desktop screenshots on macOS, Linux, and Windows with support for full screen, specific apps, windows, and pixel regions.

Validates rendered UI with browser or Playwright screenshots after implementation, redesign, responsive changes, or visual regressions.

Captures marketing screenshots of a SwiftUI iOS app across multiple locales, devices, and appearances, producing full-screen captures and isolated element renders.

Use when the user explicitly asks for a desktop or system screenshot (full screen, specific app or window, or a pixel region), or when tool-specific capture capabilities are unavailable and an OS-level capture is needed.

Capture full-page screenshots of any web page using Chrome DevTools Protocol, handling SPAs, lazy-loaded images, and very tall pages with zero external dependencies.

Use when the user explicitly asks for a desktop or system screenshot (full screen, specific app or window, or a pixel region), or when tool-specific capture capabilities are unavailable and an OS-level capture is needed.

基于证据优先的仓库执行工作流，适用于ECC。当用户需要运行命令、检查仓库、调试CI失败或推送带有精确执行和验证证明的窄修复时使用。

Create app store screenshots and preview videos for Apple App Store and Google Play with exact platform specs, device mockups, and gallery ordering guidance.

Use quando o usuário solicitar explicitamente uma captura de tela do desktop ou do sistema (tela cheia, app ou janela específica, ou região de pixels), ou quando as capacidades de captura específicas da ferramenta não estiverem disponíveis e uma captura de nível de SO for necessária.

Runs throwaway experiments to validate feasibility before building, producing a verdict with evidence.

Sentinel Validation & Project Promotion

Verify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).

Provides grep-based patterns to verify that code artifacts are real implementations rather than stubs or placeholders, covering React components, API routes, database schemas, and hooks.

Scaffolds a per-task verification skill for a repo, including a dev-local launcher, a browser driver, and a verification SOP that spawns a sub-agent to drive the app and produce proof.

Use to prove that a support process, policy or script change actually took effect — when, for whom, and whether behaviour followed — rather than that it was approved. Trigger for "prove we made that change", "when did this policy actually change", "did the team adopt the new process", evidencing remediation, "we told everyone" claims, or a change that was signed off and never landed.