Skill

Build Production-Ready WordPress Sites

WordPress dev workflow: theming, plugins, WooCommerce, performance, and security, plus WordPress 7.0's new AI/RTC APIs.

Works with wordpresswoocommerceopenaianthropicgoogle

Maintainer of this project? Claim this page to edit the listing.


91
Spark score
out of 100
Updated 5 months ago
Version 1.0.0
Models
claudegpt 4ogemini 2 0

Add to Favorites

Why it matters

Orchestrate a comprehensive development workflow for building production-ready WordPress sites, from theme and plugin creation to WooCommerce integration and security hardening.

Outcomes

What it gets done

01

Develop custom WordPress themes and plugins.

02

Integrate WooCommerce for e-commerce functionality.

03

Optimize WordPress performance and security.

04

Leverage WordPress 7.0+ features like Real-Time Collaboration and AI Connectors.

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-wordpress | bash

Overview

WordPress Development Workflow Bundle

An eight-phase WordPress development workflow (setup through deployment) delegating to specialist skills, with deep code-level coverage of WordPress 7.0's new AI Connectors, Real-Time Collaboration, and Abilities APIs. Use for building or modernizing a WordPress site end-to-end, or specifically implementing WordPress 7.0 features like AI Connectors, RTC, or the Abilities API.

What it does

This skill orchestrates an eight-phase WordPress development workflow - setup, theme development, plugin development, WooCommerce integration, performance optimization, security hardening, testing, and deployment - each phase delegating to named specialist skills via copy-paste @skill-name prompts (e.g. @frontend-developer for theme components, @wordpress-penetration-testing for security audits, @playwright-skill for E2E tests). It documents concrete file structures for both themes (style.css, functions.php, template hierarchy files, template-parts/) and plugins (activator/deactivator/loader classes, admin/, public/ directories), plus WooCommerce customization (custom product types, checkout flow, payment gateways, subscriptions) and a security checklist (core/plugin updates, 2FA, security headers, XML-RPC disabling, database prefix changes).

Its most distinctive content is deep, code-level coverage of WordPress 7.0 (April 2026) features, each with explicit backward-compatibility notes: Real-Time Collaboration using Yjs CRDT (falls back to post locking when legacy meta boxes are detected; requires show_in_rest => true on custom post meta to participate); the provider-agnostic AI Connectors API (wp_ai_client_prompt() with using_temperature(), using_model_preference(), and as_json_response() for structured output, backed by OpenAI/Claude/Gemini provider plugins configured under Settings > Connectors, worked with a full auto-excerpt-generation example on save_post); the Abilities API (a standardized capability-declaration system with wp_register_ability(), its own REST manifest endpoint, and an MCP adapter for AI agent integration, shown with a full custom "generate-summary" ability including permission callback); DataViews/DataForm replacing WP_List_Table on admin screens; PHP-only block registration without JavaScript; and Interactivity API changes (watch() replacing effect). PHP 7.4 becomes the new minimum, dropping 7.2/7.3 support.

When to use - and when NOT to

Use this skill when building a new WordPress site, creating custom themes, developing plugins, setting up WooCommerce stores, optimizing WordPress performance, hardening security, or specifically implementing WordPress 7.0 features (RTC, AI Connectors, Abilities API, DataViews). Each phase's specialist skills should be invoked directly for hands-on implementation; this skill is the roadmap connecting them.

It names four related workflow bundles for adjacent scope - development (general web dev), security-audit, testing-qa, and ecommerce - and a quality-gate checklist confirms testing, security, performance, cross-browser, mobile, and accessibility (WCAG 2.1) before moving between phases.

Inputs and outputs

Input is a WordPress project at any stage, from initial setup through deployment. Output is a sequenced plan naming which specialist skill to invoke per phase, working code examples (RTC-compatible post meta, AI Connector calls, Abilities API registration, PHP-only blocks), phase-specific checklists, and copy-paste prompts to execute each step.

define('WP_COLLABORATION_MAX_USERS', 5);

Integrations

