From 181212cb2dce0f9038acd99a1a9d19f040a19fba Mon Sep 17 00:00:00 2001 From: Paul Bakaus Date: Sun, 9 Aug 2026 15:35:07 -0700 Subject: [PATCH] Map polish's evidence and verify steps per platform (#550) * Map polish's evidence and verify steps per platform polish.md was the last command reference verifying through web-only vocabulary after #546 gave the pipeline its native leg. Three targeted mappings, following the in-file precedent new-work.md set (the classify-triage-polish-verify flow itself is platform-neutral, so no polish.native.md): - Evidence gathering: desktop and mobile sizes on the web; the shipped device classes on simulator, emulator, or hardware on native, per the platform reference's Verifying the build section. - Verify checklist layouts: phone and tablet size classes, both orientations where supported, on native. - Verify checklist "supported browsers": native has none, so the analogues are named (runtime warnings, dropped frames, supported OS versions). Assisted-by: Claude Code * fix: branch the verify checklist web-vs-native explicitly Copilot follow-up: the parenthetical style could read as both term sets applying on native. The two bullets now branch explicitly, and the shared items (console errors, layout shift, latency, image loading) stay unbranched since they apply everywhere. Assisted-by: Claude Code * fix: restore runtime warnings to the native verify branch greptile follow-up: the explicit-branch restyle dropped the runtime warnings requirement the parenthetical carried; folding it into "console errors everywhere" hid it behind web vocabulary. It is back as its own item in the native branch. Assisted-by: Claude Code --- skill/reference/polish.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/skill/reference/polish.md b/skill/reference/polish.md index d58ca3a49..1d2bfcff3 100644 --- a/skill/reference/polish.md +++ b/skill/reference/polish.md @@ -19,7 +19,7 @@ Fix the cause at the narrowest correct level. Ask when a binding system principl ## 2. Gather the evidence -Use the feature yourself at representative desktop and mobile sizes. Determine: +Use the feature yourself at the surface's representative sizes: desktop and mobile on the web; on a native platform (`ios` / `android` / `adaptive`), the shipped device classes on the simulator, emulator, or hardware, captured per the platform reference's Verifying the build section. Determine: - whether the path is functionally complete; - the intended quality bar and time available; @@ -86,10 +86,10 @@ Do not perfect one corner while leaving the rest below the same quality bar. Walk the complete path again with mouse, keyboard, and touch where applicable. Check: -- mobile, intermediate, and wide layouts; +- mobile, intermediate, and wide layouts on the web; phone and tablet size classes in both supported orientations on native; - loading, empty, error, success, disabled, long-content, and missing-content states; - zoom, contrast, focus, semantics, and screen-reader names; -- console errors, layout shift, interaction latency, image loading, and supported browsers; +- console errors, layout shift, interaction latency, and image loading everywhere; supported browsers on the web; supported OS versions, runtime warnings, and dropped frames on native; - agreement with DESIGN.md, neighboring features, and the user's scope. Follow the quality guidance supplied by `context.mjs` and hooks, then run any other relevant QA commands. Context requests a manual scan only when no automatic detector is active; never add another detector pass. Fix real defects and document only narrow intentional exceptions. A clean scan does not replace visual judgment.