Przejdź do treści
Biblioteka skilli
Programowanie · Budowanie i kod

headless-nextjs-storefront

/headless-nextjs-storefront

Buduje sklep Next.js, który ładuje katalog po stronie serwera, trzyma sekrety z dala od klienta i odświeża ceny oraz stany magazynowe.

Licencja
MIT
Ostatnia zmiana repozytorium
04.11.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
5
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 04.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Buduje sklep Next.js, który ładuje katalog po stronie serwera, trzyma sekrety z dala od klienta i odświeża ceny oraz stany magazynowe.

Oryginalny opis (EN)

Build a Next.js storefront that loads catalog data on the server, keeps admin secrets off the client, and revalidates price and stock. Use when adding product, cart, or checkout UI in a Next.js App Router storefront for WooCommerce or another headless commerce API.

Jak działa

  1. Procedure
  2. Data split
  3. WooCommerce storefront
  4. Shopify storefront
  5. Rendering
  6. Gotchas
  7. Verification
  8. Evaluation
Sekcje z nagłówków SKILL.md, w oryginale · 62 linii, 677 słów
Podgląd SKILL.md
---
name: headless-nextjs-storefront
description: "Build a Next.js storefront that loads catalog data on the server, keeps admin secrets off the client, and revalidates price and stock. Use when adding product, cart, or checkout UI in a Next.js App Router storefront for WooCommerce or another headless commerce API."
license: MIT
metadata:
  author: Naser Sadrmanesh
  version: "0.3.3"
---

# Headless Next.js storefront

Use this skill for a Next.js storefront that talks to a commerce API. WooCommerce HTTP details are in the REST API skill. Shopify admin apps are a different skill. Checkout field behavior is the checkout skill.

This skill assumes the App Router (`app/`). Do not pin a Next.js major version you have not installed. Use the cache and route APIs that version documents.

## Procedure

1. Render product and category pages from the server. The HTML should contain the price and availability a shopper and a crawler see.
2. Keep admin credentials and WooCommerce consumer secrets in server environment variables. Never import them into a client component.
3. Use the public storefront API for the cart. For WooCommerce that is the Store API (`/wp-json/wc/store/v1/`), with its cart token and nonce. It is not `wc/v3`.
4. Cache catalog reads. Invalidate that cache when price or stock changes. Do not cache a cart response as if it were a public product.
5. Re-check the charged total on the server when checkout starts. The figure in React state is not the amount to capture.

Cache and cart boundaries are in [the cache notes](references/cache-and-cart.md). Worked examples and checks are in [evals/tasks.json](evals/tasks.json).

## Data split

| Data | Where it is read | Cache |
| --- | --- | --- |
| Product title, price, stock, images | Server component or a route handler | Public cache with a tag such as `product:<id>` |
| Cart and checkout session | Server route that forwards the shopper's cart token | Do not use the public product cache |
| Admin writes | Server only, with the admin credential | Do not expose the route to the browser without your own auth |

Call `revalidateTag('product:<id>')` or `revalidatePath` from the server path that handles the catalog webhook. A client component cannot import `next/cache` revalidation and run it in the browser.

## WooCommerce storefront

- Product pages may use a read-only integration on the server. Prefer a key that cannot write, or a public product endpoint your store already exposes.
- Cart requests send the `Cart-Token` the Store API returned. Store that token in an HTTP-only cookie set by your server route, not in `localStorage`, if the token would let someone else modify the cart.
- The browser calls your Next.js route. Your route calls WooCommerce. Do not point the browser at `wc/v3` with a consumer secret.

## Shopify storefront

- Use the Storefront API for product and cart reads. The Storefront access token is still a secret if it can create checkouts. Follow the token type Shopify documents for that API.
- Do not send the Admin API token to the browser.

## Rendering

- Format money with the storefront locale on the server so the HTML and the JSON-LD match. Persian digits belong in visible text, not in the amount you post to checkout. See the RTL skill.
- Variant selection updates the visible price to that variant before add-to-cart.
- Out-of-stock variants stay disabled even if a cached page is briefly stale. The add-to-cart route checks stock again.

## Gotchas

- `cache: 'force-cache'` on a cart GET will show one shopper another shopper's cart if the URL does not vary. Do not cache cart responses on a shared key.
- A webhook that updates stock must revalidate the product tag. Restarting the Next.js process is not an invalidation strategy.
- Client-side `fetch` to a route that embeds the admin secret in the response will leak it into the browser. Return only the fields the UI needs.
- Draft-mode or preview cookies should not be cached as public product HTML.

## Verification

- The built HTML for a product contains the price without requiring client JavaScript.
- Searching the client bundle finds no consumer secret and no Admin API token.
- Updating a price and delivering the catalog webhook changes the next product response without a redeploy.
- Two browsers do not share a cart token.

## Evaluation

Worked examples and the checks they must satisfy are in [evals/tasks.json](evals/tasks.json).
Pliki w paczce (5)
  • SKILL.md 4 KB
  • evals/tasks.json 1 KB
  • evals/examples/revalidate-stock.md 1 KB
  • evals/examples/server-price.md 1 KB
  • references/cache-and-cart.md 2 KB

Wersje

W bazie nie ma innych skilli o nazwie headless-nextjs-storefront.

Migawka bazy z 13.11.2026 · wersja paczki 0b4c7d3c134e (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100bc-headless
    Buduje headless commerce z BigCommerce: Catalyst (referencyjny storefront Next.js), GraphQL Storefront API, API po stronie serwera, osadzony checkout i wzorce architektury headless.
  • 100shopify-storefront-headless
    Buduje sklepy headless z Storefront API i Cart API Shopify: własne frontendy, konfiguracja Hydrogen, zapytania o produkty i programowe operacje na koszyku.
  • 95headless-ecommerce
    Projektuje bezgłowe sklepy internetowe na Shopify Hydrogen i Storefront API: pobieranie danych, cache dla każdego typu danych, koszyk i wdrożenie.
  • 100medusa-storefront
    Buduje sklepy headless na Medusa v2 z Next.js 15: App Router, klient JS SDK, Tanstack Query, komponenty serwerowe, strony produktów, koszyk i finalizacja zakupu.
  • 100shopify
    Buduje i dostosowuje sklepy Shopify: motywy w Liquid, Storefront API, własne aplikacje i headless commerce z Hydrogen, z zarządzaniem produktami i kasą.
  • 91commerce-storefront
    Tworzy nowe sklepy internetowe i szkielety projektów e-commerce oraz aplikacje handlowe z użyciem StateSet.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.