wp-orchestrator
Master WordPress project orchestrator - coordinates all WordPress skills for complete site setup, audit, and optimization. Use for new project setup, site audits, or comprehensive reviews. Runs interview phases and manages todo lists.
What this skill does
# WordPress Project Orchestrator
Master skill that coordinates all WordPress development skills for comprehensive project management.
**See Also:** [WORKFLOW.md](./WORKFLOW.md) - Complete end-to-end development workflow documentation
## Quick Start Slash Commands
| Command | Purpose |
|---------|---------|
| `/wp-setup` | Set up a new WordPress site with Docker, plugins, white-labeling |
| `/wp-audit` | Run comprehensive site audit (SEO, visual, performance, security) |
| `/wp-launch` | Pre-launch checklist and handoff documentation |
## Complete Development Lifecycle
```
1. Discovery & Branding → 2. Environment Setup → 3. Theme Development
↓ ↓ ↓
brand-guide wp-docker wordpress-dev
gsap-animations
↓ ↓ ↓
4. Content & SEO → 5. Testing & QA → 6. Packaging & Deploy
↓ ↓ ↓
wordpress-admin visual-qa GitHub + WP Pusher
seo-optimizer form-testing demo-content.json
E2E tests theme zip
↓ ↓ ↓
7. White-Label → 8. Client Handoff
↓ ↓
white-label Documentation
ASE + Branda Training
```
## Environment Detection
The orchestrator automatically detects your WordPress environment:
### Docker Environment
```bash
# Check for docker-compose.yml with WordPress
if [ -f docker-compose.yml ] && grep -q wordpress docker-compose.yml; then
echo "Docker WordPress detected"
fi
# Check running containers
docker ps | grep wordpress
```
### WordPress Playground
```bash
# Check for Playground blueprints
if [ -f blueprint.json ] || [ -d blueprints/ ]; then
echo "Playground environment detected"
fi
# Run Playground with blueprint
npx @wp-playground/cli server --blueprint=./blueprint.json
```
### Standard WordPress
```bash
# Check for wp-config.php
if [ -f wp-config.php ]; then
echo "Standard WordPress installation detected"
fi
```
## Available Skills
| Skill | Purpose | Use When |
|-------|---------|----------|
| **wordpress-dev** | Coding standards, CPT, security, performance | Writing WordPress code |
| **wordpress-admin** | Site management, WP-CLI, REST API | Managing content, settings |
| **seo-optimizer** | Yoast/Rank Math audit, keywords, meta | SEO review and fixes |
| **visual-qa** | Screenshot testing, responsive QA | After CSS/template changes |
| **brand-guide** | Brand documentation | Starting new project |
| **white-label** | Admin branding with ASE + Branda | Client site setup |
| **gsap-animations** | GSAP best practices, accessibility | Implementing animations |
| **wp-performance** | Speed optimization, Core Web Vitals | Performance issues |
| **wp-docker** | Docker Compose environment | Local development |
| **wp-playground** | WordPress Playground blueprints | Testing and demos |
---
## Project Phases
### Phase 1: Discovery Interview
Ask the user these questions to understand the project:
```markdown
## Project Discovery
1. **Project Type**
- New site build?
- Existing site optimization?
- Site audit?
- Specific feature implementation?
2. **Site Information**
- URL (staging/production)
- WordPress version
- Theme (custom, child, builder?)
- Hosting environment (Docker local, shared, VPS, managed?)
3. **Requirements**
- What pages are needed?
- Custom post types?
- Forms (contact, inquiry)?
- E-commerce?
- Multilingual?
4. **Brand**
- Do you have brand guidelines?
- Logo files available?
- Color palette defined?
- Typography chosen?
5. **SEO Requirements**
- Focus keywords identified?
- Existing content to optimize?
- Google Analytics/Search Console connected?
6. **Performance Goals**
- Target PageSpeed score?
- Core Web Vitals requirements?
- CDN preferences?
7. **Client Handoff**
- Need white-labeled admin?
- Training documentation needed?
- Which admin features to expose?
```
### Phase 2: Initial Audit
Run these checks on existing sites:
#### Plugin Check
```bash
# Via WP-CLI in Docker
docker exec wordpress-container wp plugin list --format=table
# Check for required plugins
REQUIRED="admin-site-enhancements litespeed-cache wordpress-seo ewww-image-optimizer"
```
#### SEO Audit
```bash
# Run SEO optimizer
python3 /root/.claude/skills/seo-optimizer/audit.py --base-url https://site.com --json
```
#### Visual QA
```bash
# Take screenshots of all pages
python3 /root/.claude/skills/visual-qa/screenshot.py --all --base-url https://site.com
```
#### Performance Check
```bash
# Check PageSpeed (requires API key or use web tool)
curl "https://www.googleapis.com/pagespeedonline/v5/runPagespeed?url=https://site.com&strategy=mobile"
```
### Phase 3: Todo List Generation
Based on audit results, generate comprehensive todo list:
```markdown
## Site Setup Checklist
### Foundation
- [ ] WordPress core updated
- [ ] Theme installed and configured
- [ ] Child theme created (if needed)
- [ ] Required plugins installed
### Plugins to Install
- [ ] Admin and Site Enhancements (ASE) - Admin cleanup, security
- [ ] Branda - White labeling, login customization
- [ ] LiteSpeed Cache - Performance
- [ ] Yoast SEO - SEO optimization
- [ ] WP Mail SMTP - Email delivery
- [ ] Solid Security - Additional security
- [ ] EWWW Image Optimizer - Image compression
- [ ] WP Activity Log - Audit logging
- [ ] Site Kit by Google - Analytics integration
- [ ] ManageWP Worker - Remote management
- [ ] Instant Images - Stock photos
- [ ] Admin Menu Editor - Menu organization (optional)
### Pages to Create
- [ ] Home
- [ ] About
- [ ] Services/Portfolio
- [ ] Contact
- [ ] Privacy Policy
- [ ] Terms of Service
### SEO Setup
- [ ] Focus keyword for each page
- [ ] Meta descriptions (120-160 chars)
- [ ] Featured images with ALT text
- [ ] XML sitemap generated
- [ ] Robots.txt configured
- [ ] Google Search Console connected
### Performance
- [ ] Image optimization configured
- [ ] Caching enabled
- [ ] CDN configured
- [ ] Lazy loading enabled
- [ ] Minification enabled
- [ ] PageSpeed score >80
### Security
- [ ] Login URL changed
- [ ] XML-RPC disabled
- [ ] 2FA enabled for admins
- [ ] Automatic updates configured
- [ ] Backup solution in place
### White Label (Client Sites) - Using white-label skill
- [ ] Login page customized (Branda: logo, colors, background)
- [ ] Admin bar branded (Branda: hide WP logo, custom logo)
- [ ] "Howdy" replaced (Branda: custom greeting)
- [ ] Admin footer customized (ASE or Branda)
- [ ] Dashboard widgets hidden (ASE)
- [ ] Admin menu organized (Admin Menu Editor)
- [ ] Custom login URL set (ASE: /client-login)
- [ ] XML-RPC disabled (ASE)
- [ ] Author slugs obfuscated (ASE)
### Visual QA
- [ ] Desktop screenshots reviewed
- [ ] Tablet screenshots reviewed
- [ ] Mobile screenshots reviewed
- [ ] Animations working
- [ ] No layout issues
- [ ] Forms functional
### Pre-Launch
- [ ] All pages have content
- [ ] Forms tested
- [ ] 404 page configured
- [ ] Favicon uploaded
- [ ] Social sharing images set
- [ ] Analytics tracking verified
```
---
## Orchestration Commands
### New Project Setup
When user says: "Set up a new WordPress project"
1. **Run Discovery Interview**
- Use AskUserQuestion tool for project requirements
- Document brand, pages, features needed
2. **Create Todo List**
- Generate comprehensive TodoWrite list
- Break into phases (Foundation → Content → SEO → Performance → Launch)
3. **Plugin Installation Guidance**
- List plugins from recommended-plugins.md
- Provide installation order
4. **Theme Setup**
- Guide through theme installation
- Configure initial settings
5. **ASE Configuration**
- Apply security settings
- Configure white labeling
### Site Audit
When user says: "Audit this WordPress site"
1. **Run All Audits in PRelated in Web Dev
generating-lwc-components
IncludedLightning Web Components with PICKLES methodology and 165-point scoring. Use this skill when the user creates or edits LWC components, builds wire service patterns, or writes Jest tests for LWC. TRIGGER when: user creates/edits LWC components, touches lwc/**/*.js, .html, .css, .js-meta.xml files, or asks about wire service, SLDS, or Jest LWC tests. DO NOT TRIGGER when: Apex classes (use generating-apex), Aura components, or Visualforce.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Set up queries with useQuery, mutations with useMutation, configure QueryClient caching strategies, implement optimistic updates, and handle infinite scroll with useInfiniteQuery. Use when: setting up data fetching in React projects, migrating from v4 to v5, or fixing object syntax required errors, query callbacks removed issues, cacheTime renamed to gcTime, isPending vs isLoading confusion, keepPreviousData removed problems.
document-processor-api
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
nutrient-document-processing
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Covers useMutationState, simplified optimistic updates, throwOnError, network mode (offline/PWA), and infiniteQueryOptions. Use when setting up data fetching, fixing v4→v5 migration errors (object syntax, gcTime, isPending, keepPreviousData), or debugging SSR/hydration issues with streaming server components.
accelint-nextjs-best-practices
IncludedNext.js performance optimization and best practices. Use when writing Next.js code (App Router or Pages Router); implementing Server Components, Server Actions, or API routes; optimizing RSC serialization, data fetching, or server-side rendering; reviewing Next.js code for performance issues; fixing authentication in Server Actions; or implementing Suspense boundaries, parallel data fetching, or request deduplication.