design-qc

name

design-qc

description

Visual QC of a running UI — captures screenshots via `openwolf designqc`, then reviews them against modern UI standards (DevSkyy dashboard) or SkyyRose brand canon (WP theme). Use when the user asks to check, evaluate, or improve the design/UI of the DevSkyy app or the SkyyRose theme. Do NOT use for choosing or migrating a component framework (that is `reframe`) or for building net-new UI from scratch (that is `frontend-design` / `fashion-theme-architect`).

When to use

• The user asks to check, evaluate, or improve the design/UI of a running surface — the DevSkyy dashboard (frontend/, localhost:3000) or SkyyRose theme pages.
• After a batch of UI edits, when a before/after visual pass is wanted prior to deploy.
• .wolf/OPENWOLF.md routes "Design QC" requests here (auto-trigger on matching requests).

When NOT to use:

• Component-framework selection or migration → reframe skill.
• Designing/building net-new UI → frontend-design / fashion-theme-architect.
• Post-deploy production verification → node scripts/verify-live-playwright.mjs spec gate or the deploy-and-verify agent. This skill reviews captured pixels; any severity claim about production requires its own [live] probe (bug-287).

Inputs

Required before starting. Absent input = STOP — never fabricate a review (fail-open is bug-230, ×6):

1. Capture CLI — command -v openwolf returns a path. Observed 2026-07-29: the global install at /Users/theceo/.npm-global/bin/openwolf was a broken symlink (package removed) — treat that as absent. When absent: say so, and do NOT review from memory or from the historical .wolf/designqc-archive/ shots. Fallback capture only if a real target is reachable: the Playwright MCP screenshot tool ( / ).