wp-skills 1.0.1 → 1.0.3

package/README.md

@@ -1,161 +1,101 @@
-# Agent Skills for WordPress
+# WordPress Team Skills
 
-**Teach AI coding assistants how to build WordPress the right way.**
+This skill pack helps WordPress teams (classic themes, block themes, and plugins): clear architecture, explicit guardrails, and verification-first workflows.
 
-Agent Skills are portable bundles of instructions, checklists, and scripts that help AI assistants (Claude, Copilot, Codex, Cursor, Antigravity IDE, etc.) understand WordPress development patterns, avoid common mistakes, and follow best practices.
+## Quick Install
 
-> **AI Authorship Disclosure:** These skills were generated using GPT-5.2 Codex (High Reasoning) from official Gutenberg and WordPress documentation, then reviewed and edited by WordPress contributors. We tested skills with AI assistants and iterated based on results. This is v1, and skills will improve as the community uses them and contributes fixes. See [docs/ai-authorship.md](docs/ai-authorship.md) for details. ([WordPress AI Guidelines](https://make.wordpress.org/ai/handbook/ai-guidelines/))
-
-## Why Agent Skills?
-
-AI coding assistants are powerful, but they often:
-- Generate outdated WordPress patterns (pre-Gutenberg, pre-block themes)
-- Miss critical security considerations in plugin development
-- Skip proper block deprecations, causing "Invalid block" errors
-- Ignore existing tooling in your repo
-
-Agent Skills solve this by giving AI assistants **expert-level WordPress knowledge** in a format they can actually use.
-
-## Available Skills
-
-| Skill | What it teaches |
-|-------|-----------------|
-| **wordpress-router** | Classifies WordPress repos and routes to the right workflow |
-| **wp-project-triage** | Detects project type, tooling, and versions automatically |
-| **wp-block-development** | Gutenberg blocks: `block.json`, attributes, rendering, deprecations |
-| **wp-block-themes** | Block themes: `theme.json`, templates, patterns, style variations |
-| **wp-plugin-development** | Plugin architecture, hooks, settings API, security |
-| **wp-rest-api** | REST API routes/endpoints, schema, auth, and response shaping |
-| **wp-interactivity-api** | Frontend interactivity with `data-wp-*` directives and stores |
-| **wp-abilities-api** | Capability-based permissions and REST API authentication |
-| **wp-wpcli-and-ops** | WP-CLI commands, automation, multisite, search-replace |
-| **wp-performance** | Profiling, caching, database optimization, Server-Timing |
-| **wp-phpstan** | PHPStan static analysis for WordPress projects (config, baselines, WP-specific typing) |
-| **wp-playground** | WordPress Playground for instant local environments |
-| **classic-theme-dev** | Classic theme architecture, template hierarchy, URL-to-template-hook mapping, refactoring |
-| **block-theme-dev** | Block theme architecture (`theme.json`, templates/parts, patterns), migration planning |
-| **frontend-wp** | CSS/SCSS architecture, JS behavior, WordPress enqueue/performance patterns |
-| **wp-dev-workflow** | Feature scaffolding, WordPress-focused code review, migration/backward compatibility |
-| **wpds** | WordPress Design System |
-
-## Quick Start
-
-### Install via npx (recommended)
+Install all skills into the current project:
 
 ```bash
-# Install into current project
 npx wp-skills install --dest=. --targets=codex,vscode,claude,cursor,antigravity
-
-# List available skills
-npx wp-skills list
 ```
 
-This installs from the published npm package without cloning this repository.
-
-### Install globally for Claude Code
+List available skills:
 
 ```bash
-# Clone agent-skills
-git clone https://github.com/WordPress/agent-skills.git
-cd agent-skills
-
-# Install all skills globally (available across all projects)
-node shared/scripts/skillpack-install.mjs --global
-
-# Or install specific skills only
-node shared/scripts/skillpack-install.mjs --global --skills=wp-playground,wp-block-development
+npx wp-skills list
 ```
 
-This installs skills to `~/.claude/skills/` where Claude Code will automatically discover them.
-
-### Install into your repo
+Install a single skill:
 
 ```bash
-# Clone agent-skills
-git clone https://github.com/WordPress/agent-skills.git
-cd agent-skills
-
-# Install into your WordPress project
-node shared/scripts/skillpack-install.mjs --dest=../your-wp-project --targets=codex,vscode,claude,cursor,antigravity
+npx wp-skills install --dest=. --targets=codex,vscode,claude,cursor,antigravity --skills=classic-theme-dev
 ```
 
-This copies skills into:
-- `.codex/skills/` for OpenAI Codex
-- `.github/skills/` for VS Code / GitHub Copilot
-- `.claude/skills/` for Claude Code (project-level)
-- `.cursor/skills/` for Cursor (project-level)
-- `.agent/skill/` for Antigravity IDE (project-level)
+Installed locations:
 
-### Install globally for Cursor
+- `.codex/skills/`
+- `.github/skills/`
+- `.claude/skills/`
+- `.cursor/skills/`
+- `.agent/skill/`
 
-```bash
-node shared/scripts/skillpack-install.mjs --targets=cursor-global
-```
+## Team Usage Flow
 
-This installs skills to `~/.cursor/skills/` where Cursor will discover them.
+1. Start with `wordpress-router` or `wp-project-triage` to classify repository context.
+2. Select the domain skill (theme, frontend, plugin/API, ops, review/migration).
+3. Provide explicit inputs: URL/page type, file scope, and compatibility constraints.
+4. Require explicit verification before merge or release.
 
-### Available options
+Prompt examples:
 
-```bash
-# List available skills
-node shared/scripts/skillpack-install.mjs --list
+- `Use wordpress-router and wp-project-triage, then choose the right skill for this repository.`
+- `Use classic-theme-dev to map URL -> template -> hook and implement the fix.`
+- `Use wp-dev-workflow for a WordPress-focused code review with security and performance findings.`
 
-# Dry run (preview without installing)
-node shared/scripts/skillpack-install.mjs --global --dry-run
+## Skill Catalog
 
-# Install specific skills to a project (e.g. Claude + Antigravity)
-node shared/scripts/skillpack-install.mjs --dest=../my-repo --targets=claude,antigravity --skills=wp-wpcli-and-ops
-```
+### Routing and triage
 
-### Manual installation
+- [wordpress-router](skills/wordpress-router/README.md)
+- [wp-project-triage](skills/wp-project-triage/README.md)
 
-Copy any skill folder from `skills/` into your project's instructions directory for your AI assistant.
+### Theme development
 
-## How It Works
+- [classic-theme-dev](skills/classic-theme-dev/README.md)
+- [block-theme-dev](skills/block-theme-dev/README.md)
+- [wp-block-themes](skills/wp-block-themes/README.md)
+- [wp-block-development](skills/wp-block-development/README.md)
 
-Each skill contains:
+### Frontend
 
-```
-skills/wp-block-development/
-├── SKILL.md              # Main instructions (when to use, procedure, verification)
-├── references/           # Deep-dive docs on specific topics
-│   ├── block-json.md
-│   ├── deprecations.md
-│   └── ...
-└── scripts/              # Deterministic helpers (detection, validation)
-    └── list_blocks.mjs
-```
+- [frontend-wp](skills/frontend-wp/README.md)
+- [wp-interactivity-api](skills/wp-interactivity-api/README.md)
+- [wpds](skills/wpds/README.md)
 
-When you ask your AI assistant to work on WordPress code, it reads these skills and follows the documented procedures rather than guessing.
+### Plugin, API, and capabilities
 
-## Compatibility
+- [wp-plugin-development](skills/wp-plugin-development/README.md)
+- [wp-rest-api](skills/wp-rest-api/README.md)
+- [wp-abilities-api](skills/wp-abilities-api/README.md)
 
-- **WordPress 6.9+** (PHP 7.2.24+)
-- Works with any AI assistant that supports project-level instructions
+### Tooling, ops, and quality
 
-## Contributing
+- [wp-wpcli-and-ops](skills/wp-wpcli-and-ops/README.md)
+- [wp-performance](skills/wp-performance/README.md)
+- [wp-phpstan](skills/wp-phpstan/README.md)
+- [wp-playground](skills/wp-playground/README.md)
+- [wp-dev-workflow](skills/wp-dev-workflow/README.md)
 
-**We welcome contributions!** This project is a great way to share your WordPress expertise—you don't need to be a coding wizard. Most skills are written in Markdown, focusing on clear procedures and best practices.
+## Recommended Team Bundles
 
-See [CONTRIBUTING.md](CONTRIBUTING.md) for details on how to get started.
+- `classic-theme-dev` + `frontend-wp` + `wp-dev-workflow`
+- `block-theme-dev` + `wp-block-development` + `wp-interactivity-api`
+- `wp-plugin-development` + `wp-rest-api` + `wp-abilities-api`
+- `wp-wpcli-and-ops` + `wp-performance` + `wp-phpstan`
 
-Quick commands:
+## Maintain and Validate
 
 ```bash
-# Scaffold a new skill
-node shared/scripts/scaffold-skill.mjs <skill-name> "<description>"
-
-# Validate skills
+# Validate the skill set
 node eval/harness/run.mjs
-```
 
-## Documentation
-
-- [Authoring Guide](docs/authoring-guide.md) - How to create and improve skills
-- [Principles](docs/principles.md) - Design philosophy
-- [Packaging](docs/packaging.md) - Build and distribution
-- [Compatibility Policy](docs/compatibility-policy.md) - Version targeting
+# List available skills from local repository
+node shared/scripts/skillpack-install.mjs --list
+```
 
-## License
+Related docs:
 
-Duke Dev
+- [docs/authoring-guide.md](docs/authoring-guide.md)
+- [docs/packaging.md](docs/packaging.md)
+- [docs/skill-set-v1.md](docs/skill-set-v1.md)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wp-skills",
-  "version": "1.0.1",
+  "version": "1.0.3",
   "description": "WordPress Agent Skills installer and packager",
   "license": "Duke Dev",
   "type": "module",

package/skills/block-theme-dev/README.md

@@ -0,0 +1,46 @@
+# Block Theme Dev
+
+## Purpose
+
+Use when building or migrating WordPress block themes using theme.json, templates/parts, patterns, and custom block integration.
+
+## Install this skill only
+
+Use npm package (recommended):
+
+```bash
+npx wp-skills install --dest=. --targets=codex,vscode,claude,cursor,antigravity --skills=block-theme-dev
+```
+
+Use local repository scripts:
+
+```bash
+node shared/scripts/skillpack-install.mjs --dest=../your-wp-project --targets=codex,vscode,claude,cursor,antigravity --skills=block-theme-dev
+```
+
+## When to use
+
+- Apply this skill when your task matches the scope in [SKILL.md](./SKILL.md).
+- Typical trigger prompt: `Use block-theme-dev to handle this task in my WordPress repo`.
+
+## Inputs to provide
+
+- Repository root (or target project path).
+- Exact task goal (feature, refactor, debugging, migration, or review).
+- Constraints: WordPress/PHP versions, plugin/theme boundaries, timeline/risk constraints.
+
+## Expected output
+
+- Clear implementation plan tied to project context.
+- File-level changes or command steps with verification.
+- Guardrails and risks called out before high-impact operations.
+
+## Team guardrails
+
+- Prefer existing repo conventions and tooling over introducing new patterns.
+- Avoid destructive DB/content operations without explicit approval.
+- Keep backward compatibility visible for production WordPress sites.
+
+## References
+
+- Main instructions: [SKILL.md](./SKILL.md)

package/skills/classic-theme-dev/README.md

@@ -0,0 +1,46 @@
+# Classic Theme Dev
+
+## Purpose
+
+Use when building, refactoring, or debugging classic WordPress themes with template hierarchy, hooks, and URL-to-template mapping.
+
+## Install this skill only
+
+Use npm package (recommended):
+
+```bash
+npx wp-skills install --dest=. --targets=codex,vscode,claude,cursor,antigravity --skills=classic-theme-dev
+```
+
+Use local repository scripts:
+
+```bash
+node shared/scripts/skillpack-install.mjs --dest=../your-wp-project --targets=codex,vscode,claude,cursor,antigravity --skills=classic-theme-dev
+```
+
+## When to use
+
+- Apply this skill when your task matches the scope in [SKILL.md](./SKILL.md).
+- Typical trigger prompt: `Use classic-theme-dev to handle this task in my WordPress repo`.
+
+## Inputs to provide
+
+- Repository root (or target project path).
+- Exact task goal (feature, refactor, debugging, migration, or review).
+- Constraints: WordPress/PHP versions, plugin/theme boundaries, timeline/risk constraints.
+
+## Expected output
+
+- Clear implementation plan tied to project context.
+- File-level changes or command steps with verification.
+- Guardrails and risks called out before high-impact operations.
+
+## Team guardrails
+
+- Prefer existing repo conventions and tooling over introducing new patterns.
+- Avoid destructive DB/content operations without explicit approval.
+- Keep backward compatibility visible for production WordPress sites.
+
+## References
+
+- Main instructions: [SKILL.md](./SKILL.md)

package/skills/frontend-wp/README.md

@@ -0,0 +1,46 @@
+# Frontend WP
+
+## Purpose
+
+Use when implementing WordPress frontend CSS/SCSS architecture, JavaScript behavior, and asset loading/performance across classic and block themes.
+
+## Install this skill only
+
+Use npm package (recommended):
+
+```bash
+npx wp-skills install --dest=. --targets=codex,vscode,claude,cursor,antigravity --skills=frontend-wp
+```
+
+Use local repository scripts:
+
+```bash
+node shared/scripts/skillpack-install.mjs --dest=../your-wp-project --targets=codex,vscode,claude,cursor,antigravity --skills=frontend-wp
+```
+
+## When to use
+
+- Apply this skill when your task matches the scope in [SKILL.md](./SKILL.md).
+- Typical trigger prompt: `Use frontend-wp to handle this task in my WordPress repo`.
+
+## Inputs to provide
+
+- Repository root (or target project path).
+- Exact task goal (feature, refactor, debugging, migration, or review).
+- Constraints: WordPress/PHP versions, plugin/theme boundaries, timeline/risk constraints.
+
+## Expected output
+
+- Clear implementation plan tied to project context.
+- File-level changes or command steps with verification.
+- Guardrails and risks called out before high-impact operations.
+
+## Team guardrails
+
+- Prefer existing repo conventions and tooling over introducing new patterns.
+- Avoid destructive DB/content operations without explicit approval.
+- Keep backward compatibility visible for production WordPress sites.
+
+## References
+
+- Main instructions: [SKILL.md](./SKILL.md)

package/skills/wordpress-router/README.md

@@ -0,0 +1,46 @@
+# WordPress Router
+
+## Purpose
+
+Use when the user asks about WordPress codebases (plugins, themes, block themes, Gutenberg blocks, WP core checkouts) and you need to quickly classify the repo and route to the correct workflow/skill (classic theme dev, block theme dev, frontend, workflow/review, blocks, REST API, WP-CLI, performance, security, testing, release packaging).
+
+## Install this skill only
+
+Use npm package (recommended):
+
+```bash
+npx wp-skills install --dest=. --targets=codex,vscode,claude,cursor,antigravity --skills=wordpress-router
+```
+
+Use local repository scripts:
+
+```bash
+node shared/scripts/skillpack-install.mjs --dest=../your-wp-project --targets=codex,vscode,claude,cursor,antigravity --skills=wordpress-router
+```
+
+## When to use
+
+- Apply this skill when your task matches the scope in [SKILL.md](./SKILL.md).
+- Typical trigger prompt: `Use wordpress-router to handle this task in my WordPress repo`.
+
+## Inputs to provide
+
+- Repository root (or target project path).
+- Exact task goal (feature, refactor, debugging, migration, or review).
+- Constraints: WordPress/PHP versions, plugin/theme boundaries, timeline/risk constraints.
+
+## Expected output
+
+- Clear implementation plan tied to project context.
+- File-level changes or command steps with verification.
+- Guardrails and risks called out before high-impact operations.
+
+## Team guardrails
+
+- Prefer existing repo conventions and tooling over introducing new patterns.
+- Avoid destructive DB/content operations without explicit approval.
+- Keep backward compatibility visible for production WordPress sites.
+
+## References
+
+- Main instructions: [SKILL.md](./SKILL.md)

package/skills/wp-abilities-api/README.md

@@ -0,0 +1,46 @@
+# WP Abilities API
+
+## Purpose
+
+Use when working with the WordPress Abilities API (wp_register_ability, wp_register_ability_category, /wp-json/wp-abilities/v1/*, @wordpress/abilities) including defining abilities, categories, meta, REST exposure, and permissions checks for clients.
+
+## Install this skill only
+
+Use npm package (recommended):
+
+```bash
+npx wp-skills install --dest=. --targets=codex,vscode,claude,cursor,antigravity --skills=wp-abilities-api
+```
+
+Use local repository scripts:
+
+```bash
+node shared/scripts/skillpack-install.mjs --dest=../your-wp-project --targets=codex,vscode,claude,cursor,antigravity --skills=wp-abilities-api
+```
+
+## When to use
+
+- Apply this skill when your task matches the scope in [SKILL.md](./SKILL.md).
+- Typical trigger prompt: `Use wp-abilities-api to handle this task in my WordPress repo`.
+
+## Inputs to provide
+
+- Repository root (or target project path).
+- Exact task goal (feature, refactor, debugging, migration, or review).
+- Constraints: WordPress/PHP versions, plugin/theme boundaries, timeline/risk constraints.
+
+## Expected output
+
+- Clear implementation plan tied to project context.
+- File-level changes or command steps with verification.
+- Guardrails and risks called out before high-impact operations.
+
+## Team guardrails
+
+- Prefer existing repo conventions and tooling over introducing new patterns.
+- Avoid destructive DB/content operations without explicit approval.
+- Keep backward compatibility visible for production WordPress sites.
+
+## References
+
+- Main instructions: [SKILL.md](./SKILL.md)

package/skills/wp-block-development/README.md

@@ -0,0 +1,46 @@
+# WP Block Development
+
+## Purpose
+
+Use when developing WordPress (Gutenberg) blocks: block.json metadata, register_block_type(_from_metadata), attributes/serialization, supports, dynamic rendering (render.php/render_callback), deprecations/migrations, viewScript vs viewScriptModule, and @wordpress/scripts/@wordpress/create-block build and test workflows.
+
+## Install this skill only
+
+Use npm package (recommended):
+
+```bash
+npx wp-skills install --dest=. --targets=codex,vscode,claude,cursor,antigravity --skills=wp-block-development
+```
+
+Use local repository scripts:
+
+```bash
+node shared/scripts/skillpack-install.mjs --dest=../your-wp-project --targets=codex,vscode,claude,cursor,antigravity --skills=wp-block-development
+```
+
+## When to use
+
+- Apply this skill when your task matches the scope in [SKILL.md](./SKILL.md).
+- Typical trigger prompt: `Use wp-block-development to handle this task in my WordPress repo`.
+
+## Inputs to provide
+
+- Repository root (or target project path).
+- Exact task goal (feature, refactor, debugging, migration, or review).
+- Constraints: WordPress/PHP versions, plugin/theme boundaries, timeline/risk constraints.
+
+## Expected output
+
+- Clear implementation plan tied to project context.
+- File-level changes or command steps with verification.
+- Guardrails and risks called out before high-impact operations.
+
+## Team guardrails
+
+- Prefer existing repo conventions and tooling over introducing new patterns.
+- Avoid destructive DB/content operations without explicit approval.
+- Keep backward compatibility visible for production WordPress sites.
+
+## References
+
+- Main instructions: [SKILL.md](./SKILL.md)

package/skills/wp-block-themes/README.md

@@ -0,0 +1,46 @@
+# WP Block Themes
+
+## Purpose
+
+Use when developing WordPress block themes: theme.json (global settings/styles), templates and template parts, patterns, style variations, and Site Editor troubleshooting (style hierarchy, overrides, caching).
+
+## Install this skill only
+
+Use npm package (recommended):
+
+```bash
+npx wp-skills install --dest=. --targets=codex,vscode,claude,cursor,antigravity --skills=wp-block-themes
+```
+
+Use local repository scripts:
+
+```bash
+node shared/scripts/skillpack-install.mjs --dest=../your-wp-project --targets=codex,vscode,claude,cursor,antigravity --skills=wp-block-themes
+```
+
+## When to use
+
+- Apply this skill when your task matches the scope in [SKILL.md](./SKILL.md).
+- Typical trigger prompt: `Use wp-block-themes to handle this task in my WordPress repo`.
+
+## Inputs to provide
+
+- Repository root (or target project path).
+- Exact task goal (feature, refactor, debugging, migration, or review).
+- Constraints: WordPress/PHP versions, plugin/theme boundaries, timeline/risk constraints.
+
+## Expected output
+
+- Clear implementation plan tied to project context.
+- File-level changes or command steps with verification.
+- Guardrails and risks called out before high-impact operations.
+
+## Team guardrails
+
+- Prefer existing repo conventions and tooling over introducing new patterns.
+- Avoid destructive DB/content operations without explicit approval.
+- Keep backward compatibility visible for production WordPress sites.
+
+## References
+
+- Main instructions: [SKILL.md](./SKILL.md)

package/skills/wp-dev-workflow/README.md

@@ -0,0 +1,46 @@
+# WP Dev Workflow
+
+## Purpose
+
+Use when scaffolding WordPress features, performing WordPress-focused code review, and planning migrations with backward compatibility safeguards.
+
+## Install this skill only
+
+Use npm package (recommended):
+
+```bash
+npx wp-skills install --dest=. --targets=codex,vscode,claude,cursor,antigravity --skills=wp-dev-workflow
+```
+
+Use local repository scripts:
+
+```bash
+node shared/scripts/skillpack-install.mjs --dest=../your-wp-project --targets=codex,vscode,claude,cursor,antigravity --skills=wp-dev-workflow
+```
+
+## When to use
+
+- Apply this skill when your task matches the scope in [SKILL.md](./SKILL.md).
+- Typical trigger prompt: `Use wp-dev-workflow to handle this task in my WordPress repo`.
+
+## Inputs to provide
+
+- Repository root (or target project path).
+- Exact task goal (feature, refactor, debugging, migration, or review).
+- Constraints: WordPress/PHP versions, plugin/theme boundaries, timeline/risk constraints.
+
+## Expected output
+
+- Clear implementation plan tied to project context.
+- File-level changes or command steps with verification.
+- Guardrails and risks called out before high-impact operations.
+
+## Team guardrails
+
+- Prefer existing repo conventions and tooling over introducing new patterns.
+- Avoid destructive DB/content operations without explicit approval.
+- Keep backward compatibility visible for production WordPress sites.
+
+## References
+
+- Main instructions: [SKILL.md](./SKILL.md)

package/skills/wp-interactivity-api/README.md

@@ -0,0 +1,46 @@
+# WP Interactivity API
+
+## Purpose
+
+Use when building or debugging WordPress Interactivity API features (data-wp-* directives, @wordpress/interactivity store/state/actions, block viewScriptModule integration, wp_interactivity_*()) including performance, hydration, and directive behavior.
+
+## Install this skill only
+
+Use npm package (recommended):
+
+```bash
+npx wp-skills install --dest=. --targets=codex,vscode,claude,cursor,antigravity --skills=wp-interactivity-api
+```
+
+Use local repository scripts:
+
+```bash
+node shared/scripts/skillpack-install.mjs --dest=../your-wp-project --targets=codex,vscode,claude,cursor,antigravity --skills=wp-interactivity-api
+```
+
+## When to use
+
+- Apply this skill when your task matches the scope in [SKILL.md](./SKILL.md).
+- Typical trigger prompt: `Use wp-interactivity-api to handle this task in my WordPress repo`.
+
+## Inputs to provide
+
+- Repository root (or target project path).
+- Exact task goal (feature, refactor, debugging, migration, or review).
+- Constraints: WordPress/PHP versions, plugin/theme boundaries, timeline/risk constraints.
+
+## Expected output
+
+- Clear implementation plan tied to project context.
+- File-level changes or command steps with verification.
+- Guardrails and risks called out before high-impact operations.
+
+## Team guardrails
+
+- Prefer existing repo conventions and tooling over introducing new patterns.
+- Avoid destructive DB/content operations without explicit approval.
+- Keep backward compatibility visible for production WordPress sites.
+
+## References
+
+- Main instructions: [SKILL.md](./SKILL.md)

package/skills/wp-performance/README.md

@@ -0,0 +1,46 @@
+# WP Performance (backend-only)
+
+## Purpose
+
+Use when investigating or improving WordPress performance (backend-only agent): profiling and measurement (WP-CLI profile/doctor, Server-Timing, Query Monitor via REST headers), database/query optimization, autoloaded options, object caching, cron, HTTP API calls, and safe verification.
+
+## Install this skill only
+
+Use npm package (recommended):
+
+```bash
+npx wp-skills install --dest=. --targets=codex,vscode,claude,cursor,antigravity --skills=wp-performance
+```
+
+Use local repository scripts:
+
+```bash
+node shared/scripts/skillpack-install.mjs --dest=../your-wp-project --targets=codex,vscode,claude,cursor,antigravity --skills=wp-performance
+```
+
+## When to use
+
+- Apply this skill when your task matches the scope in [SKILL.md](./SKILL.md).
+- Typical trigger prompt: `Use wp-performance to handle this task in my WordPress repo`.
+
+## Inputs to provide
+
+- Repository root (or target project path).
+- Exact task goal (feature, refactor, debugging, migration, or review).
+- Constraints: WordPress/PHP versions, plugin/theme boundaries, timeline/risk constraints.
+
+## Expected output
+
+- Clear implementation plan tied to project context.
+- File-level changes or command steps with verification.
+- Guardrails and risks called out before high-impact operations.
+
+## Team guardrails
+
+- Prefer existing repo conventions and tooling over introducing new patterns.
+- Avoid destructive DB/content operations without explicit approval.
+- Keep backward compatibility visible for production WordPress sites.
+
+## References
+
+- Main instructions: [SKILL.md](./SKILL.md)

package/skills/wp-phpstan/README.md

@@ -0,0 +1,46 @@
+# WP PHPStan
+
+## Purpose
+
+Use when configuring, running, or fixing PHPStan static analysis in WordPress projects (plugins/themes/sites): phpstan.neon setup, baselines, WordPress-specific typing, and handling third-party plugin classes.
+
+## Install this skill only
+
+Use npm package (recommended):
+
+```bash
+npx wp-skills install --dest=. --targets=codex,vscode,claude,cursor,antigravity --skills=wp-phpstan
+```
+
+Use local repository scripts:
+
+```bash
+node shared/scripts/skillpack-install.mjs --dest=../your-wp-project --targets=codex,vscode,claude,cursor,antigravity --skills=wp-phpstan
+```
+
+## When to use
+
+- Apply this skill when your task matches the scope in [SKILL.md](./SKILL.md).
+- Typical trigger prompt: `Use wp-phpstan to handle this task in my WordPress repo`.
+
+## Inputs to provide
+
+- Repository root (or target project path).
+- Exact task goal (feature, refactor, debugging, migration, or review).
+- Constraints: WordPress/PHP versions, plugin/theme boundaries, timeline/risk constraints.
+
+## Expected output
+
+- Clear implementation plan tied to project context.
+- File-level changes or command steps with verification.
+- Guardrails and risks called out before high-impact operations.
+
+## Team guardrails
+
+- Prefer existing repo conventions and tooling over introducing new patterns.
+- Avoid destructive DB/content operations without explicit approval.
+- Keep backward compatibility visible for production WordPress sites.
+
+## References
+
+- Main instructions: [SKILL.md](./SKILL.md)

package/skills/wp-playground/README.md

@@ -0,0 +1,46 @@
+# WordPress Playground
+
+## Purpose
+
+Use for WordPress Playground workflows: fast disposable WP instances in the browser or locally via @wp-playground/cli (server, run-blueprint, build-snapshot), auto-mounting plugins/themes, switching WP/PHP versions, blueprints, and debugging (Xdebug).
+
+## Install this skill only
+
+Use npm package (recommended):
+
+```bash
+npx wp-skills install --dest=. --targets=codex,vscode,claude,cursor,antigravity --skills=wp-playground
+```
+
+Use local repository scripts:
+
+```bash
+node shared/scripts/skillpack-install.mjs --dest=../your-wp-project --targets=codex,vscode,claude,cursor,antigravity --skills=wp-playground
+```
+
+## When to use
+
+- Apply this skill when your task matches the scope in [SKILL.md](./SKILL.md).
+- Typical trigger prompt: `Use wp-playground to handle this task in my WordPress repo`.
+
+## Inputs to provide
+
+- Repository root (or target project path).
+- Exact task goal (feature, refactor, debugging, migration, or review).
+- Constraints: WordPress/PHP versions, plugin/theme boundaries, timeline/risk constraints.
+
+## Expected output
+
+- Clear implementation plan tied to project context.
+- File-level changes or command steps with verification.
+- Guardrails and risks called out before high-impact operations.
+
+## Team guardrails
+
+- Prefer existing repo conventions and tooling over introducing new patterns.
+- Avoid destructive DB/content operations without explicit approval.
+- Keep backward compatibility visible for production WordPress sites.
+
+## References
+
+- Main instructions: [SKILL.md](./SKILL.md)

package/skills/wp-plugin-development/README.md

@@ -0,0 +1,46 @@
+# WP Plugin Development
+
+## Purpose
+
+Use when developing WordPress plugins: architecture and hooks, activation/deactivation/uninstall, admin UI and Settings API, data storage, cron/tasks, security (nonces/capabilities/sanitization/escaping), and release packaging.
+
+## Install this skill only
+
+Use npm package (recommended):
+
+```bash
+npx wp-skills install --dest=. --targets=codex,vscode,claude,cursor,antigravity --skills=wp-plugin-development
+```
+
+Use local repository scripts:
+
+```bash
+node shared/scripts/skillpack-install.mjs --dest=../your-wp-project --targets=codex,vscode,claude,cursor,antigravity --skills=wp-plugin-development
+```
+
+## When to use
+
+- Apply this skill when your task matches the scope in [SKILL.md](./SKILL.md).
+- Typical trigger prompt: `Use wp-plugin-development to handle this task in my WordPress repo`.
+
+## Inputs to provide
+
+- Repository root (or target project path).
+- Exact task goal (feature, refactor, debugging, migration, or review).
+- Constraints: WordPress/PHP versions, plugin/theme boundaries, timeline/risk constraints.
+
+## Expected output
+
+- Clear implementation plan tied to project context.
+- File-level changes or command steps with verification.
+- Guardrails and risks called out before high-impact operations.
+
+## Team guardrails
+
+- Prefer existing repo conventions and tooling over introducing new patterns.
+- Avoid destructive DB/content operations without explicit approval.
+- Keep backward compatibility visible for production WordPress sites.
+
+## References
+
+- Main instructions: [SKILL.md](./SKILL.md)

package/skills/wp-project-triage/README.md

@@ -0,0 +1,46 @@
+# WP Project Triage
+
+## Purpose
+
+Use when you need a deterministic inspection of a WordPress repository (plugin/theme/block theme/WP core/Gutenberg/full site) including tooling/tests/version hints, and a structured JSON report to guide workflows and guardrails.
+
+## Install this skill only
+
+Use npm package (recommended):
+
+```bash
+npx wp-skills install --dest=. --targets=codex,vscode,claude,cursor,antigravity --skills=wp-project-triage
+```
+
+Use local repository scripts:
+
+```bash
+node shared/scripts/skillpack-install.mjs --dest=../your-wp-project --targets=codex,vscode,claude,cursor,antigravity --skills=wp-project-triage
+```
+
+## When to use
+
+- Apply this skill when your task matches the scope in [SKILL.md](./SKILL.md).
+- Typical trigger prompt: `Use wp-project-triage to handle this task in my WordPress repo`.
+
+## Inputs to provide
+
+- Repository root (or target project path).
+- Exact task goal (feature, refactor, debugging, migration, or review).
+- Constraints: WordPress/PHP versions, plugin/theme boundaries, timeline/risk constraints.
+
+## Expected output
+
+- Clear implementation plan tied to project context.
+- File-level changes or command steps with verification.
+- Guardrails and risks called out before high-impact operations.
+
+## Team guardrails
+
+- Prefer existing repo conventions and tooling over introducing new patterns.
+- Avoid destructive DB/content operations without explicit approval.
+- Keep backward compatibility visible for production WordPress sites.
+
+## References
+
+- Main instructions: [SKILL.md](./SKILL.md)

package/skills/wp-rest-api/README.md

@@ -0,0 +1,46 @@
+# WP REST API
+
+## Purpose
+
+Use when building, extending, or debugging WordPress REST API endpoints/routes: register_rest_route, WP_REST_Controller/controller classes, schema/argument validation, permission_callback/authentication, response shaping, register_rest_field/register_meta, or exposing CPTs/taxonomies via show_in_rest.
+
+## Install this skill only
+
+Use npm package (recommended):
+
+```bash
+npx wp-skills install --dest=. --targets=codex,vscode,claude,cursor,antigravity --skills=wp-rest-api
+```
+
+Use local repository scripts:
+
+```bash
+node shared/scripts/skillpack-install.mjs --dest=../your-wp-project --targets=codex,vscode,claude,cursor,antigravity --skills=wp-rest-api
+```
+
+## When to use
+
+- Apply this skill when your task matches the scope in [SKILL.md](./SKILL.md).
+- Typical trigger prompt: `Use wp-rest-api to handle this task in my WordPress repo`.
+
+## Inputs to provide
+
+- Repository root (or target project path).
+- Exact task goal (feature, refactor, debugging, migration, or review).
+- Constraints: WordPress/PHP versions, plugin/theme boundaries, timeline/risk constraints.
+
+## Expected output
+
+- Clear implementation plan tied to project context.
+- File-level changes or command steps with verification.
+- Guardrails and risks called out before high-impact operations.
+
+## Team guardrails
+
+- Prefer existing repo conventions and tooling over introducing new patterns.
+- Avoid destructive DB/content operations without explicit approval.
+- Keep backward compatibility visible for production WordPress sites.
+
+## References
+
+- Main instructions: [SKILL.md](./SKILL.md)

package/skills/wp-wpcli-and-ops/README.md

@@ -0,0 +1,46 @@
+# WP-CLI and Ops
+
+## Purpose
+
+Use when working with WP-CLI (wp) for WordPress operations: safe search-replace, db export/import, plugin/theme/user/content management, cron, cache flushing, multisite, and scripting/automation with wp-cli.yml.
+
+## Install this skill only
+
+Use npm package (recommended):
+
+```bash
+npx wp-skills install --dest=. --targets=codex,vscode,claude,cursor,antigravity --skills=wp-wpcli-and-ops
+```
+
+Use local repository scripts:
+
+```bash
+node shared/scripts/skillpack-install.mjs --dest=../your-wp-project --targets=codex,vscode,claude,cursor,antigravity --skills=wp-wpcli-and-ops
+```
+
+## When to use
+
+- Apply this skill when your task matches the scope in [SKILL.md](./SKILL.md).
+- Typical trigger prompt: `Use wp-wpcli-and-ops to handle this task in my WordPress repo`.
+
+## Inputs to provide
+
+- Repository root (or target project path).
+- Exact task goal (feature, refactor, debugging, migration, or review).
+- Constraints: WordPress/PHP versions, plugin/theme boundaries, timeline/risk constraints.
+
+## Expected output
+
+- Clear implementation plan tied to project context.
+- File-level changes or command steps with verification.
+- Guardrails and risks called out before high-impact operations.
+
+## Team guardrails
+
+- Prefer existing repo conventions and tooling over introducing new patterns.
+- Avoid destructive DB/content operations without explicit approval.
+- Keep backward compatibility visible for production WordPress sites.
+
+## References
+
+- Main instructions: [SKILL.md](./SKILL.md)

package/skills/wpds/README.md

@@ -0,0 +1,46 @@
+# WordPress Design System (WPDS)
+
+## Purpose
+
+Use when building UIs leveraging the WordPress Design System (WPDS) and its components, tokens, patterns, etc.
+
+## Install this skill only
+
+Use npm package (recommended):
+
+```bash
+npx wp-skills install --dest=. --targets=codex,vscode,claude,cursor,antigravity --skills=wpds
+```
+
+Use local repository scripts:
+
+```bash
+node shared/scripts/skillpack-install.mjs --dest=../your-wp-project --targets=codex,vscode,claude,cursor,antigravity --skills=wpds
+```
+
+## When to use
+
+- Apply this skill when your task matches the scope in [SKILL.md](./SKILL.md).
+- Typical trigger prompt: `Use wpds to handle this task in my WordPress repo`.
+
+## Inputs to provide
+
+- Repository root (or target project path).
+- Exact task goal (feature, refactor, debugging, migration, or review).
+- Constraints: WordPress/PHP versions, plugin/theme boundaries, timeline/risk constraints.
+
+## Expected output
+
+- Clear implementation plan tied to project context.
+- File-level changes or command steps with verification.
+- Guardrails and risks called out before high-impact operations.
+
+## Team guardrails
+
+- Prefer existing repo conventions and tooling over introducing new patterns.
+- Avoid destructive DB/content operations without explicit approval.
+- Keep backward compatibility visible for production WordPress sites.
+
+## References
+
+- Main instructions: [SKILL.md](./SKILL.md)