Coordinates specialist skills across its eight phases (app-builder, frontend-developer, backend-dev-guidelines, payment-integration, web-performance-optimization, wordpress-penetration-testing, playwright-skill, deployment-engineer, and more), and integrates directly with WordPress 7.0's new core APIs (AI Connectors, Abilities API, RTC via Yjs) plus WooCommerce for ecommerce.

Who it's for

Teams building or modernizing production WordPress sites - themes, plugins, WooCommerce stores - who need both the phase-by-phase project roadmap and concrete WordPress 7.0 API code (AI, real-time collaboration, Abilities) rather than generic WordPress tutorials.

Source README

WordPress Development Workflow Bundle

Overview

Comprehensive WordPress development workflow covering theme development, plugin creation, WooCommerce integration, performance optimization, and security. This bundle orchestrates skills for building production-ready WordPress sites and applications.

WordPress 7.0 Features (Backward Compatible)

WordPress 7.0 (April 9, 2026) introduces significant features while maintaining backward compatibility:

Real-Time Collaboration (RTC)

  • Multiple users can edit simultaneously using Yjs CRDT
  • HTTP polling provider (configurable via WP_COLLABORATION_MAX_USERS)
  • Custom transport via sync.providers filter
  • Backward Compatibility: Falls back to post locking when legacy meta boxes detected

AI Connectors API

  • Provider-agnostic AI interface in core (wp_ai_client_prompt())
  • Settings > Connectors for centralized API credential management
  • Official providers: OpenAI, Anthropic Claude, Google Gemini
  • Backward Compatibility: Works with WordPress 6.9+ via plugin

Abilities API (Stable in 7.0)

  • Standardized capability declaration system
  • REST API endpoints: /wp-json/abilities/v1/manifest
  • MCP adapter for AI agent integration
  • Backward Compatibility: Can be used as Composer package in 6.x

DataViews & DataForm

  • Replaces WP_List_Table on Posts, Pages, Media screens
  • New layouts: table, grid, list, activity
  • Client-side validation (pattern, minLength, maxLength, min, max)
  • Backward Compatibility: Plugins using old hooks still work

PHP-Only Block Registration

  • Register blocks entirely via PHP without JavaScript
  • Auto-generated Inspector controls
  • Backward Compatibility: Existing JS blocks continue to work

Interactivity API Updates

  • watch() replaces effect from @preact/signals
  • State navigation changes
  • Backward Compatibility: Old syntax deprecated but functional

Admin Refresh

  • New default color scheme
  • View transitions between admin screens
  • Backward Compatibility: CSS-level changes, no breaking changes

Pattern Editing

  • ContentOnly mode defaults for unsynced patterns
  • disableContentOnlyForUnsyncedPatterns setting
  • Backward Compatibility: Existing patterns work

When to Use This Workflow

Use this workflow when:

  • Building new WordPress websites
  • Creating custom themes
  • Developing WordPress plugins
  • Setting up WooCommerce stores
  • Optimizing WordPress performance
  • Hardening WordPress security
  • Implementing WordPress 7.0 features (RTC, AI, DataViews)

Workflow Phases

Phase 1: WordPress Setup

Skills to Invoke
  • app-builder - Project scaffolding
  • environment-setup-guide - Development environment
Actions
  1. Set up local development environment (LocalWP, Docker, or Valet)
  2. Install WordPress (recommend 7.0+ for new projects)
  3. Configure development database
  4. Set up version control
  5. Configure wp-config.php for development
WordPress 7.0 Configuration
// wp-config.php - Collaboration settings
define('WP_COLLABORATION_MAX_USERS', 5);

// AI Connector is enabled by installing a provider plugin
// (e.g., OpenAI, Anthropic Claude, or Google Gemini connector)
// No constant needed - configure via Settings > Connectors in admin
Copy-Paste Prompts
Use @app-builder to scaffold a new WordPress project with modern tooling

Phase 2: Theme Development

Skills to Invoke
  • frontend-developer - Component development
  • frontend-design - UI implementation
  • tailwind-patterns - Styling
  • web-performance-optimization - Performance
