ce-ssr

Build custom Commerce Engine SSR bindings with cookie-backed session storage.

Updated Feb 7, 2026
One-click install
npx skills add https://github.com/tark-ai/ce-starter-projects --skill ce-ssr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-ssr
Source: https://github.com/tark-ai/ce-starter-projects/tree/main/.agents/skills/ce-ssr
Command: npx skills add https://github.com/tark-ai/ce-starter-projects --skill ce-ssr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build custom server-side rendering bindings for frameworks that do not have a first-party Commerce Engine wrapper, providing cookie-based session storage and token management patterns.

Core Features & Use Cases

  • CookieAdapter to normalize cookie APIs into a simple get/set/delete interface.
  • ServerTokenStorage to persist tokens during server-side requests.
  • Guidance for integrating with framework-specific SSR patterns (e.g., Nuxt) and tying PublicStorefrontSDK vs SessionStorefrontSDK flows.

Quick Start

Install and configure @commercengine/ssr-utils, implement a CookieAdapter for your framework, and initialize ServerTokenStorage to bootstrap your SSR binding.

Frequently Asked Questions about ce-ssr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build custom SSR bindings for frameworks without a first-party Commerce Engine wrapper?

You can bridge SSR for unsupported frameworks by installing @commercengine/ssr-utils, implementing a CookieAdapter to normalize cookie APIs, and initializing ServerTokenStorage to manage tokens during server-side rendering.

How does cookie-based session storage work during server-side rendering in Nuxt?

Cookie-based session storage normalizes cookie APIs through a CookieAdapter and persists tokens via ServerTokenStorage, allowing you to maintain user sessions across server-side rendered pages in frameworks like Nuxt.

Can I use Commerce Engine SSR utils with frameworks other than Nuxt?

The SSR utils package is designed for frameworks without first-party wrappers, so you can integrate it into any environment by implementing a custom CookieAdapter that maps your framework's cookie APIs.

Do I need a CookieAdapter and ServerTokenStorage to enable SSR for Commerce Engine?

Both components are required: the CookieAdapter standardizes cookie interactions for your framework, while ServerTokenStorage handles token persistence, together powering the SessionStorefrontSDK in live SSR flows.

What is the difference between PublicStorefrontSDK and SessionStorefrontSDK in server-side rendering?

In server-side rendering, the PublicStorefrontSDK handles public unauthenticated traffic, whereas the SessionStorefrontSDK requires ServerTokenStorage and a CookieAdapter to maintain authenticated user sessions.