SleekByte 2.0Claude Code terminal, Git history, SCSS and more
The agentic code snippets plugin for WordPress
Write PHP, CSS, SCSS and JavaScript snippets as files, checked before they are saved and previewed before they go live. Let the assistant explain, fix and edit them, then export any selection as a standalone plugin.
Operate SleekByte from the terminal
Everything SleekByte does in a script belongs to a first-class command surface under wp sleek byte. Structured JSON output, safe destructive operations, and WordPress-native multisite behavior come as standard.
You design in the admin like always. Provisioning, refreshing, and verifying move to the terminal, where a person, a deploy script, or a coding agent can run them and trust the exit code.
CLI referencewp sleek byte
WP-CLI
# Snippets
wp sleek byte snippet list --format=json
# Files and checks
wp sleek byte test --snippet=my-snippet
# Errors and export
wp sleek byte errors list my-snippet
# Exports a snippet as a standalone plugin and prints the output path
wp sleek byte export <id>
# Writes a file, creating parent folders as needed
wp sleek byte file update <path>
Everything lives in your filesystem
Each snippet is a folder of ordinary files with a snippet.json beside them, stored in wp-content/uploads/sleek-byte rather than the database. Every PHP, CSS, SCSS and JavaScript file inside it loads automatically, so a snippet can be copied, versioned and deployed like any other code.
A few configuration examples:
Build features, not fragments
Traditional snippet plugins force you to manage CSS, JavaScript, and PHP separately. A SleekByte snippet keeps a complete feature with all its files in one folder, and per-file options give each file its own context: the front end, wp-admin or the block editor. Your snippets work like mini plugins.
Traditional Plugins 😭
CSS snippet for button styles
PHP snippet for user redirects
JavaScript snippet for animations
HTML snippet for custom layouts
Admin CSS snippet for dashboard tweaks
SleekByte 🤩
Custom login system
WooCommerce checkout
Dashboard improvements
Block editor enhancements
Performance optimizations
One config to rule them all
Every snippet’s snippet.json declares where and when its files load: the contexts, the hook PHP runs on, environments, a schedule and conditions. Edit it as a file in the editor, or through Snippet configuration, which writes the same file into the draft, so your configuration stays plain JSON you can read, copy and version.
Looks familiar? If you have worked with WordPress blocks, you will recognize this pattern. Like block.json, snippet.json keeps the declaration beside the code, so loading is declared, not coded.
Fine-tune when your snippets run
Conditions decide on each request whether the files load: the user and their role, the page WordPress shows, the device and browser, the date and time, the request and any option. A snippet loads when any group of conditions matches, and a schedule limits it to a period and to recurring times.
In Admin
WordPress admin area
Time of Day
Hour-based targeting
User Agent
Browser string matching
Is 404
Error pages only
Is Search
Search results pages
Day of Week
Weekday based rules
Is Front Page
The homepage only
Logged In
Authenticated visitors
User ID
Target specific users
Is Attachment
Media attachment pages
User Role
Filter by user role
Is Page
Static pages only
Is Multisite
Multisite networks only
Post Type
Filter by content type
Device Type
Mobile, tablet, desktop
Query String
URL parameter matching
Is Feed
RSS and Atom feeds
Is Main Site
Network main site only
Browser Version
Specific browser versions
Is Single
Single posts only
Is Archive
Archive pages only
IP Address
Visitor IP matching
Referrer
Traffic source rules
Is Home
The blog index
Code editing that feels joyful
A full code workspace lives in your WordPress admin: files open in tabs with PHP errors, change marks and search and replace across files. Everything you change is a draft until you save, and the preview runs that draft on the front end first.
Preview drafts on the front end
The preview opens beside the editor and runs your unsaved draft on the site, renewed each time your PHP passes the check.
PHP checked before saving
Every changed PHP file is parsed for syntax errors about a second after you stop typing, and Save refuses while one is broken.
Find any file
Filter the file tree to reach any file of any snippet in a few keystrokes.
Right-click menu
Add files and folders, create a snippet, jump to a PHP error or delete, right from the file tree.
Every change is a draft
Changed lines and files are marked until you save, so nothing runs on the site before you choose Save.
When a saved snippet fails, its error log records what it raised, three fatal errors in an hour stop it from loading, and safe mode turns every snippet off while you repair the site.
The runtime error log
While a snippet’s PHP file is being loaded, Byte records the warnings, notices, deprecations and errors it raises in the snippet’s runtime log.
When a snippet stops itself
A snippet whose log holds three fatal errors from the last hour stops loading until the log is cleared or the oldest of those errors is more than an hour old.
Safe mode
Stop every snippet for your own requests for an hour while you repair the site, or for every request with the SLEEK_BYTE_DISABLE constant.
Search across all your files
Search and replace works across the files of your snippets: find every match, see the files it sits in, and replace them all in one step, as a draft you review before you save.
Build with SleekByte, deploy without it
Export any selection of snippets as an ordinary WordPress plugin that runs them without SleekByte, for a site where Byte is not installed or for code that should ship as its own plugin. The plugin keeps each snippet as its own folder and loads it exactly as Byte does, with the same snippet.json, conditions, error log and safe mode.
Every save is a version
Turn on Git history with one filter and every save records a commit per snippet, in an ordinary repository inside the snippet’s folder. The history lists the commits, shows what each one changed and restores an earlier version as unsaved changes.
Intelligent help, right where you code
The workspace assistant opens beside Byte. It explains a snippet, finds a problem and edits the files of the open workspace, and it runs Byte’s WP-CLI commands. Its edits are drafts like your own, checked and previewed before anything runs, and it asks before it writes a file, creates a snippet or enables one.
Write snippets from a description
Describe what you need, and the assistant writes the files and their snippet.json as a draft for you to review and save.
Fix errors in place
Hand it a PHP error, and it edits the file, checks the PHP again and refreshes an open preview.
Ask about your snippets
It reads the open workspace, its files, unsaved changes and PHP errors, and answers about the snippets you have.
One set of keys for every Sleek plugin
The assistant uses the AI provider keys in Settings, not keys of its own. Enter a key for OpenAI, Anthropic, Google or OpenRouter once: it is stored encrypted and never shown again, and every SleekWP plugin on the site uses the same keys. Requests go from your site to the provider you choose.
What’s coming next
Planned SleekByte features live on the public roadmap, which shows what is planned, in progress and shipped, ranked by customer votes.
FAQ
What is SleekByte?
SleekByte runs the code snippets you write, PHP, CSS, SCSS and JavaScript, without a child theme or edits to plugin files. Each snippet is a folder of ordinary files with a snippet.json that says where and when they load. PHP is checked before it is saved, and a draft can be previewed on the front end before it goes live.
Where are snippets stored?
In wp-content/uploads/sleek-byte, one folder per snippet, as ordinary files beside a snippet.json. You can copy, version and deploy them like any other code.
How does snippet.json work?
It declares where and when a snippet’s files load: the contexts, the hook PHP runs on, environments, a schedule and conditions, for the whole snippet or per file. Edit it in the editor like any other file, or through Snippet configuration in the workspace, which writes the same file.
Can I preview a snippet before it goes live?
Yes. The preview opens beside the editor and shows the site’s front end with the unsaved draft running in place of your saved snippets. The draft runs only for you and for site managers; anyone else who opens the address sees the site as it is.
Does SleekByte check for errors?
Yes. Before saving, the workspace parses every changed PHP file for syntax errors and refuses to save while one is broken. The check does not run the code, so an error that only happens at run time passes it; the preview and the snippet’s error log show those.
What if a snippet breaks my site?
A snippet that hits three fatal errors in an hour stops loading on its own. To stop every snippet at once, add ?sleek-byte-safe-mode=1 to any address while logged in as an administrator.
Can I keep a version history?
Yes. With the sleekByte/snippets/git filter on, every save records a Git commit per snippet. Git history in the workspace shows what each commit changed and restores an earlier version as unsaved changes.
Can I export my snippets to work without SleekByte?
Yes. Any selection of snippets exports as an ordinary WordPress plugin that runs them without Byte, from the workspace or with wp sleek byte export. The plugin loads its snippets exactly as Byte does, with the same snippet.json keys, conditions, error log and safe mode.
What does the assistant do?
The workspace assistant opens beside Byte. It explains snippets, finds problems and edits the files of the open workspace as drafts you review before anything runs, and it can run Byte’s WP-CLI commands. It asks before it writes a file, creates a snippet or enables one.
Do I need my own API key for the assistant?
Yes. Enter a key for OpenAI, Anthropic, Google or OpenRouter once in Settings. Every SleekWP plugin on the site uses the same keys, and requests go from your site to the provider you choose, billed to that provider’s account. Keys saved in the earlier built-in AI chat move to Settings once.
Can I manage snippets from the terminal?
Yes. wp sleek byte lists, creates, enables, disables and deletes snippets, writes files, runs the PHP check, reads and clears error logs and exports plugins, for a deploy script, a CI pipeline or a coding agent.
What does SleekByte need?
PHP 8.2 or later and WordPress 6.5 or later.
Do I need a license key?
No. SleekByte works without one. A license key from sleekwp.com turns on updates: enter it on the License page under SleekWP > Byte, or define SLEEK_BYTE_LICENSE in wp-config.php.
Pricing
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
…or get the Bundle Deal
and save €250
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
SleekAI
SleekByte
SleekMotion
SleekPixel
SleekView
SleekRank
SleekTrack