Expand description
The Cybercore theme engine: versioned theme documents, validation, contrast reports, built-in and user theme catalogs, selection, and CSS.
Existing palette files remain the built-in source of truth. Custom
themes use ThemeDocument and live under the user’s Cybercore config
directory, so consumers can load them without rebuilding their binary.
Structs§
- Appearance
Contrast Check - Contrast
Check - Contrast
Report - Design
Tokens - Shared typography, density, corners, and motion settings. These are deliberately enums/allowlisted values so imported themes cannot inject arbitrary CSS into an application’s page.
- Pack
Conflicts - Pack
Import Report - Theme
Catalog - Theme index with embedded built-ins and optional custom documents. In-memory operations never read environment variables or access the filesystem.
- Theme
Document - A saved theme, portable as JSON and independent of a specific app.
- Theme
Entry - Theme
Metadata - Theme
Pack Document - A portable bundle of themes that can be shared and installed together.
- Theme
Pack Metadata - Theme
Quality Report
Enums§
- Appearance
- Corners
- Density
- Motion
- Pack
Conflict Policy - What to do when an imported pack contains IDs already in the catalog.
- Theme
Error