Share the foundation
Stokes UI exports HTML rendering helpers, attributes, surfaces, stacks, buttons, navigation, and design tokens from one local package. The service also hosts a live studio with three layouts. The shared package has no external imports.
The visual vocabulary is specific: system fonts, flat surfaces, square joins, neutral separators, and slanted vertical edges. Those choices are encoded as reusable geometry and palette rules instead of being reinterpreted independently in every application.
Keep behavior separate
The package deliberately avoids changing forms, authorization, sessions, canvas drawing, or application data. A common appearance should not silently change a service's security or interaction model.
The studio includes an element extractor that can export HTML and CSS with the scoped foundation. Source roots, generated assets, and the typed manifest are kept consistent through a consolidation tool. The generated browser stylesheet has its own verification step.
The service stores no mutable server data, and its health response includes the deployed revision. The design package can therefore be reviewed independently of saved studio preferences.
Compatibility is part of design
Existing layout identifiers and saved browser preferences are retained across the rename. Older entry points redirect or re-export the shared implementation. The design system therefore includes migration behavior as well as appearance: interfaces can become more consistent without making established saved work unreadable.