Headless Ecommerce
Use when the user asks about headless commerce, Shopify Hydrogen, Storefront API, Oxygen, composable commerce or caching a commerce frontend. Produces a headless storefront design: data fetching, cache per data type, cart handling and deployment. Not for checkout and order backends (use ecommerce-checkout-cart) or payments (use ecommerce-payment-processing).
Install
npx skills add j4flmao/agent-skills --skill headless-ecommercegit clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/ecommerce/headless ~/.claude/skills/headless-ecommercePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Headless E-commerce
## Purpose
Build a custom storefront on top of a commerce backend (Shopify, commercetools, BigCommerce, Saleor, Medusa) while keeping catalog pages fast and cacheable and keeping personalized data (cart, customer) uncached and correct. Checkout usually stays on the platform's hosted checkout.
## Agent Protocol
### Trigger
"headless commerce", "hydrogen", "storefront api", "oxygen", "composable commerce", "headless shopify", "storefront caching".
### Input Context
- Commerce platform and plan; whether hosted checkout is required.
- Frontend framework preference (Hydrogen on React Router, Next.js, Astro).
- Catalog size, update frequency, markets/currencies.
### Output Artifact
Architecture + data-fetching/caching plan; route loader code on request.
### Response Format
```
Platform: {backend} Frontend: {framework} Hosting: {Oxygen|Vercel|Cloudflare|...}
Data -> cache: {products: long, collections: short, cart/customer: none}
Checkout: {hosted|custom}
Risks: {list}
```
## When Headless Is Worth It
| Situation | Recommendation |
|-----------|---------------|
| Standard store, theme customization enough | Stay on platform themes (Shopify Online Store 2.0) |
| Custom UX, content-heavy storytelling, multiple frontends (web/app/kiosk) | Headless |
| Small team without frontend ops capacity | Avoid — you now own SEO, performance, analytics, a11y |
| Many markets/brands on one catalog | Headless with shared component library |
## Caching by Data TypeDetails
- Skill name
headless-ecommerce- Repository
- j4flmao/agent-skills
- Path
skills/ecommerce/headless/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Headless Ecommerce skill do?
Use when the user asks about headless commerce, Shopify Hydrogen, Storefront API, Oxygen, composable commerce or caching a commerce frontend. Produces a headless storefront design: data fetching, cache per data type, cart handling and deployment. Not for checkout and order backends (use ecommerce-checkout-cart) or payments (use ecommerce-payment-processing).
How do I install the Headless Ecommerce skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill headless-ecommerce. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Headless Ecommerce popular?
It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.
Related skills
Agent Observability
45j4flmao/agent-skills
Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).
AI Agent Architectures
45j4flmao/agent-skills
Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).
AI Agent Core Loop
45j4flmao/agent-skills
Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).
It Business Analyst
9abhattachar5/BASkill-Claude
Use this skill for IT Business Analysis deliverables in insurance, reinsurance, or financial services. Triggers: writing BRDs, FRDs, user stories, epics, themes, acceptance criteria; creating process flows or swimlane diagrams; building RACI matrices or stakeholder maps; performing gap analysis or impact assessments; breaking features into epics and stories; creating traceability matrices or data dictionaries; source-to-target data mappings; ingesting existing specs, transcripts, wiki pages, or PRDs; estimating stories or epics; drafting stakeholder comms, status updates, or steering briefs; a
Frontend SEO
45j4flmao/agent-skills
Use when the user asks about meta tags, Open Graph and Twitter cards, canonical URLs, generateMetadata, generating sitemap.xml and robots.txt, or SSR for crawlers in a React/Vue/Svelte app. Produces framework metadata code and generated sitemaps. Not for technical SEO audits (use seo-fundamentals) or JSON-LD rich results (use seo-structured-data).
Packaging Distribution
24forcedotcom/partner-ecosystem-agentic-kit
Route and synthesize ISV decisions about packageability, managed 2GP, package architecture, versions, ancestry, promotion, migration, listings, distribution, and upgrades. Use when a partner asks whether or how a Salesforce solution should be packaged or distributed.
Browse the most popular Claude skills, all marketing, sales & business skills, or write your own with the skills generator.