skill
Adom UI Design System
Public Made by Adomby adom
How the AI builds and tests interfaces people love to use in Adom. Ships as one installable skill that bundles focused skills (tooltips, floating-windows, toasts, responsive-ui, app-shell, ai-driven-apps, clickable-paths).
← Commit history
1.25.1: test at your user's real pane width (a breakpoint bug hides between your test widths); installing needs a slot, publishing does not
3 files changed
+14−1
package.json+1−1@@ -1,6 +1,6 @@ { "slug": "adom-ui-design",- "version": "1.25.0",+ "version": "1.25.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/dock-dashboard/SKILL.md+7@@ -141,6 +141,13 @@ prompts panel at all; a pup capture published as though it were the ah view; and consecutive launch defects that were invisible in a developer's container and appeared only on a real box. +### Publishing is free; INSTALLING touches the user's machine++Publishing to the wiki affects nobody's running system. **Installing does**: `bridge_install`+and friends restart a bridge or a server on the user's desktop, and doing that under another+thread's live session looks exactly like that thread's own flake. So when several agents work+one machine, publish freely and treat INSTALL as the thing that needs a slot.+ ### And verify on the instance the DOCK runs, not the one you develop against There are usually TWO INSTALLS of your app: the copy you develop against (your cloud
skills/newbie-panel/SKILL.md+6@@ -87,6 +87,12 @@ instead of the boxes around them. surface is a guess.** Before you pick one, measure `window.innerWidth` inside the ah webview your card actually opens. + **And put YOUR USER'S ACTUAL PANE WIDTH in your test matrix.** A breakpoint bug is+ invisible to anyone whose test widths straddle it: pup ralph-tested at 1280px and 390px,+ which sit either side of John's 744px pane, so every frame it ever showed him was the+ collapsed fallback and nothing in its matrix could reveal that. Test at 744px (or whatever+ you measure), not only at the widths that are convenient to reason about.+ - At the narrow end of the band the left column may shrink to **180px** rather than collapsing; the demo button still fits on one line at that width.