wordpress-creator

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.

Ir para a instalação

Repositório: Automattic/build-with-wordpress
Última atividade na origem: 12 de junho de 2026 às 01:04
Idioma detectado do SKILL.md: inglês
Estrelas: 7
Forks: 2

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/Automattic/build-with-wordpress --skill wordpress-creator

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

studio

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

2026-06-15

auditing

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

2026-06-12

block-creator

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

2026-06-12

Ver todas deste repositório

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.