What problem does it solve? Building Wix service plugins (SPIs) requires precise handler signatures, response structures, and a two-step extension registration process that is easy to get wrong, causing plugins to silently fail or never activate. ## Core Features & Use Cases - SPI Implementation Guidance: Step-by-step checklist and code patterns for implementing service plugins with provideHandlers() from @wix/ecom/service-plugins and @wix/bookings/service-plugins. - Seven SPI References: Detailed reference docs for Additional Fees, Discount Triggers, Gift Cards, Shipping Rates, Tax Calculation, Validations, and Bookings Staff Sorting, each with imports, handler signatures, and response schemas. - Extension Registration: Enforces the mandatory two-step registration with builder methods, unique UUIDs, and updates to src/extensions.ts. - Use Case: Add a custom handling fee to every checkout by implementing the Additional Fees SPI, registering it with ecomAdditionalFees(), and verifying with npx wix build. ## Quick Start Ask the assistant to create a Wix service plugin for your chosen SPI type, such as custom shipping rates, and have it read the matching reference doc before writing plugin.ts and extensions.ts.