From 29e5b1494c0e8f8eaa583ad10657f8564031313c Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Sun, 9 Aug 2026 22:35:43 +0000 Subject: [PATCH] Sync generated provider output --- .agents/skills/impeccable/reference/polish.md | 6 +++--- .claude/skills/impeccable/reference/polish.md | 6 +++--- .cursor/skills/impeccable/reference/polish.md | 6 +++--- .gemini/skills/impeccable/reference/polish.md | 6 +++--- .github/skills/impeccable/reference/polish.md | 6 +++--- .grok/skills/impeccable/reference/polish.md | 6 +++--- .kiro/skills/impeccable/reference/polish.md | 6 +++--- .opencode/skills/impeccable/reference/polish.md | 6 +++--- .pi/skills/impeccable/reference/polish.md | 6 +++--- .qoder/skills/impeccable/reference/polish.md | 6 +++--- .rovodev/skills/impeccable/reference/polish.md | 6 +++--- .trae-cn/skills/impeccable/reference/polish.md | 6 +++--- .trae/skills/impeccable/reference/polish.md | 6 +++--- .vibe/skills/impeccable/reference/polish.md | 6 +++--- plugin/skills/impeccable/reference/polish.md | 6 +++--- 15 files changed, 45 insertions(+), 45 deletions(-) diff --git a/.agents/skills/impeccable/reference/polish.md b/.agents/skills/impeccable/reference/polish.md index b18014fe5..a9fd13935 100644 --- a/.agents/skills/impeccable/reference/polish.md +++ b/.agents/skills/impeccable/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. diff --git a/.claude/skills/impeccable/reference/polish.md b/.claude/skills/impeccable/reference/polish.md index a23c3887f..9db878697 100644 --- a/.claude/skills/impeccable/reference/polish.md +++ b/.claude/skills/impeccable/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. diff --git a/.cursor/skills/impeccable/reference/polish.md b/.cursor/skills/impeccable/reference/polish.md index f7ad2f44b..7af88f60c 100644 --- a/.cursor/skills/impeccable/reference/polish.md +++ b/.cursor/skills/impeccable/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. diff --git a/.gemini/skills/impeccable/reference/polish.md b/.gemini/skills/impeccable/reference/polish.md index f3cfc9c39..877a83c84 100644 --- a/.gemini/skills/impeccable/reference/polish.md +++ b/.gemini/skills/impeccable/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. diff --git a/.github/skills/impeccable/reference/polish.md b/.github/skills/impeccable/reference/polish.md index 7bdf7eb5c..0e115f981 100644 --- a/.github/skills/impeccable/reference/polish.md +++ b/.github/skills/impeccable/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. diff --git a/.grok/skills/impeccable/reference/polish.md b/.grok/skills/impeccable/reference/polish.md index c9c14dd4d..e5ff9c4b5 100644 --- a/.grok/skills/impeccable/reference/polish.md +++ b/.grok/skills/impeccable/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. diff --git a/.kiro/skills/impeccable/reference/polish.md b/.kiro/skills/impeccable/reference/polish.md index 391142469..fee049ce1 100644 --- a/.kiro/skills/impeccable/reference/polish.md +++ b/.kiro/skills/impeccable/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. diff --git a/.opencode/skills/impeccable/reference/polish.md b/.opencode/skills/impeccable/reference/polish.md index 6e4709750..d46ea12c9 100644 --- a/.opencode/skills/impeccable/reference/polish.md +++ b/.opencode/skills/impeccable/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. diff --git a/.pi/skills/impeccable/reference/polish.md b/.pi/skills/impeccable/reference/polish.md index fdb9ef52d..fb26c7fca 100644 --- a/.pi/skills/impeccable/reference/polish.md +++ b/.pi/skills/impeccable/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. diff --git a/.qoder/skills/impeccable/reference/polish.md b/.qoder/skills/impeccable/reference/polish.md index ae688924a..b392fe8fd 100644 --- a/.qoder/skills/impeccable/reference/polish.md +++ b/.qoder/skills/impeccable/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. diff --git a/.rovodev/skills/impeccable/reference/polish.md b/.rovodev/skills/impeccable/reference/polish.md index 21f624ece..b18f133ad 100644 --- a/.rovodev/skills/impeccable/reference/polish.md +++ b/.rovodev/skills/impeccable/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. diff --git a/.trae-cn/skills/impeccable/reference/polish.md b/.trae-cn/skills/impeccable/reference/polish.md index 5bbe2215d..56789b001 100644 --- a/.trae-cn/skills/impeccable/reference/polish.md +++ b/.trae-cn/skills/impeccable/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. diff --git a/.trae/skills/impeccable/reference/polish.md b/.trae/skills/impeccable/reference/polish.md index 2f5cdff3f..ffd4ea340 100644 --- a/.trae/skills/impeccable/reference/polish.md +++ b/.trae/skills/impeccable/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. diff --git a/.vibe/skills/impeccable/reference/polish.md b/.vibe/skills/impeccable/reference/polish.md index bad65d956..7e7d52c3f 100644 --- a/.vibe/skills/impeccable/reference/polish.md +++ b/.vibe/skills/impeccable/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. diff --git a/plugin/skills/impeccable/reference/polish.md b/plugin/skills/impeccable/reference/polish.md index a23c3887f..9db878697 100644 --- a/plugin/skills/impeccable/reference/polish.md +++ b/plugin/skills/impeccable/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.