Wp Playground Development

WordPress Playground review and development guidance. Use when reviewing Blueprints, Playground JSON setup flows, `@wp-playground/cli` usage, embedded Playground demos, reproducible bug repros, docs examples, or when user mentions "WordPress Playground", "Blueprint", "playground.json", "run-blueprint", "build-snapshot", "embed Playground", or "zero-setup repro". Helps review Blueprint design, local Playground workflows, demo reliability, and reproducible WordPress environments.

116 stars 13 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add jorgerosal/wordpress-skills --skill wp-playground-development
Manual install
git clone --depth 1 https://github.com/jorgerosal/wordpress-skills.git /tmp/wordpress-skills
mkdir -p ~/.claude/skills
cp -r /tmp/wordpress-skills/claude-skills/wp-playground-development ~/.claude/skills/wp-playground-development

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# WordPress Playground Development Skill

## Overview

Systematic review guidance for WordPress Playground-based demos and reproducible environments. **Core principle:** Playground setups should be deterministic, portable, and easy to understand from the Blueprint or CLI entrypoint alone. Review covers Blueprint structure, local CLI usage, embedded demos, repro environments, and demo-specific WordPress configuration.

## When to Use

**Use when:**
- Reviewing a Blueprint JSON file
- Auditing docs that embed or link to Playground
- Building a zero-setup bug repro or demo
- Reviewing Playground CLI usage in local workflows or tests
- Designing a repeatable environment for blocks, plugins, or themes

**Don't use for:**
- General block or plugin review without Playground
- WP-CLI operations outside a Playground context
- Static analysis or CI setup alone

## Code Review Workflow

1. **Identify the Playground entrypoint**
   - Blueprint JSON
   - Playground CLI command
   - Embedded iframe or blueprint URL
   - Local docs or scripts used to reproduce an issue

2. **Check reproducibility first**
   - Explicit WordPress and PHP versions where needed
   - Steps are ordered and self-contained
   - No hidden manual steps outside the Blueprint/docs

3. **Review setup steps**
   - Theme/plugin install and activation
   - Login, site options, content seeding
   - File writes, copies, or mounts
   - Any `wp-cli` steps used inside the Blueprint

4. **Review developer ergonomics**
Read the full skill on GitHub

Details

Skill name
wp-playground-development
Path
claude-skills/wp-playground-development/SKILL.md
License
MIT
Repo updated
7 June 2026

FAQ

What does the Wp Playground Development skill do?

WordPress Playground review and development guidance. Use when reviewing Blueprints, Playground JSON setup flows, `@wp-playground/cli` usage, embedded Playground demos, reproducible bug repros, docs examples, or when user mentions "WordPress Playground", "Blueprint", "playground.json", "run-blueprint", "build-snapshot", "embed Playground", or "zero-setup repro". Helps review Blueprint design, local Playground workflows, demo reliability, and reproducible WordPress environments.

How do I install the Wp Playground Development skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add jorgerosal/wordpress-skills --skill wp-playground-development. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Wp Playground Development popular?

It lives in jorgerosal/wordpress-skills, which has 116 GitHub stars and 13 forks.

Related skills

Wp Accessibility Review

116

jorgerosal/wordpress-skills

WordPress accessibility review for themes, blocks, plugins, and admin interfaces. Use when reviewing keyboard navigation, focus behavior, semantic HTML, ARIA usage, form labeling, screen-reader support, contrast-related implementation issues, or when user mentions "accessibility review", "a11y", "keyboard navigation", "focus management", "screen reader", "ARIA", "semantic HTML", "accessible form", or "accessible block". Detects implementation-level accessibility issues in frontend output, block markup, admin screens, and interactive UI behavior.

Frontend & Design13

Wp Accessibility Review

116

jorgerosal/wordpress-skills

WordPress accessibility review for Codex. Use when reviewing semantic HTML, keyboard access, focus behavior, form labels, ARIA usage, and accessible interaction patterns in themes, blocks, plugins, and admin screens.

Frontend & Design13

Wp Acf and Content Modeling

116

jorgerosal/wordpress-skills

WordPress ACF and content modeling review. Use when reviewing Advanced Custom Fields usage, field group architecture, CPT and taxonomy design, options pages, repeaters, flexible content, block-bound field groups, meta storage patterns, or when user mentions "ACF", "field groups", "flexible content", "repeater", "custom post type design", "taxonomy design", "content model", "relationship fields", "ACF JSON", "options page", or "meta query performance". Detects schema drift, weak content modeling, brittle field naming, and performance issues in meta-heavy WordPress builds.

AI, LLMs & Agents13

Wp Playground Development

116

jorgerosal/wordpress-skills

WordPress Playground review for Codex. Use when reviewing Blueprints, Playground CLI usage, embedded Playground demos, reproducible WordPress setups, or zero-setup bug repro environments.

Software Development13

Wp Phpstan Review

116

jorgerosal/wordpress-skills

WordPress PHPStan review for Codex. Use when reviewing phpstan config, baseline strategy, CI analysis setup, WordPress stubs, or `szepeviktor/phpstan-wordpress` integration in WordPress projects.

Software Development13

Wp Plugin Development

116

jorgerosal/wordpress-skills

WordPress plugin architecture review and WordPress.org submission standards. Use when reviewing WordPress plugin code, auditing plugin architecture, preparing WordPress.org plugin submission, checking plugin best practices, analyzing custom post types, taxonomies, Settings API, hooks system, internationalization, or when user mentions "plugin review", "plugin development", "plugin best practices", "WordPress.org submission", "Plugin Check", "plugin headers", "activation hook", "deactivation hook", "uninstall", "custom post type", "taxonomy", "Settings API", "hooks", "actions", "filters", "i18n

Software Development13

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.