Actions
  1. Design theme architecture
  2. Create theme files (style.css, functions.php, index.php)
  3. Implement template hierarchy
  4. Create custom page templates
  5. Add custom post types and taxonomies
  6. Implement theme customization options
  7. Add responsive design
  8. Test with WordPress 7.0 admin refresh
WordPress 7.0 Theme Considerations
  • Block API v3 now reference model
  • Pseudo-element support in theme.json
  • Global Styles custom CSS honors block-defined selectors
  • View transitions for admin navigation
Theme Structure
theme-name/
├── style.css
├── functions.php
├── index.php
├── header.php
├── footer.php
├── sidebar.php
├── single.php
├── page.php
├── archive.php
├── search.php
├── 404.php
├── template-parts/
├── inc/
├── assets/
│   ├── css/
│   ├── js/
│   └── images/
└── languages/
Copy-Paste Prompts
Use @frontend-developer to create a custom WordPress theme with React components
Use @tailwind-patterns to style WordPress theme with modern CSS

Phase 3: Plugin Development

Skills to Invoke
  • backend-dev-guidelines - Backend standards
  • api-design-principles - API design
  • auth-implementation-patterns - Authentication
Actions
  1. Design plugin architecture
  2. Create plugin boilerplate
  3. Implement hooks (actions and filters)
  4. Create admin interfaces
  5. Add custom database tables
  6. Implement REST API endpoints
  7. Add settings and options pages
WordPress 7.0 Plugin Considerations
  • RTC Compatibility: Register post meta with show_in_rest => true
  • AI Integration: Use wp_ai_client_prompt() for AI features
  • DataViews: Consider new admin UI patterns
  • Meta Boxes: Migrate to block-based UIs for collaboration support
RTC-Compatible Post Meta Registration
register_post_meta('post', 'custom_field', [
    'type' => 'string',
    'single' => true,
    'show_in_rest' => true,  // Required for RTC
    'sanitize_callback' => 'sanitize_text_field',
]);
AI Connector Example
// Using WordPress 7.0 AI Connector
// Note: Requires an AI provider plugin (OpenAI, Claude, or Gemini) to be installed and configured

// Basic text generation
$response = wp_ai_client_prompt('Summarize this content.')
    ->generate_text();

// With temperature for deterministic output
$response = wp_ai_client_prompt('Summarize this content.')
    ->using_temperature(0.2)
    ->generate_text();

// With model preference (tries first available in list)
$response = wp_ai_client_prompt('Summarize this content.')
    ->using_model_preference('gpt-4', 'claude-3-opus', 'gemini-2-pro')
    ->generate_text();

// For JSON structured output
$schema = [
    'type' => 'object',
    'properties' => [
        'summary' => ['type' => 'string'],
        'keywords' => ['type' => 'array', 'items' => ['type' => 'string']]
    ],
    'required' => ['summary']
];
$response = wp_ai_client_prompt('Analyze this content and return JSON.')
    ->using_system_instruction('You are a content analyzer.')
    ->as_json_response($schema)
    ->generate_text();
Plugin Structure
plugin-name/
├── plugin-name.php
├── includes/
│   ├── class-plugin-activator.php
│   ├── class-plugin-deactivator.php
│   ├── class-plugin-loader.php
│   └── class-plugin.php
├── admin/
│   ├── class-plugin-admin.php
│   ├── css/
│   └── js/
├── public/
│   ├── class-plugin-public.php
│   ├── css/
│   └── js/
└── languages/
Copy-Paste Prompts
Use @backend-dev-guidelines to create a WordPress plugin with proper architecture

Phase 4: WooCommerce Integration

Skills to Invoke
  • payment-integration - Payment processing
  • stripe-integration - Stripe payments
  • billing-automation - Billing workflows
Actions
  1. Install and configure WooCommerce
  2. Create custom product types
  3. Customize checkout flow
  4. Integrate payment gateways
  5. Set up shipping methods
  6. Create custom order statuses
  7. Implement subscription products
  8. Add custom email templates
WordPress 7.0 + WooCommerce Considerations
  • Test checkout with new admin interfaces
  • AI connectors for product descriptions
  • DataViews for order management screens
  • RTC for collaborative order editing
