enable-shopify-menus
Skill137 starsChanged 22 days agoMITView on GitHub
Replace the hardcoded nav and footer links with Shopify-managed menus, cached until a protected endpoint refreshes them.
- Reads credentials
- Sends data out
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- build-shopSkill
- enable-analyticsSkill
- enable-i18nSkill
- enable-shopify-marketsSkill
- init-vercel-shopSkill
- shopify-graphql-referenceSkill
- update-shopSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Ask the user two questions in order:
- Very specific: line 24
Ask for each selected menu.
- Distinctive: line 26
Wait for the user to answer before proceeding.
- Very specific: line 32
Create lib/shopify/operations/menu/server.ts.
- Distinctive: line 116
If you add fields, validate the document with the Shopify AI Toolkit first.
- Distinctive: line 193
Keep the inline fallbacks so a missing menu or Storefront error never leaves a blank nav.
- Very specific: line 194
Keep cacheLife("max") with the menus tag and refresh through POST /api/revalidate.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Enable Shopify Menus
By default, the storefront's nav renders an inline const items: MenuItem[] = [...] in Nav (components/nav/index.tsx), and the footer renders an empty const items: MenuItem[] = [] in Footer (components/footer/index.tsx). QuickLinks, MobileMenu, and Footer's FooterMenu already render MenuItem[] from lib/menu/types.ts, up to three levels deep in the nav and two in the footer.
This skill adds a cached Shopify menu read and points the selected components at it with the inline items as fallback. Shopify sends no webhook when a menu changes, so menus stay cached until the storefront's protected POST /api/revalidate endpoint is called with the menus tag.
Before you start
Ask the user two questions in order:
1. Which menus do you want to fetch from Shopify?
- Nav menu — replaces the hardcoded items used by the desktop quick links and mobile sheet.
- Footer menu — adds footer columns.
- Both
2. What are the Shopify menu handles?
Ask for each selected menu. Defaults: main-menu for nav, footer for footer. Every Shopify store starts with both.
Wait for the user to answer before proceeding.
1. Add the menu operation
Create lib/shopify/operations/menu/server.ts. Shopify returns absolute item URLs on the store's myshopify or primary domain, sometimes with a Markets locale prefix; the operation turns those into storefront paths and leaves external links alone.
import { gql } from "@shopify/hydrogen";
import { shopConfig } from "@/lib/config";
import type { CommerceLocale } from "@/lib/config/types";
import type { MenuItem } from "@/lib/menu/types";
import { assertStorefrontOk } from "@/lib/shopify/errors/server";
import { storefront } from "@/lib/shopify/storefront/server";
const GET_MENU_QUERY = gql(`#graphql
query getMenu($handle: String!, $country: CountryCode, $language: LanguageCode) @inContext(country: $country, language: $language) {
shop {
primaryDomain {
url
}
}
menu(handle: $handle) {
items {
id
title
url
items {
id
title
url
items {
id
title
url
}
}
}
}
}
`);
function toStorefrontUrl(url: string | null | undefined, internalHosts: string[]): string {
if (!url) return "/";
let parsed: URL;
try {
parsed = new URL(url);
} catch {
return url;
}
if (!internalHosts.includes(parsed.hostname)) return url;
const path = parsed.pathname.replace(/^\/[a-z]{2}(?:-[a-z]{2,4})?(?=\/|$)/i, "") || "/";
return `${path}${parsed.search}${parsed.hash}`;
}
export async function fetchMenu({
handle,
locale = shopConfig.localization,
}: {
handle: string;
locale?: CommerceLocale;
}): Promise<MenuItem[] | null> {
const response = await storefront.request(GET_MENU_QUERY, { locale, variables: { handle } });
assertStorefrontOk(response, "getMenu");
const menu = response.data.menu;
if (!menu || menu.items.length === 0) return null;
const internalHosts = [
process.env.NEXT_PUBLIC_SHOPIFY_STORE_DOMAIN ?? "",
new URL(response.data.shop.primaryDomain.url).hostname,
];
const link = ({ id, title, url }: { id: string; title: string; url?: string | null }) => ({
id,
title,
url: toStorefrontUrl(url, internalHosts),
});
return menu.items.map((item) => ({
...link(item),
items: item.items.map((child) => ({
...link(child),
items: child.items.map((leaf) => ({ ...link(leaf), items: [] })),
})),
}));
}If you add fields, validate the document with the Shopify AI Toolkit first.
2. Cache the menu
Create lib/menu/server.ts:
import { cacheLife, cacheTag } from "next/cache";
import type { CommerceLocale } from "@/lib/config/types";
import type { MenuItem } from "@/lib/menu/types";
import { fetchMenu } from "@/lib/shopify/operations/menu/server";
export async function getMenu(params: {
handle: string;
locale?: CommerceLocale;
}): Promise<MenuItem[] | null> {
"use cache: remote";
cacheLife("max");
cacheTag("menus");
return fetchMenu(params);
}3. Refresh menus after edits
The storefront's app/api/revalidate/route.ts refreshes the cache tags it is given, including menus, and returns 404 until REVALIDATE_SECRET is set. If the storefront has no app/api/revalidate/route.ts, take it from the template with the update-shop skill first; do not add a menu-only endpoint.
Tell the user to set REVALIDATE_SECRET in the deployment's environment variables, then refresh menus after editing them in Shopify admin:
curl -X POST "https://your-store.example.com/api/revalidate?tag=menus" \
-H "Authorization: Bearer $REVALIDATE_SECRET"Any scheduler or automation that can send that request can refresh menus on a schedule.
4. Wire the nav menu
Skip this section if the user did not select the nav menu.
Edit components/nav/index.tsx. Make Nav async (preserving any existing props in a customized storefront), import getMenu, and let the Shopify menu take precedence over the inline default:
import { getMenu } from "@/lib/menu/server";const items: MenuItem[] = (await getMenu({ handle: "NAV_HANDLE" }).catch(() => null)) ?? [
{ id: "default-nav-shop", items: [], title: "Shop", url: "/collections/all" },
];Replace "NAV_HANDLE" with the handle the user provided. QuickLinks and MobileMenu need no changes.
5. Wire the footer menu
Skip this section if the user did not select the footer menu.
Edit components/footer/index.tsx. Import getMenu and replace const items: MenuItem[] = []; with:
const items: MenuItem[] = (await getMenu({ handle: "FOOTER_HANDLE" }).catch(() => null)) ?? [];Replace "FOOTER_HANDLE" with the handle the user provided. FooterMenu needs no changes; an empty or missing menu hides the columns.
Verification
- The nav and footer render the Shopify menu items, with internal links as storefront paths such as
/collections/all, and external links unchanged. - A missing or empty menu falls back to the inline items.
POST /api/revalidate?tag=menusreturns404withoutREVALIDATE_SECRET,401with a wrong token, and200with{"revalidated":["menus"]}with the right one.- Lint, typecheck, and build pass.
Guardrails
- Keep the inline fallbacks so a missing menu or Storefront error never leaves a blank nav.
- Keep
cacheLife("max")with themenustag and refresh throughPOST /api/revalidate; do not shorten the cache life to pick up edits. - In a localized or Markets-enabled store, pass the validated commerce locale to
getMenufrom each caller; do not read locale from request headers inside the cached read. - New fallback labels belong beside the consuming component; Shopify menu translations and storefront fallback copy are separate.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

