a8cteam51

This skill should be used when the user asks to "build a block theme from this HTML", "turn these designs into a WordPress theme", "convert this Claude Design output to a block theme", "make a WordPress theme from these HTML files", "make this design into a real WordPress site", or otherwise requests turning static HTML/CSS/JS design files into a WordPress block theme on a local WordPress Studio site. Triggers when static HTML/CSS design files (or a directory of them) are supplied alongside any HTML→block-theme conversion intent.

Use when the user wants to extract images, assets, or design context from a Figma selection — e.g. "extract images from my current Figma selection", "pull the assets out of this Figma frame", "download the images from this Figma design", "grab the design context for this node". Connects directly to Figma desktop's local Dev Mode MCP server, downloads every referenced image (PNG/JPG/GIF/WEBP/SVG) plus a screenshot, and saves the design context to a local folder.

This skill should be used when the user asks to "convert this page", "migrate this page to blocks", "convert WPBakery on <URL>", "rewrite this page as Gutenberg", or otherwise requests an in-place WPBakery→Gutenberg conversion of a single post or page on a local WordPress Studio site. Triggers when a page URL is supplied alongside any WPBakery→Gutenberg conversion intent.

Converts an existing local WordPress Studio site's wp-content directory into a fresh clone of a GitHub repo while preserving the site's local runtime data (uploads, SQLite database, db.php drop-in, sqlite-database-integration mu-plugin, and all installed plugins and themes). Use when the user asks to "set up git on an existing site", "make this site's wp-content a git repo", "swap wp-content for <repo> on an existing site", "git-ify my Studio site's wp-content", "back the existing site with this repo", "point my local site at <repo>", "clone <repo> into an existing site without losing my uploads/database/plugins/themes", or describes any variant of converting an already-working local Studio site to be backed by a git repo. For brand-new sites with no local data to preserve, use clone-new-site instead.

Scaffolds a brand-new local WordPress Studio site from a GitHub repo by downloading WordPress, using the cloned repo AS wp-content, and creating a Studio site via the studio CLI. Use when the user asks to "set up a new Studio site", "scaffold a Studio site from <repo>", "spin up a local WordPress for <repo>", "create a Studio site using <github url>", "install WordPress with this repo as wp-content", "clone <repo> into a fresh WordPress install", "get a new Studio site running with <repo>", "bootstrap a WordPress site from <repo>", "stand up a local WP site with wp-content from <repo>", or describes any variant of bootstrapping a new local WP Studio site whose wp-content comes from a specific repo. For converting an existing local site's wp-content into a git clone (preserving uploads/database), use clone-into-existing-site instead.

Security review a WordPress plugin by slug, URL, or current directory.

Guides writing/running Atlantis tests and fixing CI issues across Codeception integration tests, PHP QA tools, and npm/composer workflow stability.

Guides work on Atlantis plugin PHP architecture including bootstrap flow, module lifecycle, settings model, and activation behavior. Use when adding/changing modules, plugin initialization, or shared helper patterns.

Guides Autoupdates module work including schedule windows, rollout delays, per-plugin filter toggles, and legacy Plugin Autoupdate Filter compatibility. Use when changing autoupdate behavior or related admin UI.

Guides work on Atlantis Colophon module, including credits rendering, shortcodes, and customization filters.

Guides work on Atlantis Messages module, including CRUD, storage, admin list/form flows, and location-based notice rendering.

Guides work on Atlantis Tracking module for WooCommerce, Sensei, and Bilmur integrations, including environment-based activation behavior.

Accessibility-focused QA testing against WCAG 2.2 Level AA standards

AEO / AI Mode QA — evaluates how AI tools discover, parse, and cite a website

Functional and design-focused QA testing across multiple pages and viewports

Performance-focused QA testing for load times, console errors, and network health

Guides work on Restrict Media File Access WordPress plugin PHP architecture including services, REST API, cron, settings, filesystem helper, and bulk operations. Use when adding or modifying services, REST endpoints, admin UI, settings, cron jobs, or understanding the plugin bootstrap and service pattern.

Guides work on the Restrict Media File Access file protection pipeline including protecting/unprotecting files, hash-based URL rewriting, file serving with range request support, access control, attachment tracking, and URL replacement in post content. Use when debugging access issues, modifying the protection flow, working with URL rewriting, or changing how files are served.

Guides writing and running tests for the Restrict Media File Access WordPress plugin using Codeception/wp-browser integration tests and Codeception E2E tests. Use when writing tests, debugging test failures, or adding coverage for new features.

Runs the PHPUnit test suite for the Query Loop Load More plugin. Use when the user asks to "run tests", "execute tests", "run the test suite", "verify tests pass", "run phpunit", or when validating changes before commit/PR.

Prepares a new release of the Query Loop Load More WordPress plugin. Use when the user asks to "bump version", "prepare release", "cut a release", "update changelog for release", or when releasing a new plugin version to WordPress.org or GitHub.