UX wave U8. A repo-wide grep found loading UI hand-rolled everywhere: bespoke animate-pulse divs (notion hosts), raw Loader2 spans (preview-kit, admin-login), and a one-off docs body skeleton. New loading-states slice centralizes the pattern: LoadingSkeleton composes the shadcn Skeleton primitive with seven kind presets (text / card / list / table / form / page / block, count + columns overridable), and LoadingState composes the shadcn Spinner for in-flight work (inline / block / overlay). The page kind drops straight into a route loading.tsx. The site now eats its own dog food: DocsLoadingSkeleton keeps only the docs-shell chrome strips and delegates its body to kind="page"; the notion database/notes hosts swap pulse divs for kind="block"; preview-kit chat + composer and admin-login swap Loader2 for the Spinner primitive. Per-slice skeletons (icon-picker, notion editor) stay put — slice self-containment beats DRY across slice boundaries.

UX wave U7. Three compounding bugs killed the docs-sidebar tree: (1) category branches never toggled at all — SidebarMenuButton's tooltip prop wraps the button in a Tooltip root, and CollapsibleTrigger's asChild Slot merged its onClick onto that non-DOM wrapper, silently dropping the handler; (2) section chevrons never rotated — the group/section class sat on SidebarGroupLabel, which Radix never stamps data-state on, so the group-data-[state=open] selector could not match; (3) every section defaulted to open, rendering the whole catalog as one wall. Fixes: tooltip dropped from the trigger (sidebar is always full-width — it added nothing), group classes moved to the Collapsible roots that actually carry data-state, and only the section containing the active path starts open (navigation re-opens, manual toggles stick). Also: publish gate caught template-base/contact-form-resend still on the removed "email" category — moved to integrations.

The os-vps lint sweep (55 compiler-era react-hooks warnings → 0, rules promoted to error) lands in every lifted slice so both repos are line-identical outside seams again. Pattern conversions, no blanket disables: latest-ref mirrors move into effects, effect-driven resets become request/prop-keyed derived state (window-content, file-tree, use-konva-image, favicon, omnibar, remote-view, NumBox, waveform, spotlight), dynamic icon lookups render via createElement (useMemo does NOT satisfy static-components — probed), inline components hoist to module scope, the image-editor co-locates selection+mask in one state so the mask-exit invariant is atomic, history snapshots canUndo/canRedo at mutation time, and the inspector AI thread resets via key= remount. Bonus: the appshell AppIcon drops the hard iOS-glass sheen for a macOS Ventura treatment — soft full-height luminance ramp, hairline edge ring, layered drop shadow, shadowed glyph — mirrored in the app-store icon preview + card tiles.

UX wave U6. The catalog had editors, payments and an OS shell — but no data table, no 404 page, no footer. Five foundational slices land, all pure-UI, adapter-driven where state is involved, each with variant previews + smoke coverage (registry 37 → 42): data-table (generic DataTable<TData> on TanStack Table v8 + shadcn Table — sorting, search, pagination, row selection, column visibility; density/selectable axes), empty-states (six presets 404/500/403/no-results/empty-list/first-use on the shadcn Empty primitive + ErrorPage drop-in for app/not-found.tsx + error.tsx), marketing-chrome (config-driven MarketingHeader split/centered/minimal + mobile sheet menu, MarketingFooter columns/slim — the chrome every template hand-rolled), settings-page (Profile/Preferences/Notifications/Danger-zone shell over a two-method SettingsAdapter with optimistic save), notifications-center (bell + unread badge + popover/sheet inbox over a NotificationsAdapter; enhances appshell + dashboard-shell). CLI 1.12.0 carries them plus the U2 category enum + U3 alias resolution.

UX wave U5. Six shell-family slices (appshell, dashboard-shell, workspace-shell, admin-panel, admin, platform-admin) had no documented composition story — consumers couldn't tell which renders chrome and which mounts inside it. Now: /architecture gains a "Shell hierarchy — who composes whom" section (one rule: exactly one outer chrome, never nest two); admin-panel + platform-admin declare dashboard-shell as a peer with the mount direction in the reason; the admin slice's description states upfront that it is HEADLESS (nav-from-registry scaffold, no chrome); AdminShell's docblock spells out that it is the INNER section nav. Investigation note: AdminShell composing DashboardShell directly would nest two chromes — wrong by the hierarchy's own rule — so the DRY here is the contract, not a forced refactor.

UX wave U4. Docs pages had three header patterns (PageHeader, inline text-3xl copies, a custom text-lg bar on /build) and four page-spacing values. Now: PageHeader gains a compact bar variant (used by /build); /control-room, /audit-chain and /agents/[slug] swap their hand-rolled headers for PageHeader; page root spacing standardized to space-y-8; section h2 standardized to text-2xl (audit-chain, best-practice); DocCard bakes in p-4 default padding (twMerge keeps explicit overrides working); ShotThumbnail's aspect-[8/5] normalized to the same aspect-[16/10] string everyone else uses (identical 1.6 ratio, one spelling). Slice detail pages gain the prev/next arrows the layout detail header already had — both detail chromes now match.

UX wave U3. The seven landing-page section slices (blog-section, faq-section, portfolio-section, changelog-feed, feature-grid, testimonials-grid, pricing-page) were merged into landing-sections as kind-variants back in v0.2.0 — but their old slugs just errored in the CLI and 404'd on the site. Now: lib/content/slice-aliases.json is the SSOT; gen-manifest embeds it as manifest.aliases; the CLI's findEntry falls through to the alias with a "superseded by" warning, so npx rahman-resources add blog-section installs landing-sections; /slices/<old-slug> redirects to /slices/landing-sections; each old slice.json carries deprecated: "landing-sections" (new optional schema field). Also fixed: landing-sections was miscategorized as infra — it's content.

UX wave U2. Category order + labels were duplicated in four components and drifted: docs-sidebar showed "Ai"/"Ui" (naive capitalize), the /build picker was missing "os" entirely (OS slices invisible in the group list), the /slices tab row was missing OS too, and an empty "Storage" group sat in the sidebar. New lib/content/taxonomy.ts is the single source; all four consumers import it. Categories merged 12 → 8: payment+email → integrations, search+realtime → data, storage dropped (was empty). Moved: doku-payment, midtrans-payment, resend-newsletter, contact-form-resend → integrations; vector-search, broadcast-channel-sync → data. Sidebar label "Website templates" → "Templates — full apps" and both catalog heroes now state what they are NOT (layouts = single page shapes; templates = complete apps) — killing the layouts-vs-templates confusion.

UX wave U1. The catalog had two names for the same artifact: nav said Slices while the homepage hero, /docs intro, breadcrumbs, command palette and detail titles said Modules — and the live site description still said "kitab" (pre-2026-05-16 internal codename). All user-facing copy now says Slices; kitab → catalog/resources in site.ts, /build, /mcp and /directory copy. Dead code out: the orphaned /recipes/[slug] route (parent already redirects to /slices) and the never-used "template" layout category (union + LAYOUT_CATEGORY_TITLE entry).