Adom UI Design System

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

@@ -104,6 +104,17 @@ instead of the boxes around them.   the band. Your app's content breakpoints are yours to choose, but a threshold sitting   inside the band is almost certainly an accident rather than a decision. +### Let the PAGE tell you how wide it really is++kicad's idea, and the cure for the class of bug that hid 744px from six apps at once: give+your dashboard a `GET /api/viewport` that reports its OWN `window.innerWidth`,+`scrollWidth`, `overflowX` and `devicePixelRatio` back to whoever asks.++Then "how wide is the user's pane" stops being an assumption you carry and becomes a fact you+can fetch, and horizontal overflow reports itself instead of waiting to be noticed. It also+gives you an attributable answer: a width you measured through your own page in the user's ah+is evidence, where a width you assumed is not.+ ### The capture matrix  Six frames, not four (nb's, and better than what this skill asked for):

@@ -55,6 +55,27 @@ That prose is good - as EXPANSION. Tapping a pill opens its detail (popover on d sheet on touch) holding the full explanation, timestamps, and versions. The resting page shows pills only. +## ⛔ NEVER emit a next step for a state you have not established++An EMPTY cache is not a FAILED check. Project Manager's first pill row read+**"Wiki: signed out"** with a next step of "run adom-wiki auth" whenever its identity cache+was merely empty, which on a fresh server is always, because that cache only fills on the+first board-list fetch. A signed-in user was being told to re-authenticate by a red pill,+which is worse than showing nothing: it is a confident instruction to fix something that+was never broken.++So separate the three honestly:++| Situation | Colour | State text | Next step? |+|---|---|---|---|+| Not probed yet, or probe in flight | **gray** | `checking` | **NO** |+| Probed, and it works | green | the short state | no |+| Probed, and it genuinely failed | red / amber | the short state | **yes, the exact command** |++A gray pill costs a user nothing. A red pill with a wrong instruction costs them their trust+in every other pill on the row. If you cannot tell the difference between "not yet known" and+"broken", you must show gray.+ ## A red LED always carries its next step  The detail of any non-green pill leads with what to DO, exactly like the CLI's `Hint:`