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.

Aller à l'installation

Dépôt: Automattic/build-with-wordpress
Dernière activité de la source: 12 juin 2026 à 01:04
Langue détectée de SKILL.md: anglais
Étoiles: 7
Forks: 2

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.

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

La commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.

Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

SKILL.md

Instructions source · Aperçu en lecture seule

Retour à la recherche Retour à l’installation

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.