chore(release): publish content (#20)

Co-authored-by: ct-sdks[bot] <153784748+ct-sdks[bot]@users.noreply.github.com>

Author: ct-sdks[bot]

.agents/plugins/commercetools/skills/commercetools-checkout/SKILL.md

@@ -1,8 +1,8 @@
 ---
 name: commercetools-checkout
-description: The commercetools Checkout product — payment-only mode (integrating commercetools Checkout for payments while owning the rest of the flow), full hosted checkout (checkoutFlow), widget integration via @commercetools/checkout-browser-sdk, configuration, PSP connector setup (Stripe, Adyen, Mollie), and webhook handling. Use when integrating commercetools Checkout (the product) into a storefront or headless app — not for generic cart-to-order patterns (see commercetools-storefront).
+description: The Checkout — payment-only mode (integrating Checkout for payments while owning the rest of the flow), full hosted checkout (checkoutFlow), widget integration via @commercetools/checkout-browser-sdk, configuration, PSP connector setup (Stripe, Adyen, Mollie), and webhook handling. Use when integrating Checkout (the product) into a storefront or headless app — not for generic cart-to-order patterns (see commercetools-storefront).
 when_to_use:
-  - "Integrating the commercetools Checkout product into a storefront or headless app"
+  - "Integrating the Checkout into a storefront or headless app"
   - "Setting up payment-only mode while keeping existing address and shipping flows"
   - "Configuring PSP connectors such as Stripe, Adyen, or Mollie"
   - "Handling payment webhooks and order confirmation"
@@ -14,15 +14,15 @@ metadata:
     - psp
 ---
 
-# commercetools Checkout
+# Checkout
 
-The commercetools Checkout product provides hosted payment and checkout experiences via the Browser SDK.
+The Checkout provides hosted payment and checkout experiences via the Browser SDK.
 
 ## Integration Modes
 
-Three modes — choose based on how much of the checkout flow commercetools Checkout should own:
+Three modes — choose based on how much of the checkout flow Checkout should own:
 
-- **`paymentFlow`** (payment-only) — keep existing address/shipping UI, replace only the payment step with the commercetools Checkout widget. Least invasive.
+- **`paymentFlow`** (payment-only) — keep existing address/shipping UI, replace only the payment step with the Checkout widget. Least invasive.
 - **`checkoutFlow`** (full hosted) — replace the entire multi-step checkout with a single commercetools-hosted page covering address, shipping, and payment.
 - **`expressPayment`** — add Apple Pay / Google Pay express buttons to cart or PDP. Can coexist with either mode above.
 
@@ -48,7 +48,7 @@ When this skill is invoked, always follow these steps:
 ## References
 
 See [payment-only-mode.md](./references/payment-only-mode.md) for:
-- Full architecture diagram (Browser SDK → commercetools Checkout service → PSP)
+- Full architecture diagram (Browser SDK → Checkout service → PSP)
 - Session creation (`/api/checkout/session` → commercetools Sessions API)
 - `paymentFlow`, `checkoutFlow`, and `expressPayment` implementation patterns
 - PSP connector setup (Stripe, Adyen, Mollie)

.agents/plugins/commercetools/skills/commercetools-checkout/references/payment-only-mode.md

@@ -1,10 +1,10 @@
 ---
 name: payment-only-mode
-description: Implementation guide for integrating the commercetools Checkout Browser SDK with payment-only mode (paymentFlow), full hosted checkout (checkoutFlow), and express payment buttons.
+description: Implementation guide for integrating the Checkout Browser SDK with payment-only mode (paymentFlow), full hosted checkout (checkoutFlow), and express payment buttons.
 when_to_use:
-  - "Integrating the commercetools Checkout product into a headless or hosted storefront"
+  - "Integrating the Checkout into a headless or hosted storefront"
   - "Replacing only the payment step while keeping existing address and shipping flows"
-  - "Setting up Stripe, Adyen, Mollie, or other PSP connectors via commercetools Checkout Applications"
+  - "Setting up Stripe, Adyen, Mollie, or other PSP connectors via Checkout Applications"
   - "Implementing order creation via commercetools Sessions API and handling post-payment confirmation"
 metadata:
   contentType: REFERENCE
@@ -15,9 +15,9 @@ metadata:
     - sdk
 ---
 
-# commercetools Checkout Integration
+# Checkout Integration
 
-Adds payment processing via the [commercetools Checkout Browser SDK](https://docs.commercetools.com/checkout/browser-sdk).
+Adds payment processing via the [Checkout Browser SDK](https://docs.commercetools.com/checkout/browser-sdk).
 
 ---
 
@@ -27,7 +27,7 @@ Adds payment processing via the [commercetools Checkout Browser SDK](https://doc
 
 1. **Which checkout mode?**
    - `paymentFlow` — payment-only: keep existing address/shipping steps, replace only `StepPayment.tsx` with the commercetools widget. Least invasive.
-   - `checkoutFlow` — full page: replace the entire multi-step checkout with a single commercetools-hosted checkout page (addresses, shipping, and payment all handled by commercetools Checkout).
+   - `checkoutFlow` — full page: replace the entire multi-step checkout with a single commercetools-hosted checkout page (addresses, shipping, and payment all handled by Checkout).
    - `expressPayment` — express buttons: add Apple Pay / Google Pay buttons to the cart or PDP. Can coexist with either of the above.
 
 2. **Which PSP (Payment Service Provider)?**
@@ -38,9 +38,9 @@ Adds payment processing via the [commercetools Checkout Browser SDK](https://doc
 ## Architecture Overview
 
 ```
-Browser (SDK)  →  commercetools Checkout service  →  PSP
+Browser (SDK)  →  Checkout service  →  PSP
                        ↑
-      /api/checkout/session  (creates commercetools Checkout Session from cart)
+      /api/checkout/session  (creates Checkout Session from cart)
                        ↑
       commercetools Sessions API  (POST https://session.{region}.commercetools.com/{projectKey}/sessions)
 ```
@@ -54,7 +54,7 @@ The storefront creates a **Checkout Session** (server-side, via a new API route)
 ### 0a. Add environment variables to `site/.env`
 
 ```bash
-# The key of your commercetools Checkout Application
+# The key of your Checkout Application
 CTP_CHECKOUT_APP_KEY=storefront-checkout
 ```
 
@@ -182,19 +182,19 @@ export default function StepPayment() {
 
 In Checkout page, the payment step should render the PaymentStep.tsx
 
-> **Note**: With `paymentFlow`, commercetools Checkout handles the payment AND the **order is created by commercetools** automatically when payment succeeds (via the `paymentReturnUrl` configured in the Application). 
+> **Note**: With `paymentFlow`, Checkout handles the payment AND the **order is created by commercetools** automatically when payment succeeds (via the `paymentReturnUrl` configured in the Application). 
 
 ---
 
-## Step 3 — Order confirmation after commercetools Checkout
+## Step 3 — Order confirmation after Checkout
 
-commercetools Checkout navigates the browser to `paymentReturnUrl` after a successful payment, appending `?orderId=<id>` (or `?orderNumber=<n>`). Update the confirmation page to read these params:
+Checkout navigates the browser to `paymentReturnUrl` after a successful payment, appending `?orderId=<id>` (or `?orderNumber=<n>`). Update the confirmation page to read these params:
 
 ---
 
 ## Step 5 — Styling
 
-Optional: Override commercetools Checkout widget styles via the `styles` option (CSS custom properties):
+Optional: Override Checkout widget styles via the `styles` option (CSS custom properties):
 
 ```typescript
 checkoutFlow({
@@ -208,15 +208,15 @@ checkoutFlow({
 });
 ```
 
-Available CSS variables are listed in the commercetools Checkout theming docs.
+Available CSS variables are listed in the Checkout theming docs.
 
 ---
 
 ## Environment Variable Summary
 
 | Variable | Secret? | Purpose |
 |---|---|---|
-| `CTP_CHECKOUT_APP_KEY` | No | **New** — key of the commercetools Checkout Application |
+| `CTP_CHECKOUT_APP_KEY` | No | **New** — key of the Checkout Application |
 
 
 No `CT_REGION`, `NEXT_PUBLIC_CT_PROJECT_KEY`, or `NEXT_PUBLIC_CT_REGION` variables are needed. The session API derives the region from `CTP_API_URL` and returns `{ sessionId, projectKey, region }` to the browser.

.agents/plugins/commercetools/skills/commercetools-storefront/examples/prompts/b2c/scaffold.md

@@ -9,7 +9,7 @@ Generate a complete production ready B2C storefront connected to commercetools.
 3. product-listing + facets
 4. product-detail
 5. cart
-6. checkout: create complete integration with paymentflow of commercetools checkout but keep the application key as const
+6. checkout: create complete integration with paymentflow of Checkout but keep the application key as const
 7. customer authentication and registration
 8. search page + facets
 9. wishlist

.agents/plugins/commercetools/skills/commercetools-storefront/references/b2b/checkout.md

@@ -37,17 +37,17 @@ The address step reads saved addresses from the active business unit, not from t
 ### Order Placement Sequence
 
 ```
-addresses (shipping + billing) → shipping method → payment (commercetools checkout SDK) → confirmation
+addresses (shipping + billing) → shipping method → payment (Checkout SDK) → confirmation
 ```
 
 1. **Addresses step** — shipping and billing addresses persisted to cart when moving to the next step. All cart writes use the as-associate chain — see the [reference](./cart.md).
 2. **Shipping step** — user selects a method with `shippingMethodId`
-3. **Payment step** — commercetools checkout frontend SDK mounts and handles payment capture and order placement. If a PO Number payment method is configured in the commercetools checkout frontend SDK, it will appear automatically — no custom PO Number field is needed in the checkout form.
+3. **Payment step** — Checkout frontend SDK mounts and handles payment capture and order placement. If a PO Number payment method is configured in the Checkout frontend SDK, it will appear automatically — no custom PO Number field is needed in the checkout form.
 4. **Confirmation** — SDK signals completion → clear `cartId` from session → redirect to `/checkout/confirmation?orderId=<id>`
 
-Order placement is handled entirely by the commercetools checkout frontend SDK. Do not implement a separate `POST /api/checkout` route for order creation.
+Order placement is handled entirely by the Checkout frontend SDK. Do not implement a separate `POST /api/checkout` route for order creation.
 
-> **Reference:** See the [commercetools checkout frontend SDK](../../../commercetools-checkout/references/payment-only-mode.md) implementation skill for SDK setup and the order-completion event handler.
+> **Reference:** See the [Checkout frontend SDK](../../../commercetools-checkout/references/payment-only-mode.md) implementation skill for SDK setup and the order-completion event handler.
 
 ### BU + Store Validation
 
@@ -102,8 +102,8 @@ After submission, the quote progresses through seller review and negotiation. Se
 - [ ] Address step reads BU addresses, auto-selects `defaultShippingAddressId` / `defaultBillingAddressId`
 - [ ] All cart writes in checkout use the as-associate chain
 - [ ] `session.businessUnitKey` and `session.storeKey` validated before rendering checkout
-- [ ] Order placement driven by commercetools checkout frontend SDK — no custom order route for cart checkout
-- [ ] PO Number not added manually — relies on commercetools checkout SDK configuration if needed
+- [ ] Order placement driven by Checkout frontend SDK — no custom order route for cart checkout
+- [ ] PO Number not added manually — relies on Checkout SDK configuration if needed
 - [ ] Confirmation page handles `order.orderState === 'Open'` (approval pending) gracefully
 - [ ] Cart page shows **Request a Quote** button below the Checkout button
 - [ ] Quote request flow: addresses and shipping use the same BU patterns as Flow 1

.agents/plugins/commercetools/skills/commercetools-storefront/references/b2c/checkout.md

@@ -30,17 +30,17 @@ Saved addresses are display-only in the selector — editing or adding a new add
 ## Order Placement Sequence
 
 ```
-addresses (shipping + billing) → shipping method → payment (commercetools checkout SDK) → confirmation
+addresses (shipping + billing) → shipping method → payment (Checkout SDK) → confirmation
 ```
 
 1. **Addresses step** — shipping and billing addresses persisted to cart in real time
 2. **Shipping step** — user selects a method
-3. **Payment step** — commercetools checkout frontend SDK mounts, handles payment capture and order placement
+3. **Payment step** — Checkout frontend SDK mounts, handles payment capture and order placement
 4. **Confirmation** — SDK signals completion → clear `cartId` from session → redirect to `/checkout/confirmation?orderId=<id>`
 
-Order placement is handled entirely by the commercetools checkout frontend SDK on the payment step. Do not implement a separate `POST /api/checkout` route for order creation.
+Order placement is handled entirely by the Checkout frontend SDK on the payment step. Do not implement a separate `POST /api/checkout` route for order creation.
 
-> **Reference:** See the [commercetools checkout frontend SDK](../../../commercetools-checkout/references/payment-only-mode.md) implementation skill for SDK setup and the order-completion event handler.
+> **Reference:** See the [Checkout frontend SDK](../../../commercetools-checkout/references/payment-only-mode.md) implementation skill for SDK setup and the order-completion event handler.
 
 ---
 
@@ -51,5 +51,5 @@ Order placement is handled entirely by the commercetools checkout frontend SDK o
 - [ ] Saved address list shown as selectable options; manual entry also allowed
 - [ ] Address changes debounced to `PATCH /api/cart` (inherited from shared)
 - [ ] Shipping method filtered by session currency (inherited from shared)
-- [ ] Order placement driven by commercetools checkout frontend SDK — no custom order route
+- [ ] Order placement driven by Checkout frontend SDK — no custom order route
 - [ ] `cartId` cleared from session after SDK order completion event

.agents/plugins/commercetools/skills/commercetools-storefront/references/b2c/overview.md

@@ -15,7 +15,7 @@ metadata:
 
 # Next.js + commercetools B2C Storefront
 
-Production-tested patterns for building a B2C storefront on commercetools with Next.js 16, TypeScript, Tailwind v4, and JWT sessions. Derived from the b2c-starter-kit — a working production storefront.
+Production-tested patterns for building a B2C storefront on commercetools with Next.js 16, TypeScript, Tailwind v4, and JWT sessions. 
 
 > **Shared foundation:** BFF architecture, JWT session setup, commercetools SDK singleton, project scaffold, `COUNTRY_CONFIG`, performance patterns, image config, Vercel deployment, and the shared auth base are in the `commercetools-storefront` skill. Load that skill alongside this one when starting a new project.
 

.agents/plugins/commercetools/skills/commercetools-storefront/references/core/checkout-page.md

@@ -4,7 +4,7 @@ description: Multi-step checkout structure, address step, shipping method select
 when_to_use:
   - "Building the checkout flow"
   - "Implementing shipping method selection"
-  - "Integrating the payment step with commercetools checkout SDK"
+  - "Integrating the payment step with Checkout SDK"
   - "Handling order confirmation pages"
 metadata:
   contentType: REFERENCE
@@ -17,13 +17,13 @@ metadata:
 
 **Impact: HIGH — The checkout route is the revenue path. A failed order placement or stale cart version drops the conversion entirely.**
 
-This reference covers the shared checkout structure used by both B2C and B2B storefronts: the multi-step page shell, shipping method selection, payment via the commercetools checkout frontend SDK, and the confirmation page. Address step details and order placement are storefront-specific — see the relevant extension file.
+This reference covers the shared checkout structure used by both B2C and B2B storefronts: the multi-step page shell, shipping method selection, payment via the Checkout frontend SDK, and the confirmation page. Address step details and order placement are storefront-specific — see the relevant extension file.
 
 ## Table of Contents
 - [Pattern 1: Multi-Step Checkout Page Structure](#pattern-1-multi-step-checkout-page-structure)
 - [Pattern 2: Address Step](#pattern-2-address-step)
 - [Pattern 3: Shipping Method Selection](#pattern-3-shipping-method-selection)
-- [Pattern 4: Payment Step — commercetools Checkout Frontend SDK](#pattern-4-payment-step--commercetools-checkout-frontend-sdk)
+- [Pattern 4: Payment Step — Checkout Frontend SDK](#pattern-4-payment-step--commercetools-checkout-frontend-sdk)
 - [Pattern 5: Confirmation Page](#pattern-5-confirmation-page)
 - [Checklist](#checklist)
 
@@ -121,11 +121,11 @@ When the user selects a method, `PATCH /api/cart` with `shippingMethodId` and up
 
 ---
 
-## Pattern 4: Payment Step — commercetools Checkout Frontend SDK
+## Pattern 4: Payment Step — Checkout Frontend SDK
 
-The payment step is handled entirely by the commercetools checkout frontend SDK, which renders the full payment UI and drives order placement.
+The payment step is handled entirely by the Checkout frontend SDK, which renders the full payment UI and drives order placement.
 
-> **Reference:** See the [commercetools checkout frontend SDK](../../../commercetools-checkout/references/payment-only-mode.md) implementation skill for full setup, component mounting, and event handling.
+> **Reference:** See the [Checkout frontend SDK](../../../commercetools-checkout/references/payment-only-mode.md) implementation skill for full setup, component mounting, and event handling.
 
 Key rules:
 - Do not implement a custom payment form — mount the SDK component and let it manage the flow.
@@ -169,6 +169,6 @@ Both flows (cart checkout and quote checkout) redirect to `/checkout/confirmatio
 - [ ] Step skip guards redirect back if prerequisites are not met
 - [ ] `GET /api/shipping-methods` filters by session currency
 - [ ] Address changes debounced to update cart address method
-- [ ] Payment step mounts the commercetools checkout frontend SDK — no custom payment form
+- [ ] Payment step mounts the Checkout frontend SDK — no custom payment form
 - [ ] `cartId` cleared from session after the SDK signals order completion
 - [ ] Confirmation page is a Server Component that fetches order by ID from commercetools