WordPress Headless and WPGraphQL Skill

Overview

Systematic review guidance for headless WordPress projects that expose content through WPGraphQL or adjacent APIs. Core principle: the schema should reflect durable content boundaries and predictable frontend needs, while auth, preview, caching, and build pipelines must stay explicit about trust boundaries and invalidation rules.

When to Use

Use when:

• Reviewing WPGraphQL-powered themes, plugins, or headless integrations
• Auditing custom schema extensions and resolver code
• Reviewing frontend data-fetching patterns for WordPress content
• Planning preview, draft, auth, or revalidation flows
• Checking build pipelines, webhook invalidation, or persisted-query setups