critique

<!-- HARNESS MIRROR — do not edit here. Canonical source: skills/ or commands/. After editing source, copy into cli/assets/<harness>/ and repo-root harness mirrors. --> **Context:** this sub-skill is one lens of the broader `ui-craft` skill. If the `ui-craft` skill is also installed, read its SKILL.md first for Discovery + Anti-Slop + Craft Test, then apply the specific lens below. Critique the UI at `$ARGUMENTS` through a design lens. Load the `ui-craft` skill. ## Step 0: Visual capture (mandatory) Code-only review is insufficient. Every audit/critique starts with the surface as the user sees it. Try the following in order; use the first one available: 1. **Playwright MCP** — if `playwright` MCP server is available, use it. Capture full-page screenshots at three viewports: desktop (1280×800), tablet (768×1024), mobile (375×812). Capture dark mode if the app supports it. 2. **Browser DevTools / Chrome MCP** — second choice; same viewport set. 3. **Other browser automation** (`agent-browser`, `cursor-ide-browser`) — third choice. 4. **Ask the user** — last resort. If no automation is available, request screenshots from the user before proceeding. Be specific: - "Visual review needs screenshots. Please provide: - Full-page at 1280px (desktop) - Full-page at 768px (tablet) - Full-page at 375px (mobile) - Dark mode of each, if supported." Do not begin the review until visuals are captured or provided. State this explicitly to the user when no automati...