Adom UI Design System

@@ -1,6 +1,6 @@ {   "slug": "adom-ui-design",-  "version": "1.3.0",+  "version": "1.3.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). One adompkg install drops the whole set of skill files onto your container.",   "dependencies": {},

@@ -23,10 +23,12 @@ holds many skill files. Bundle related skills as separate files in ONE repo. Nev wiki repo, or page, per skill.**  > **THE MISTAKE TO NEVER MAKE.** Do not create one wiki page per small skill. A skill as small as a-> tooltip spec is a file in a bundle, not its own repo. Spinning up a page per skill pollutes the-> owner's namespace, and wiki pages **cannot be hard-deleted**: a `DELETE` only soft-deletes and-> reserves the slug for good. If you catch yourself looping `POST /pages` to create many small-> skills, stop. You want one package with many files under `skills/`.+> tooltip spec is a file in a bundle, not its own repo. A page per skill clutters the owner's+> namespace, fragments install (the user has to find and install each one separately), and+> duplicates metadata. A stray page can be purged by its owner (`DELETE /api/v1/pages/<slug>?hard=true`,+> irreversible: row, repo, and tarballs gone, slug freed), but the right move is to never create it.+> If you catch yourself looping `POST /pages` to create many small skills, stop. You want one+> package with many files under `skills/`.  ## The bundle layout