← Search

Build Medusa storefronts: JS SDK patterns, React Query, price rules
E-commerce 🧪 Install ran in our test sandbox · Nov 11, 2026 📌 Pinned version: commit 066132d
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: a Medusa project with a storefront to build or…

Build Medusa storefronts: JS SDK patterns, React Query, price rules

Frontend integration skill for Medusa storefronts — always use the JS SDK (never plain fetch), use built-in SDK methods, structure React Query keys hierarchically, never divide prices by 100, handle errors

At a glance
What
Frontend integration skill for Medusa storefronts — always use the JS SDK (never plain fetch), use built-in SDK methods, structure React Query keys hierarchically, never divide prices by 100, handle errors
Cost
Free
Needs
a Medusa project with a storefront to build or extend — the skill is an integration playbook, not software to install
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

Quick answer

Build Medusa storefronts is a free short listing for the frontend integration playbook for building storefronts on Medusa. SDK usage is critical: always use the Medusa JS SDK for every API request and never plain fetch, since missing headers cause silent failures. For built-in endpoints use existing SDK methods, for custom routes use sdk.client.fetch, with React Query patterns.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 066132d

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a Medusa project with a storefront to build or extend — the skill is an integration playbook, not software to install Install "Build Medusa storefronts: JS SDK patterns, React Query, price rules" for me. It gives my agent @medusajs's storefront skill: always use the Medusa JS SDK (never plain fetch), use built-in SDK methods or sdk.client.fetch() for custom routes, follow React Query patterns (useQuery/useMutation, hierarchical keys, invalidation, error handling), display prices as-is (never divide by 100), and load references/frontend-integration.md before writing implementation code. IMPORTANT: the repo's license is unknown — fetch from the link only, and reproduce nothing beyond the link. Repository: https://raw.githubusercontent.com/medusajs/medusa-agent-skills/066132d1c20550cc36c0122e83970eaefe9a2bfd/plugins/medusa-dev/skills/building-storefronts/SKILL.md Pinned version: install the code at commit 066132d1c20550cc36c0122e83970eaefe9a2bfd exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "building-storefronts". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. locate the SDK instantiation in my project first; load references/frontend-integration.md before any implementation work; nothing else — it's a playbook). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit 066132d · 2026-10-13
🧪 Install ran in our test sandbox · Nov 11, 2026
👁 Observed during the install test · Nov 11, 2026 : no network contact
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
066132d · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 11, 2026
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : No commands, network calls, packages, file writes or API keys detected.

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.