wordpress-router

To identify a WordPress codebase, inspect repository indicators like package.json, composer.json, block.json, theme.json, and wp-content. This classification determines whether the project is a plugin, theme, block theme, WP core checkout, or full site for accurate workflow routing.

The best way to route WordPress tasks is by running a project triage script that analyzes repository indicators. It classifies the codebase and applies decision-tree guidance to delegate work to specialized domain skills based on user intent and repository kind.

Yes, WordPress routing works with both block themes and classic themes. The detection mechanism inspects specific files like theme.json and block.json to distinguish between block themes, standard themes, plugins, and WP core checkouts before delegating.

You can classify a repository by running the project triage script, such as node skills/wp-project-triage/scripts/detect_wp_project.mjs. This script analyzes repository indicators to provide consistent starting points and minimize misrouting overhead at task kickoff.

WordPress projects get misrouted when repository indicators are ambiguous or missing. The triage script relies on detecting files like composer.json and wp-content to apply guardrails and route accurately, so ensuring these indicators exist prevents incorrect workflow delegation.