# wordpress-creator

Routes a WordPress build or audit request to site creation, theme work, a custom block, a plugin, or an audit.

Skill by Automattic. Category: Agent craft.

## Install

Project (for this project only):

```sh
npx skills add automattic/build-with-wordpress --skill wordpress-creator
```

Works with: Claude Code, Codex CLI, Cursor, Antigravity, Copilot CLI, opencode.

Global (for every project on this machine):

```sh
npx skills add automattic/build-with-wordpress --skill wordpress-creator -g
```

Works with: Claude Code, Codex CLI, Cursor, Antigravity, Copilot CLI, opencode.

## Tags

- Runs on your computer: It runs as a program on your machine, with your access.

## Security audits

- Gen Agent Trust Hub: Pass
- Socket: Pass
- Snyk: Pass

Installs: 2. Installs counted by skills.sh. [Open on skills.sh](https://www.skills.sh/automattic/build-with-wordpress/wordpress-creator)

## Source

[Open the source](https://github.com/automattic/build-with-wordpress/tree/HEAD/skills/wordpress-creator). Checked 2026-10-10. This summary may contain AI-generated text, so it can be wrong. Check the source before you rely on it.

## SKILL.md

````markdown
---
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.
````

- Previous: [theme-creator](https://syn4pse.dev/terminal/automattic-theme-creator.md)
- Next: [codeknit-parse](https://syn4pse.dev/terminal/codeknit-parse.md)
- [Terminal](https://syn4pse.dev/terminal.md)
- [Suggest a change](mailto:terminal@syn4pse.dev?subject=Terminal%20suggestion)
