What problem does it solve? Building Wix service plugins (SPIs) requires exact handler signatures, response schemas, and a two-step extension registration process that is easy to get wrong. This Skill guides the implementation of custom backend logic for Wix business solutions so plugins compile, register, and respond correctly when Wix calls them. ## Core Features & Use Cases - SPI Implementation Guidance: Step-by-step patterns for Additional Fees, Shipping Rates, Tax Calculation, Validations, Discount Triggers, Gift Cards, and Bookings Staff Sorting plugins using provideHandlers(). - Extension Registration: Enforces the mandatory two-step registration with builder methods like ecomShippingRates() and bookingsStaffSortingProvider(), including unique UUID generation and src/extensions.ts updates. - Schema-First Workflow: Directs reading reference docs and calling ReadFullDocsMethodSchema before writing any code, plus permission elevation with auth.elevate for Wix API calls. - Use Case: A developer needs to add a handling fee to every checkout. The Skill walks them through creating plugin.ts with calculateAdditionalFees, registering it via ecomAdditionalFees(), and verifying with npx wix build. ## Quick Start Ask the assistant to create a Wix service plugin for your scenario, for example: "Create an additional fees service plugin that adds a $5 handling fee to every order."