wordpress/agent-skills

wordpress-router

Use when the user asks about WordPress codebases (plugins, themes, block themes, Gutenberg blocks, WP core checkouts) and you need to quickly classify the repo and route to the correct workflow/skill (blocks, theme.json, REST API, WP-CLI, performance, secur…

Ver código-fonte

Como usar

  1. Copie o comando e verifique o pacote antes de instalar no seu ambiente de agente.
  2. Consulte no original as ferramentas, credenciais e ambientes necessários.
  3. Descreva os dados de entrada e a entrega esperada; confira a saída com as fontes.
npx skills add https://github.com/wordpress/agent-skills --skill wordpress-router

Antes de começar

  • A instalação não inclui assinatura de modelo, franquia API ou acesso aos seus arquivos.
  • Estrelas e instalações indicam atividade, não um teste independente de qualidade ou segurança.
Documento original do Skill

Renderizado do repositório de origem, preservando títulos, exemplos, código, tabelas, links e imagens.

WordPress Router

When to use

Use this skill at the start of most WordPress tasks to:

  • identify what kind of WordPress codebase this is (plugin vs theme vs block theme vs WP core checkout vs full site),
  • pick the right workflow and guardrails,
  • delegate to the most relevant domain skill(s).

Inputs required

  • Repo root (current working directory).
  • The user’s intent (what they want changed) and any constraints (WP version targets, WP.com specifics, release requirements).

Procedure

  1. Run the project triage script:
  • node skills/wp-project-triage/scripts/detect_wp_project.mjs
  1. Read the triage output and classify:
  • primary project kind(s),
  • tooling available (PHP/Composer, Node, @wordpress/scripts),
  • tests present (PHPUnit, Playwright, wp-env),
  • any version hints.
  1. Route to domain workflows based on user intent + repo kind:
  • For the decision tree, read: skills/wordpress-router/references/decision-tree.md.
  1. Apply guardrails before making changes:
  • Confirm any version constraints if unclear.
  • Prefer the repo’s existing tooling and conventions for builds/tests.

Verification

  • Re-run the triage script if you create or restructure significant files.
  • Run the repo’s lint/test/build commands that the triage output recommends (if available).

Failure modes / debugging

  • If triage reports kind: unknown, inspect:
  • root composer.json, package.json, style.css, block.json, theme.json, wp-content/.
  • If the repo is huge, consider narrowing scanning scope or adding ignore rules to the triage script.

Escalation

  • If routing is ambiguous, ask one question:
  • “Is this intended to be a WordPress plugin, a theme (classic/block), or a full site repo?”

Relacionados por tarefa

do mesmo repositório

Mais Skills

Todos os Skills
wordpress
Oficial

wp-plugin-development

Use when developing WordPress plugins: architecture and hooks, activation/deactivation/uninstall, admin UI and Settings API, data storage, cron/tasks, security (nonces/capabilities/sanitization/escaping), and release packaging.

Instalações / 1h
1
GitHub Stars
2,4 mil
Atualizado
16 de nov.
wordpress
Oficial

wp-project-triage

Use when you need a deterministic inspection of a WordPress repository (plugin/theme/block theme/WP core/Gutenberg/full site) including tooling/tests/version hints, and a structured JSON report to guide workflows and guardrails.

Instalações / 1h
5
GitHub Stars
2,4 mil
Atualizado
16 de nov.
wordpress
Oficial

wp-block-development

Use when developing WordPress (Gutenberg) blocks: block.json metadata, registerblocktype(frommetadata), attributes/serialization, supports, dynamic rendering (render.php/rendercallback), deprecations/migrations, viewScript vs viewScriptModule, and @wordpress/scripts/@wordpress/create-block build and test workflows.

Instalações / 1h
4
GitHub Stars
2,4 mil
Atualizado
16 de nov.
wordpress
Oficial

wp-block-themes

Use when developing WordPress block themes: theme.json (global settings/styles), templates and template parts, patterns, style variations, and Site Editor troubleshooting (style hierarchy, overrides, caching).

Instalações / 1h
5
GitHub Stars
2,4 mil
Atualizado
16 de nov.