Asset CleanUp stores its configuration in WordPress options prefixed wpassetcleanup_, along with per-post unload rules saved as postmeta entries on each piece of content. The global rules cover sitewide unloads (for example, Contact Form 7 scripts excluded from non-contact pages), regex exclusions, and the minify and combine toggles. Per-page rules live in postmeta keys like _assetcleanup_unload_styles and _assetcleanup_unload_scripts, listing which CSS and JS handles are disabled for that URL. SleekAI can read those values, so the bot's system message exposes global behaviour and per-URL exceptions.

That turns Asset CleanUp's per-page editor into a conversation. An editor asks why a specific post is loading a plugin script they thought was unloaded, the bot reads the post's _assetcleanup_unload_scripts postmeta and confirms whether the handle is in the unload list. A developer asks which global unload rules apply on this page, the bot reads the sitewide list and the page's overrides and returns the resolved view.

Multibot lets a public help bot run alongside the asset-rules admin one. Display conditions scope the admin bot to administrators inside wp-admin, so the unload rules never appear to public visitors. Conversation logging captures every question with model and origin page, so the team can audit which asset rules repeat and refine the global list.

Asset CleanUp's value proposition is precise asset control: unload a script sitewide, then re-enable it on the one URL that needs it, with regex and template rules for the long tail. That precision is the whole point of the plugin, and it is also why the configuration spreads across global options and per-page postmeta on every post and page. Editors and developers spend small slices of time clicking through the meta box on individual posts to confirm which assets are unloaded where.

SleekAI exposes both the global rules and the per-page postmeta as named variables, scoped to administrators via display conditions, with logs recording every conversation. Asset audits compress into a single chat, regression diagnosis after a plugin update becomes one question, and editors who do not own the Asset CleanUp configuration get plain-English answers about why a specific page is heavier than its siblings. Asset CleanUp still owns the unload logic; SleekAI is the read layer that makes the existing rules visible and conversational.