Source snapshot bcc79fcc · Declared package version 6.0.4. This page combines the checked-in package guide and manifest; commands and runtime behavior were not executed in this review.
/hooks/useReducedMotion selects the web implementation under the browser
condition, including when react-native is also active. Native alone selects
AccessibilityInfo; Bun and Node retain the web implementation and its SSR fallback. Workspace source resolution follows the existing published condition order, and published export targets are unchanged.
@lssm-tech/lib.ui-kit-core is the shared foundation for the UI packages. It provides the low-level cn() utility plus the canonical shared interface layer used by ui-kit and ui-kit-web.
./interfaces is the shared compatibility layer for semantically matching ui-kit and ui-kit-web exports.
./command-theme is a narrow shared class contract for command palette/search-trigger color states. It exists only to keep native, web, and design-system command surfaces aligned on semantic theme tokens; it is not a general design-token bucket.
cn() composes clsx with tailwind-merge.
Changes here ripple into all UI packages even though the file count is small.
This package should stay boring and predictable.
./ssr/subject-scope carries an already resolved contract Subject through request-local async scopes. AuthOS supplies the subject at the request edge; web SSR reads the same scope. It performs no authentication or policy decision, returns undefined outside a scope, and belongs only in Node server bundles. Existing AuthOS SSR entry points keep their signatures and strict missing-context error. This additive lower port removes the UI package's upward domain dependency.
Compatibility guard
ui-kit-core also owns the registry used to compare the native and web UI kit lanes. Run the repo-level guard before adding or changing shared ./ui/* surfaces:
bash
bun run ui-kit:compat
The guard compares packages/platform/ui/ui-kit and packages/platform/ui/ui-kit-web exported ./ui/* subpaths, exported symbols, and shared prop-shape contracts. Existing drift is recorded in scripts/ui-kit-compatibility-baseline.json; new drift should be fixed or deliberately accepted by refreshing that baseline in the same reviewed change. Shared component contracts should be declared here first under ./interfaces, then consumed from both UI kit packages.
Layout contract split
./interfaces separates neutral wrapper semantics from directional stack semantics so the web and native lanes can migrate Box safely:
SharedBoxProps is the shared semantic wrapper contract. It intentionally carries only className today; consumers should not depend on Box for flex direction, default gap, or default alignment.
SharedFlexStackProps owns the cross-platform stack subset:
gap, align, justify, and wrap.
HStack and VStack should consume SharedFlexStackProps; new shared UI should pick one of them whenever direction matters.
SharedStackProps remains exported for compatibility while the staged Box neutral-default migration is underway.
Changing gap, align, justify, wrap, as, or the Box/stack split is a public compatibility decision. Update package docs, release capsules, and guard evidence in the same reviewed change.
When not to use this package
Do not use it for components.
Do not use it for design tokens.
Do not use it for router or link abstractions.
Related packages
@lssm-tech/lib.ui-kit
@lssm-tech/lib.ui-kit-web
@lssm-tech/lib.ui-link
Local commands
bun run lint:check
bun run typecheck
Graph & Timeline Primitives
@lssm-tech/lib.ui-kit-core now exports platform-agnostic graph and timeline hooks and interfaces — pure TypeScript, no React or react-native imports.
useAdaptiveGraphRenderer returns "svg" or "reactflow" based on a bounded node/edge threshold (default 300 nodes / 500 edges), enabling lazy-loading of GraphCanvasAdvanced in the web lane.
The compatible ownership proposal places the complete existing Annotation, SavedView, and GraphExport declaration families in UiKitCore under ./data-views/annotation, ./data-views/saved-view, and ./data-views/graph-export. Legacy imports remain forwards to those same declarations and documentation objects. Existing constants, fields, defaults, helper behavior and tests are preserved. Source and publication roots include their existing platform conditions and the explicit Node condition.
The proposal also binds UI consumers to existing canonical Core, Kernel and DesignCatalog families. Qualification requires fresh task-bound adoption, owning production, declaration consumers and affected tests; this source checkpoint does not claim that execution.
Declared capabilities.
Lib Ui Kit Core
Core UI primitives and utilities
Use it to
Adopt core ui primitives and utilities
Requires
TypeScript
Choose another boundary when
The @lssm-tech/lib.ui-kit-core package constraints do not match the target runtime or platform.
These are package-manifest entry points. Named symbols listed above come from the capability catalogue; this is not an exhaustive TypeScript symbol reference.