Copy-Paste Prompts
Use @payment-integration to set up WooCommerce with Stripe
Use @billing-automation to create subscription products in WooCommerce

Phase 5: Performance Optimization

Skills to Invoke
  • web-performance-optimization - Performance optimization
  • database-optimizer - Database optimization
Actions
  1. Implement caching (object, page, browser)
  2. Optimize images (lazy loading, WebP)
  3. Minify and combine assets
  4. Enable CDN
  5. Optimize database queries
  6. Implement lazy loading
  7. Configure OPcache
  8. Set up Redis/Memcached
WordPress 7.0 Performance
  • Client-side media processing
  • Font Library enabled for all themes
  • Responsive grid block optimizations
  • View transitions reduce perceived load time
Performance Checklist
  • Page load time < 3 seconds
  • Time to First Byte < 200ms
  • Largest Contentful Paint < 2.5s
  • Cumulative Layout Shift < 0.1
  • First Input Delay < 100ms
Copy-Paste Prompts
Use @web-performance-optimization to audit and improve WordPress performance

Phase 6: Security Hardening

Skills to Invoke
  • security-auditor - Security audit
  • wordpress-penetration-testing - WordPress security testing
  • sast-configuration - Static analysis
Actions
  1. Update WordPress core, themes, plugins
  2. Implement security headers
  3. Configure file permissions
  4. Set up firewall rules
  5. Enable two-factor authentication
  6. Implement rate limiting
  7. Configure security logging
  8. Set up malware scanning
WordPress 7.0 Security Considerations
  • PHP 7.4 minimum (drops 7.2/7.3 support)
  • Test Abilities API permission boundaries
  • Verify collaboration data isolation
  • AI connector credential security
Security Checklist
  • WordPress core updated (7.0+ recommended)
  • All plugins/themes updated
  • Strong passwords enforced
  • Two-factor authentication enabled
  • Security headers configured
  • XML-RPC disabled or protected
  • File editing disabled
  • Database prefix changed
  • Regular backups configured
Copy-Paste Prompts
Use @wordpress-penetration-testing to audit WordPress security
Use @security-auditor to perform comprehensive security review

Phase 7: Testing

Skills to Invoke
  • test-automator - Test automation
  • playwright-skill - E2E testing
  • webapp-testing - Web app testing
Actions
  1. Write unit tests for custom code
  2. Create integration tests
  3. Set up E2E tests
  4. Test cross-browser compatibility
  5. Test responsive design
  6. Performance testing
  7. Security testing
WordPress 7.0 Testing Priorities
  • Test with iframed post editor
  • Verify DataViews integration
  • Test collaboration (RTC) workflows
  • Validate AI connector functionality
  • Test Interactivity API with watch()
Copy-Paste Prompts
Use @playwright-skill to create E2E tests for WordPress site

Phase 8: Deployment

Skills to Invoke
  • deployment-engineer - Deployment
  • cicd-automation-workflow-automate - CI/CD
  • github-actions-templates - GitHub Actions
Actions
  1. Set up staging environment
  2. Configure deployment pipeline
  3. Set up database migrations
  4. Configure environment variables
  5. Enable maintenance mode during deployment
  6. Deploy to production
  7. Verify deployment
  8. Monitor post-deployment
Copy-Paste Prompts
Use @deployment-engineer to set up WordPress deployment pipeline

WordPress-Specific Workflows

Custom Post Type Development (RTC-Compatible)

register_post_type('book', [
    'labels' => [...],
    'public' => true,
    'has_archive' => true,
    'supports' => ['title', 'editor', 'thumbnail', 'excerpt'],
    'menu_icon' => 'dashicons-book',
    'show_in_rest' => true,  // Enable for RTC
]);

// Register meta with REST API for collaboration
register_post_meta('book', 'isbn', [
    'type' => 'string',
    'single' => true,
    'show_in_rest' => true,
    'sanitize_callback' => 'sanitize_text_field',
]);

Custom REST API Endpoint

add_action('rest_api_init', function() {
    register_rest_route('myplugin/v1', '/books', [
        'methods' => 'GET',
        'callback' => 'get_books',
        'permission_callback' => '__return_true',
    ]);
});

