What problem does it solve?
Adding or modifying endpoints under the WooCommerce Store API (/wc/store/v1/*) involves subtle conventions around authentication, schema contracts, variation reconciliation, and idempotency that are easy to get wrong, leading to CSRF vulnerabilities, N+1 query problems, and broken client integrations.
Core Features & Use Cases
- Authentication guidance: Choose between
AbstractRoute and AbstractCartRoute, enforce nonces correctly, and write conventional permission_callback closures.
- Schema and REST conventions: Keep schemas as the single source of truth, apply correct status codes, design collection vs action routes, and build idempotent storage keys.
- Variation handling and performance: Reconcile variation attributes server-side and apply cache priming to avoid N+1 queries in collection responses.
- Use Case: When adding a new POST endpoint that lets shoppers save preferences to their cart, use this Skill to pick the right abstract route class, wire nonce validation, design the response schema, and write the required auth tests.
Quick Start
Use the woocommerce-store-api skill to help me add a new Store API endpoint for managing saved cart item notes with proper nonce handling and schema design.