Adom UI Design System

@@ -1,6 +1,6 @@ {   "slug": "adom-ui-design",-  "version": "1.38.0",+  "version": "1.38.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": {},

@@ -155,6 +155,15 @@ 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. +  ⚠ **IDENTICAL CSS DOES NOT GIVE IDENTICAL COLUMNS.** The `30%` resolves against each app's+  OWN content box, so two apps running the same rule in the same pane measured **197.594px**+  and **192.198px** — a 5.4px spread caused by ~18px of difference in their page padding.+  If you want every dashboard's left column to land on the same number (and the point of a+  fixed contract is that it does), **the page padding is part of the contract**: the content+  region uses `padding: 20px 20px 24px` and the panel uses `padding: 18px 20px 20px`. An app+  carrying its own 16px page padding will be a few pixels off no matter how correct its grid+  rule is. Measure your own content box before blaming the clamp.+   ⚠ **`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@@ -163,6 +172,13 @@ instead of the boxes around them.   were in fact collapsing at the wrong width. **Grep for `@media` and read the conditions**,   then confirm by walking the widths. +  ⚠ **IF `grid-template-columns` COMES BACK AS THE SPECIFIED VALUE, YOU ARE MEASURING AN+  UNRENDERED PANE.** A computed read that returns the literal `"clamp(180px, 30%, 220px)"`+  rather than pixels — usually alongside heights of 0 and a `0x0` button — is not data. Stop,+  activate your tab by its `span.tab-name`, and measure again. Do not record the number. This+  trap has produced garbage readings for three separate threads, including the one writing+  this skill.+   **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