← Commit history

1.32.1: grep max-width is not a breakpoint list; grep @media and walk the widths

John Lauer ·8e15173566 ·1mo ago ·parent d46d58d
2 files changed +9−1
package.json+1−1
@@ -1,6 +1,6 @@ {   "slug": "adom-ui-design",-  "version": "1.32.0",+  "version": "1.32.1",   "type": "skill",   "description": "The Adom UI Design System plus a bundle of focused UI skills (tooltips, floating-windows, toasts, responsive-ui, app-shell, ai-driven-apps, clickable-paths, dark-default, input-feedback, settings-layout). One install drops the whole set of skill files onto your container, plus shared icon assets (the settings cog) so every Adom app draws the same glyph.",   "dependencies": {},
skills/newbie-panel/SKILL.md+8
@@ -109,6 +109,14 @@ instead of the boxes around them.   against the grid container, giving roughly 180px at a 620px container, ~200px at a 744px   dock pane, and 220px from 853px up. +  ⚠ **`grep max-width` DOES NOT GIVE YOU A BREAKPOINT LIST.** It folds ELEMENT widths+  (`.welcome{max-width:760px}`, `.vtable{min-width:760px}`) in with real `@media` queries,+  and the resulting list is wrong in both directions: it invents breakpoints that do not+  exist and can hide the ones that do. Two separate threads made exactly this mistake within+  an hour on 2026-08-25, one of them reporting a clean bill of health for a page whose pills+  were in fact collapsing at the wrong width. **Grep for `@media` and read the conditions**,+  then confirm by walking the widths.+   **AUDIT EVERY BREAKPOINT IN YOUR PAGE, NOT JUST THIS ONE.** Any `max-width` media query   that fires inside the **744-853px** pane band collapses something in the place users   actually work. nb found its own Layer 1 / Layer 2 comparison cards collapsing at 760px, so