wordpress-router

Classify WordPress codebases and route them to domain-specific workflows.

12|9|Updated Oct 23, 2025
One-click install
npx skills add https://github.com/jnealey88/designsetgo --skill wordpress-router-jnealey88
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wordpress-router
Source: https://github.com/jnealey88/designsetgo/tree/main/.claude/skills/wordpress-router
Command: npx skills add https://github.com/jnealey88/designsetgo --skill wordpress-router-jnealey88

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Classify WordPress codebases (plugins, themes, block themes, Gutenberg blocks, and WP core checkouts) and route to the correct workflow/skill, enabling rapid, context-aware actions.

Core Features & Use Cases

  • Detect repository kind (plugin, theme, block theme, WP core checkout, or full site) from code structure and key files.
  • Route user intent to the appropriate domain skill(s) (blocks, theme.json, REST API, WP-CLI, performance, security, testing, release packaging) and apply guardrails.
  • Provide a deterministic triage workflow and recommended commands to bootstrap builds, tests, and deployments, with a clear escalation path.
  • Use examples to illustrate routing decisions in real projects (e.g., a repo with block.json and Gutenberg blocks routes to wp-block-development workflow).

Quick Start

Run the project triage script at the start of a WordPress task to classify the repo and route to the matching workflow.

Frequently Asked Questions about wordpress-router

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route a WordPress codebase to the correct development workflow?

To route a WordPress codebase, classify its repository structure to detect plugins, themes, block themes, or WP core checkouts. This triage process directs your project to the appropriate domain workflow like blocks, REST API, or WP-CLI with applied guardrails.

What is the best way to triage a WordPress repository before making changes?

Triage a WordPress repository by analyzing code structure and key files like block.json to determine the project type. This deterministic workflow ensures safe, consistent routing to matching skills before you execute builds or tests.

Can I use workflow routing for both WordPress plugins and block themes?

Yes, workflow routing supports WordPress plugins, themes, block themes, Gutenberg blocks, and WP core checkouts. It detects the repository kind from code structure and routes each type to the correct domain-specific skill.

Does WordPress codebase classification support WP-CLI and REST API tasks?

WordPress codebase classification supports WP-CLI and REST API tasks by routing user intent to the appropriate domain skill. It applies guardrails and provides recommended commands to bootstrap builds and deployments.

When should I run WordPress project triage during my development process?

Run WordPress project triage at the start of any task involving plugins, themes, or WP core checkouts. This ensures you select the appropriate workflow for performance, security, testing, or release packaging before making changes.

Why does my WordPress block development workflow need a routing step?

A routing step is needed because WordPress block development requires specific domain skills. Triage identifies repositories containing block.json and Gutenberg blocks, routing them to the wp-block-development workflow to ensure context-aware actions.