Astra stores its global theme options in a single serialized option called astra-settings, which holds typography presets, container widths, header builder rows, footer rows, and color palettes. Per-page layout overrides live in postmeta keys such as site-sidebar-layout, site-content-layout, ast-disable-sections, and ast-main-header-display. Astra Pro adds modules like Header Footer Builder, Mega Menu, Custom Layouts, and White Label, each toggled in another option key. Editors who want to know why one page hides the header have to dig through the post sidebar.

SleekAI exposes the astra-settings option, the ast_* postmeta keys, and the Astra Pro modules list as named variables. An editor on a post edit screen can type, why does the header not show on this page, and the bot reads ast-main-header-display together with the active Custom Layout overrides and answers with the specific override that hides it. Display conditions limit the bot to admins inside /wp-admin/ and a separate public-facing FAQ bot can run under multibot.

Generic chatbots cannot read serialized option values or know what an Astra Custom Layout is. They also cannot reason about Header Footer Builder rows. SleekAI's Wizard exposes any option or postmeta key in two clicks, including custom Astra hooks. Conversations log model name, tokens, and the page the question came from, so support teams see which Astra features actually confuse editors.

Astra Pro is one of the most flexible WordPress themes, which is exactly what makes it confusing for non-technical editors. The Customizer alone has dozens of panels. Header Footer Builder adds a drag and drop grid.

Custom Layouts add hooks that override pages. Module toggles change what the rest of the interface shows. Most editors only publish a handful of posts a week and never internalize where each setting lives.

They publish a page, see something off, click around, and either give up or guess. A chat interface compresses that workflow. The editor types a plain question, the bot reads the same astra-settings option and ast_* postmeta keys the theme itself reads, and the answer cites the exact override or row that produced the result.

That changes Astra from a theme editors tolerate into a theme they trust. It also means agencies stop fielding the same five Astra questions every week from client teams. SleekAI does not replace Astra.

It surfaces what Astra already knows, in a place editors are willing to use it.