SleekByte snippets target the languages WordPress runs directly: PHP, JS, CSS, and HTML. If a snippet needs SASS, the recommended pattern is to compile it as part of the theme build pipeline that already produces the CSS shipped with the rest of the site, and let the SleekByte snippet ship the compiled CSS file. The agent can scaffold the file structure and reference the compiled output, but in-snippet SASS compilation is not part of the runtime.

Gemini and OpenAI assist generate snippets in response to a prompt; the developer then pastes the result. SleekByte's agent operates on your snippet files directly: it reads the current code, modifies the files in place across multiple turns, calls tools to look up WordPress hooks and conditions, and uses the editor's line-by-line PHP error hints to fix errors without leaving the editor. Same starting point, very different working shape.

Yes. SleekByte's agent works with Anthropic, OpenAI, Google, and OpenRouter keys, so a Gemini or OpenAI key you already pay for can drive the agent. Claude is the default model the agent is tuned around, but provider selection is per-key and feature parity is the same across providers. The API spend is billed by the provider against your own account, not through SleekByte.

Not yet. Migration is a copy-paste flow today, accelerated by the agent: paste a CodeKit Custom Codes entry, ask the agent to import it into a new snippet folder, and verify the result with the preview URL. Automatic import for the major snippet plugins is on the roadmap. The copy-paste route is usually a one-afternoon job for a typical library, since the agent does the file-splitting and condition translation.

Inside your active theme, in a directory created and managed by SleekByte. Each snippet is a subdirectory containing PHP, JS, CSS, and HTML files as needed, plus a declarative snippet.json for hooks, conditions, and metadata. Because the files are theme assets, anything that already moves the theme between staging and production moves the snippets along with it.

The agent proposes changes; nothing executes until you save. You review the diff in the editor, the same way you would review a teammate's pull request, before committing. The Claude session itself runs on Anthropic's API through your own key, so the code path mirrors any other API integration you might already have on the site, with no Sleek-side server in the middle.

CodeKit Custom Codes stores snippets in the WordPress database. If you uninstall the plugin without migrating, the rows remain in the database but stop executing. The clean migration path is to copy each snippet into a SleekByte folder, verify it via the preview URL, deactivate the CodeKit entry, and only uninstall CodeKit once every active snippet has moved over and been signed off.

Yes. Any snippet folder can be exported as a standalone WordPress plugin from inside the SleekByte editor. That exported plugin keeps running even if SleekByte is removed, and it can be re-imported back into SleekByte later to resume editing. This is useful when a particular snippet needs to outlive the plugin on a specific site, or when shipping a feature to the WordPress plugin directory.