Blueprint
94TrustedInstructions onlyWordPress Playground Blueprint file creation, validation, and debugging assistance.
What it does
This skill provides your assistant with the structural logic needed to author and refine WordPress Playground configurations. It ensures that your JSON files adhere strictly to the schema requirements while organizing plugin installation, file staging, and database constants into a clean, repeatable environment definition.
By installing this capability, you can generate complex setup sequences that define precisely how a site should initialize upon launch. It is designed to handle the intricate mapping of resources and execution pipelines required to transform a raw WordPress installation into a functional development or testing instance.
When it earns its place
Reach for it when…
Use this when you need to codify a repeatable WordPress environment for demonstration, local testing, or automated demos. It is ideal for defining custom plugin sets, specific configuration constants, and initial site settings that must persist across different user instances of Playground.
Look elsewhere when…
Do not use this for the actual execution or hosting of a live Playground site, as it focuses on the creation of the underlying configuration file. It is also unsuitable for managing existing live WordPress databases or handling complex infrastructure outside of the specific Playground JSON format.
What to say to use it
You never invoke a skill directly — the assistant picks it up when your request matches what it covers. These are the kinds of things that do that.
- help me draft a blueprint file for a new plugin demo
- can you check this blueprint json for syntax errors
- convert my site configuration into a playground blueprint
- how do I define a git resource in a wordpress blueprint
Install it
Install for all your projects
Copy the skill directory into your personal skills folder. Claude picks it up on its own the next time your request matches what it does — there is nothing to enable.
git clone --depth 1 --branch trunk https://github.com/WordPress/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/blueprint ~/.claude/skills/blueprintInstall for one project only
Put it in the project's own skills folder instead, so it can be committed and shared with everyone working on that repository.
cp -r /tmp/agent-skills/skills/blueprint .claude/skills/blueprintIf a skill of the same name exists in both places, the personal one wins.
Installing on Claude.ai or through the API instead? The full guide covers every surface.