JetStyleManager is Crocoblock's free Gutenberg companion that adds advanced style options to every Crocoblock block: typography presets, color schemes, spacing tokens, hover and active states. The settings are stored as block attributes inside the post content and, for site-wide presets, in wp_options under keys like jet_style_manager_presets. The Gutenberg block editor reads them on save; the frontend reads them on render.

SleekAI reads the same presets. When the chat widget loads, it inspects the active JetStyleManager preset for the page and applies the same color, typography, and spacing tokens to the chat bubble, input, and message UI. There is no separate widget skin to maintain. If you rebrand the site, the chat rebrands with it. The bot also has access to the JetEngine and WooCommerce data layer, just like every other SleekAI install, so the conversation itself stays grounded in live WordPress data.

Generic chatbots ship with a hard-coded look or a fixed set of theme tokens. Either you accept the default styling, which clashes with carefully tuned brand palettes, or you write custom CSS to override every selector inside an iframe widget. With SleekAI on a JetStyleManager site, neither is necessary. The widget reads the same option keys the rest of your blocks read, so visual consistency is automatic.

Sites that bother with JetStyleManager bother with it because brand consistency matters. The plugin exists to give Gutenberg the same kind of design system controls that Elementor and theme.json offer, with a friendly UI on top. Once a brand has invested in defining presets and rolling them across the block library, the last thing it wants is a third-party chat widget that ignores all of it.

Most chat widgets do exactly that. They ship in an iframe with their own fonts, their own colors, and their own padding. Even the ones that offer color customization expose a flat list of options that does not respect the layered token system JetStyleManager builds.

SleekAI is different because it lives in the same DOM as the rest of the site and reads the same option keys JetStyleManager writes to. The chat looks like part of the design system from day one. When the design team tweaks a preset, the chat moves with the rest of the site.

That removes a small but real friction point in adopting chat: the design team does not have to sign off on a separate visual treatment, and there is no ongoing maintenance to keep the chat in sync as the brand evolves. For agencies that ship JetStyleManager sites for clients, the integration also means one less plugin to brief on, one less ticket about chat colors, and one fewer surface that drifts from the brand over time.