eng-ui-screenshot
FeaturedScreenshot capture for deterministic PNG evidence and visual-contract bundles for Compozy Storybook stories and local UI URLs. Use for visual audits, regression diffs, and design-parity checks. Do not use for interactive E2E flows, remote authenticated sites, or Storybook test execution.
Install
Quality Score: 93/100
Skill Content
Details
- Author
- compozy
- Repository
- compozy/compozy
- Created
- 7 months ago
- Last Updated
- today
- Language
- Go
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
screenshot-assets
Capture authenticated product screenshots through the repository-owned Playwright CDP script and archive them in the invoking loop's Memory. Use when content needs truthful UI evidence, reusable product screenshots, a selected component, or a full-page browser capture. Requires only user-installed uv and Chrome configured by onboarding; never depends on MCP tools, external Skills, private repositories, or external scripts.
capturing-screenshots
Captures deterministic, visually verified screenshots of a running web or native app (named screens, states, viewports, dark mode) with a manifest. Use when the user says "take screenshots", or when asked for screenshots of an app or its screens. Not for attaching images to a PR; use attaching-pr-screenshots.
capture-pr-screenshots
Use when opening or updating a PR that changes a UI route file (`page.tsx`, `+page.svelte`, a `routes/` entry) without adding a matching screenshot. Also fire when the user says "missing screenshot" / "no screenshot for the UI" / "capture the screenshot" / "screenshot for this PR" / "you forgot the screenshot". Skip on a backend-only PR, or one that already includes screenshots for the surfaces it changes. Where the repo documents its own capture command, run that instead — this skill is the fallback for repos that document nothing.