wp-page

WP Page — Page Template Generator

Generate complete page templates with associated ACF fields and CSS based on the page type.

Step 1: Parse Arguments

Parse $ARGUMENTS:

• First word = page type (required): blog, generic, legal, 404, search, embed, or custom
• Second word = name/slug (required for custom AND embed types)
• --provider <name> (used by embed) = sets the provider name; strip this flag and its value from the arguments before resolving the screenshot path, so it is never treated as the screenshot path
• Remaining words = screenshot path (optional)

If no type is provided, print an error:

Error: Page type is required.
Usage: /wp-page <type> [name] [screenshot-path]
Types: blog, generic, legal, 404, search, embed, custom
Examples:
  /wp-page blog
  /wp-page generic
  /wp-page legal
  /wp-page 404
  /wp-page search
  /wp-page embed home-search --provider "Showcase IDX"
  /wp-page custom pricing

Step 2: Read Project Context

Read .claude/CLAUDE.md to extract:

• Function prefix
• Theme slug
• Languages
• Theme directory path

Step 3: Generate by Type

CSS agent routing

Read Template: from .claude/CLAUDE.md. When Template: is tailwind, dispatch wp-tailwind; when it is basic, dispatch wp-css.

• basic → dispatch wp-css exactly as described below.
• tailwind → dispatch wp-tailwind in author mode instead, passing the page slug (which selects components/<slug>.css) and the block name. The agent reads skills/wp-tailwind-system/SKILL.md for the decision ladder. It writes utility classes into the markup and only adds @apply rules where the ladder demands them. It must never write assets/css/styles.css.

Dispatch exactly one of the two, never both.

Every tailwind dispatch opens its quoted prompt with this line, verbatim:

Mode: author

The quoted prompt it opens is the one under "The tailwind prompt body" below — not the quoted prompt at the dispatch site, which is the basic branch's and names assets/css/styles.css, the one file the tailwind path must never write.