WordPress 7.0 AI Connector Usage

// Auto-generate post excerpt with AI
add_action('save_post', function($post_id, $post) {
    if (wp_is_post_autosave($post_id) || wp_is_post_revision($post_id)) {
        return;
    }
    
    // Skip if excerpt already exists
    if (!empty($post->post_excerpt)) {
        return;
    }
    
    $content = strip_tags($post->post_content);
    if (empty($content)) {
        return;
    }
    
    // Check if AI client is available
    if (!function_exists('wp_ai_client_prompt')) {
        return;
    }
    
    // Build prompt with input
    $result = wp_ai_client_prompt(
        'Create a brief 2-sentence summary of this content: ' . substr($content, 0, 1000)
    );
    
    if (is_wp_error($result)) {
        return; // Silently fail - don't block post saving
    }
    
    // Use temperature for consistent output
    $result->using_temperature(0.3);
    $summary = $result->generate_text();
    
    if ($summary && !is_wp_error($summary)) {
        wp_update_post([
            'ID' => $post_id,
            'post_excerpt' => sanitize_textarea_field($summary)
        ]);
    }
}, 10, 2);

PHP-Only Block Registration (WordPress 7.0)

// Register block entirely in PHP
register_block_type('my-plugin/hello-world', [
    'render_callback' => function($attributes, $content) {
        return '<p class="hello-world">Hello, World!</p>';
    },
    'attributes' => [
        'message' => ['type' => 'string', 'default' => 'Hello!']
    ],
]);

Abilities API Registration

// Register ability category on correct hook
add_action('wp_abilities_api_categories_init', function() {
    wp_register_ability_category('content-creation', [
        'label' => __('Content Creation', 'my-plugin'),
        'description' => __('Abilities for generating and managing content', 'my-plugin'),
    ]);
});

// Register abilities on correct hook
add_action('wp_abilities_api_init', function() {
    wp_register_ability('my-plugin/generate-summary', [
        'label' => __('Generate Post Summary', 'my-plugin'),
        'description' => __('Creates an AI-powered summary of a post', 'my-plugin'),
        'category' => 'content-creation',
        'input_schema' => [
            'type' => 'object',
            'properties' => [
                'post_id' => ['type' => 'integer', 'description' => 'The post ID to summarize']
            ],
            'required' => ['post_id']
        ],
        'output_schema' => [
            'type' => 'object',
            'properties' => [
                'summary' => ['type' => 'string', 'description' => 'The generated summary']
            ]
        ],
        'execute_callback' => 'my_plugin_generate_summary_handler',
        'permission_callback' => function() {
            return current_user_can('edit_posts');
        }
    ]);
});

// Handler function for the ability
function my_plugin_generate_summary_handler($input) {
    $post_id = isset($input['post_id']) ? absint($input['post_id']) : 0;
    $post = get_post($post_id);
    
    if (!$post) {
        return new WP_Error('invalid_post', 'Post not found');
    }
    
    $content = strip_tags($post->post_content);
    if (empty($content)) {
        return ['summary' => ''];
    }
    
    if (!function_exists('wp_ai_client_prompt')) {
        return new WP_Error('ai_unavailable', 'AI client not available');
    }
    
    $result = wp_ai_client_prompt('Summarize in 2 sentences: ' . substr($content, 0, 1000))
        ->using_temperature(0.3)
        ->generate_text();
    
    if (is_wp_error($result)) {
        return $result;
    }
    
    return ['summary' => sanitize_textarea_field($result)];
}

WooCommerce Custom Product Type

add_action('init', function() {
    class WC_Product_Custom extends WC_Product {
        // Custom product implementation
    }
});

Quality Gates

Before moving to next phase, verify:

  • All custom code tested
  • Security scan passed
  • Performance targets met
  • Cross-browser tested
  • Mobile responsive verified
  • Accessibility checked (WCAG 2.1)
  • WordPress 7.0 compatibility verified (for new projects)

Related Workflow Bundles

  • development - General web development
  • security-audit - Security testing
  • testing-qa - Testing workflow
  • ecommerce - E-commerce development

(End of file - total 440 lines)

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.