wordpress-woocommerce-development
WooCommerce store development workflow covering store setup, payment integration, shipping configuration, and customization.
Best use case
wordpress-woocommerce-development is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
WooCommerce store development workflow covering store setup, payment integration, shipping configuration, and customization.
Teams using wordpress-woocommerce-development should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/wordpress-woocommerce-development/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How wordpress-woocommerce-development Compares
| Feature / Agent | wordpress-woocommerce-development | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
WooCommerce store development workflow covering store setup, payment integration, shipping configuration, and customization.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# WordPress WooCommerce Development Workflow ## Overview Specialized workflow for building WooCommerce stores including setup, payment gateway integration, shipping configuration, custom product types, and store optimization. ## When to Use This Workflow Use this workflow when: - Setting up WooCommerce stores - Integrating payment gateways - Configuring shipping methods - Creating custom product types - Building subscription products ## Workflow Phases ### Phase 1: Store Setup #### Skills to Invoke - `app-builder` - Project scaffolding - `wordpress-penetration-testing` - WordPress patterns #### Actions 1. Install WooCommerce 2. Run setup wizard 3. Configure store settings 4. Set up tax rules 5. Configure currency #### Copy-Paste Prompts ``` Use @app-builder to set up WooCommerce store ``` ### Phase 2: Product Configuration #### Skills to Invoke - `wordpress-penetration-testing` - WooCommerce patterns #### Actions 1. Create product categories 2. Add product attributes 3. Configure product types 4. Set up variable products 5. Add product images #### Copy-Paste Prompts ``` Use @wordpress-penetration-testing to configure WooCommerce products ``` ### Phase 3: Payment Integration #### Skills to Invoke - `payment-integration` - Payment processing - `stripe-integration` - Stripe - `paypal-integration` - PayPal #### Actions 1. Choose payment gateways 2. Configure Stripe 3. Set up PayPal 4. Add offline payments 5. Test payment flows #### Copy-Paste Prompts ``` Use @stripe-integration to integrate Stripe payments ``` ``` Use @paypal-integration to integrate PayPal ``` ### Phase 4: Shipping Configuration #### Skills to Invoke - `wordpress-penetration-testing` - WooCommerce shipping #### Actions 1. Set up shipping zones 2. Configure shipping methods 3. Add flat rate shipping 4. Set up free shipping 5. Integrate carriers #### Copy-Paste Prompts ``` Use @wordpress-penetration-testing to configure shipping ``` ### Phase 5: Store Customization #### Skills to Invoke - `frontend-developer` - Store customization - `frontend-design` - Store design #### Actions 1. Customize product pages 2. Modify cart page 3. Style checkout flow 4. Create custom templates 5. Add custom fields #### Copy-Paste Prompts ``` Use @frontend-developer to customize WooCommerce templates ``` ### Phase 6: Extensions #### Skills to Invoke - `wordpress-penetration-testing` - WooCommerce extensions #### Actions 1. Install required extensions 2. Configure subscriptions 3. Set up bookings 4. Add memberships 5. Integrate marketplace #### Copy-Paste Prompts ``` Use @wordpress-penetration-testing to configure WooCommerce extensions ``` ### Phase 7: Optimization #### Skills to Invoke - `web-performance-optimization` - Performance - `database-optimizer` - Database optimization #### Actions 1. Optimize product images 2. Enable caching 3. Optimize database 4. Configure CDN 5. Set up lazy loading #### Copy-Paste Prompts ``` Use @web-performance-optimization to optimize WooCommerce store ``` ### Phase 8: Testing #### Skills to Invoke - `playwright-skill` - E2E testing - `test-automator` - Test automation #### Actions 1. Test checkout flow 2. Verify payment processing 3. Test email notifications 4. Check mobile experience 5. Performance testing #### Copy-Paste Prompts ``` Use @playwright-skill to test WooCommerce checkout flow ``` ## Quality Gates - [ ] Products displaying correctly - [ ] Checkout flow working - [ ] Payments processing - [ ] Shipping calculating - [ ] Emails sending - [ ] Mobile responsive ## Related Workflow Bundles - `wordpress` - WordPress development - `wordpress-theme-development` - Theme development - `wordpress-plugin-development` - Plugin development - `payment-integration` - Payment processing
Related Skills
managing-autonomous-development
Enables Claude to manage Sugar's autonomous development workflows. It allows Claude to create tasks, view the status of the system, review pending tasks, and start autonomous execution mode. Use this skill when the user asks to create a new development task using `/sugar-task`, check the system status with `/sugar-status`, review pending tasks via `/sugar-review`, or initiate autonomous development using `/sugar-run`. It provides a comprehensive interface for interacting with the Sugar autonomous development system.
overnight-development
Automates software development overnight using git hooks to enforce test-driven Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
ros2-development
Comprehensive best practices, design patterns, and common pitfalls for ROS2 (Robot Operating System 2) development. Use this skill when building ROS2 nodes, packages, launch files, components, or debugging ROS2 systems. Trigger whenever the user mentions ROS2, colcon, rclpy, rclcpp, DDS, QoS, lifecycle nodes, managed nodes, ROS2 launch, ROS2 parameters, ROS2 actions, nav2, MoveIt2, micro-ROS, or any ROS2-era robotics middleware. Also trigger for ROS2 workspace setup, DDS tuning, intra-process communication, ROS2 security, or deploying ROS2 in production. Also trigger for colcon build issues, ament_cmake, ament_python, CMakeLists.txt for ROS2, package.xml dependencies, rosdep, workspace overlays, custom message generation, or ROS2 build troubleshooting. Covers Humble, Iron, Jazzy, and Rolling distributions.
ros1-development
Best practices, design patterns, and common pitfalls for ROS1 (Robot Operating System 1) development. Use this skill when building ROS1 nodes, packages, launch files, or debugging ROS1 systems. Trigger whenever the user mentions ROS1, catkin, rospy, roscpp, roslaunch, roscore, rostopic, tf, actionlib, message types, services, or any ROS1-era robotics middleware. Also trigger for migrating ROS1 code to ROS2, maintaining legacy ROS1 systems, or building ROS1-ROS2 bridges. Covers catkin workspaces, nodelets, dynamic reconfigure, pluginlib, and the full ROS1 ecosystem.
docker-ros2-development
Best practices for Docker-based ROS2 development including multi-stage Dockerfiles, docker-compose for multi-container robotic systems, DDS discovery across containers, GPU passthrough for perception, and dev-vs-deploy container patterns. Use this skill when containerizing ROS2 workspaces, setting up docker-compose for robot software stacks, debugging DDS communication between containers, configuring NVIDIA Container Toolkit for GPU workloads, forwarding X11/Wayland for rviz2 and GUI tools, or managing USB device passthrough for cameras and serial devices. Trigger whenever the user mentions Docker with ROS2, docker-compose for robots, Dockerfile for colcon workspaces, container networking for DDS, GPU containers for perception, devcontainer for ROS2, multi-stage builds for ROS2, or deploying ROS2 in containers. Also trigger for CI/CD with Docker-based ROS2 builds, CycloneDDS or FastDDS configuration in containers, shared memory in Docker, or X11 forwarding for rviz2. Covers Humble, Iron, Jazzy, and Rolling distributions across Ubuntu 22.04 and 24.04 base images.
apify-actor-development
Develop, debug, and deploy Apify Actors - serverless cloud programs for web scraping, automation, and data processing. Use when creating new Actors, modifying existing ones, or troubleshooting Actor code.
docker-development
Docker and container development agent skill and plugin for Dockerfile optimization, docker-compose orchestration, multi-stage builds, and container security hardening. Use when: user wants to optimize a Dockerfile, create or improve docker-compose configurations, implement multi-stage builds, audit container security, reduce image size, or follow container best practices. Covers build performance, layer caching, secret management, and production-ready container patterns.
woocommerce-markdown
Guidelines for creating and modifying markdown files in WooCommerce. Use when writing documentation, README files, or any markdown content.
woocommerce-dev-cycle
Run tests, linting, and quality checks for WooCommerce development. Use when running tests, fixing code style, or following the development workflow.
woocommerce-copy-guidelines
Guidelines for UI text and copy in WooCommerce. Use when writing user-facing text, labels, buttons, or messages.
woocommerce-code-review
Review WooCommerce code changes for coding standards compliance. Use when reviewing code locally, performing automated PR reviews, or checking code quality.
woocommerce-backend-dev
Add or modify WooCommerce backend PHP code following project conventions. Use when creating new classes, methods, hooks, or modifying existing backend code. **MUST be invoked before writing any PHP unit tests.**