Run any Skill in Manus with one click

wordpress-creator

Stars6

Forks0

UpdatedJune 9, 2026 at 22:50

Route WordPress build and audit requests to the right implementation path for a Studio-backed site. Use when the user wants WordPress work and it is not yet clear whether the task should be handled as site creation, theme work, a custom block, a plugin, or an audit.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Automattic

Automattic/wordpress-cursor-plugin

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Computer Occupations, All OtherComputer and Mathematical Occupations·SOC 15-1299

SKILL.md

readonly

name	wordpress-creator
description	Route WordPress build and audit requests to the right implementation path for a Studio-backed site. Use when the user wants WordPress work and it is not yet clear whether the task should be handled as site creation, theme work, a custom block, a plugin, or an audit.

WordPress Creator

Use this skill as the top-level decision maker for WordPress implementation and audit work.

Ownership

This skill owns:

choosing between site-creator, theme-creator, block-creator, plugin-creator, and auditing
picking the smallest fitting WordPress abstraction
handing execution off to the specialist skill once the approach is clear

Routing rules

Use site-creator when the user wants a new site, homepage, landing page, or a full site built from a brief.
Use theme-creator when the main work is theme templates, layout, styling, presentation, or a visual redesign.
Use block-creator when the main deliverable is an editor-insertable content block that can't be achieved with existing core blocks or aleady installed custom blocks.
Use plugin-creator when the request is reusable site functionality, admin/settings UI, REST endpoints, scheduled tasks, integrations, or backend behavior that should survive theme changes, and that can't be achieved with an existing plugin.
Use auditing when the main request is performance review, accessibility review, frontend QA, or optimization guidance on an existing site.
If the request could fit more than one path, choose the smallest abstraction that cleanly solves it.

Guardrails

Do not reach for a plugin when a theme or block would solve the request more directly.
Do not reach for a plugin when an existing installed, or well known plugin is available. For example, Set up an ecommerce system could be accomplished with the WooCommerce plugin.
Do not route pure presentation work into plugin-creator.
Do not route reusable backend behavior into theme-creator.
Once the path is clear, rely on the specialist skill instead of restating its workflow here.

More from this repository

same repository

studio

Automattic/wordpress-cursor-plugin

Use WordPress Studio for local WordPress development, preferring MCP and falling back to the Studio CLI when needed.

2026-06-156

auditing

Automattic/wordpress-cursor-plugin

Audit a Studio-backed WordPress site for performance, accessibility, and visible frontend quality issues, then recommend or validate improvements.

2026-06-126

theme-creator

Automattic/wordpress-cursor-plugin

Create a modern WordPress block theme.

2026-06-126

block-creator

Automattic/wordpress-cursor-plugin

Create, edit, build, and review a custom WordPress Gutenberg block plugin inside a Studio-backed site.

2026-06-096

design-previews-creator

Automattic/wordpress-cursor-plugin

Generate three parallel design preview options for a Studio-backed site and collect the user's preferred direction before theme implementation.

2026-06-096

plugin-creator

Automattic/wordpress-cursor-plugin

Create or update a custom WordPress plugin for site functionality that should not live in a theme or a block. Use when the user needs reusable behavior, admin/settings UI, hooks, REST endpoints, scheduled tasks, integrations, or server-side logic for a Studio-backed site.

2026-06-096

name	wordpress-creator
description	Route WordPress build and audit requests to the right implementation path for a Studio-backed site. Use when the user wants WordPress work and it is not yet clear whether the task should be handled as site creation, theme work, a custom block, a plugin, or an audit.

WordPress Creator

Use this skill as the top-level decision maker for WordPress implementation and audit work.

Ownership

This skill owns:

choosing between site-creator, theme-creator, block-creator, plugin-creator, and auditing
picking the smallest fitting WordPress abstraction
handing execution off to the specialist skill once the approach is clear

Routing rules

Use site-creator when the user wants a new site, homepage, landing page, or a full site built from a brief.
Use theme-creator when the main work is theme templates, layout, styling, presentation, or a visual redesign.
Use block-creator when the main deliverable is an editor-insertable content block that can't be achieved with existing core blocks or aleady installed custom blocks.
Use plugin-creator when the request is reusable site functionality, admin/settings UI, REST endpoints, scheduled tasks, integrations, or backend behavior that should survive theme changes, and that can't be achieved with an existing plugin.
Use auditing when the main request is performance review, accessibility review, frontend QA, or optimization guidance on an existing site.
If the request could fit more than one path, choose the smallest abstraction that cleanly solves it.

Guardrails

Do not reach for a plugin when a theme or block would solve the request more directly.
Do not reach for a plugin when an existing installed, or well known plugin is available. For example, Set up an ecommerce system could be accomplished with the WooCommerce plugin.
Do not route pure presentation work into plugin-creator.
Do not route reusable backend behavior into theme-creator.
Once the path is clear, rely on the specialist skill instead of restating its workflow here.