Adom UI Design System

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

@@ -81,6 +81,14 @@ broken - is ALWAYS carried by the led tokens, never by a brand color alone. - **toasts** - bottom-center, success green / error red / info teal. - **pup-taskbar-progress** (bridge-side) - long AI work shows an indeterminate taskbar bar. +## Every layout change is tested in BOTH panel states++The newbie panel opens and closes, so your dashboard has TWO layouts, and the closed one is+where regular users live (see **newbie-panel**). Capture panel-open and panel-closed at+desktop and phone width before shipping any layout change, and judge each as a whole page.+The spacing under the header must be IDENTICAL in both states: if it changes, your page+padding is on the panel instead of on the content region.+ ## Ralph-test the contract  Open the dashboard cold from its dock icon next to kicad's, screenshot both, and LOOK: same

@@ -160,6 +160,32 @@ Found by chip-fetcher, the first app to convert: 2. **The demo button must fold WITH the panel.** A dismissed panel that leaves a stray demo    button behind looks like a bug. +## ⛔ RALPH-TEST THE LAYOUT IN BOTH STATES. EVERY TIME.++John's ruling, 2026-08-24: *"ralph test their layout with and without the newbie panel+showing cuz we can't have the layout look shitty when the newbie panel is closed."*++**The panel-closed layout is a FIRST-CLASS state, not a leftover.** Most users spend most of+their time there: the panel closes on dismissal, on graduation after three green launches,+and on the first AI-driven action, so the closed page is what a regular user actually looks+at day to day. A dashboard that only looks composed with the panel open is a dashboard that+looks broken to everyone past their first week.++Before you ship ANY change to a dashboard's layout, capture BOTH states and LOOK at each as+a whole page, not just at the gap you were fixing:++1. Panel OPEN, desktop width. 2. Panel CLOSED, desktop width.+3. Panel OPEN, 390px. 4. Panel CLOSED, 390px.++In every one of the four, judge: is the spacing under the header the same as the other+state, does the first content block sit at the page's normal padding rather than jammed or+floating, is anything orphaned (a stray heading, a lone divider, a control that belonged to+the panel), does the app's own content fill the width it just gained, and does the header+toggle correctly show the state you are in.++Toggle it live at least once rather than testing two separately-loaded pages: closing the+panel must not shift anything except the panel's own footprint.+ ## Ralph-test  At 1400px: panel spans the content width, two columns with the hairline between them, every