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
ai-driven-apps: declare the boundary with app-creator (create vs drive/test) so the two skills never drift into duplicates
2 files changed
+10−4
page.json+2−4@@ -1,6 +1,6 @@ { "slug": "adom-ui-design",- "version": "1.3.4",+ "version": "1.3.5", "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). One adompkg install drops the whole set of skill files onto your container.", "dependencies": {},@@ -81,7 +81,5 @@ "label": "make this UI responsive for mobile", "prompt": "make this UI responsive for mobile" }- ],- "visibility": "public",- "org": "adom"+ ] }
skills/ai-driven-apps/SKILL.md+8@@ -92,6 +92,14 @@ genuinely drivable. - **Inside a webview, always use relative URLs.** A leading slash bypasses the proxy and hits the wrong origin. Every `fetch`, `href`, `src`, and CSS `url()` must be relative. +## Boundary with app-creator (do not blur it)++`adom/app-creator` owns CREATING the app: scaffolding, project layout, server + webview skeleton,+wiring the first commit. THIS skill owns everything after: SHOWING the app, DRIVING its front-end,+and RALPH-TESTING the UI until it is right. If you are adding "how to build/scaffold" content, it+goes in app-creator; if you are adding "how to drive/verify/test the UI", it goes here. Keeping the+line crisp is what stops the two skills drifting into contradictory duplicates.+ ## Related skills `app-creator` (scaffolding the app), `adom-screenshot` (the ralph loop and shotlog),