init-vercel-shop
Skill137 starsChanged 21 days agoMITView on GitHub
Initialize a new Vercel Shop storefront from the vercel/shop template with create-next-app. Use when the user wants to create, scaffold, start, or initialize a Vercel Shop project from a coding agent.
- Installs packages
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- build-shopSkill
- enable-analyticsSkill
- enable-i18nSkill
- enable-shopify-marketsSkill
- enable-shopify-menusSkill
- shopify-graphql-referenceSkill
- update-shopSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Ask for the target directory if the user did not provide one.
- Distinctive: line 20
Read the generated AGENTS.md before making further changes.
- Distinctive: line 21
If dependency installation fails, keep the generated project and show the retry command to run from its root:
- Distinctive: line 27
Ask one optional follow-up: Connect an existing Shopify store now?
- Very specific: line 29
If yes, ask only for the store's admin URL or .myshopify.com domain, then read references/storefront-token.md and follow its automated …
- Distinctive: line 31
If no, finish with the normal environment setup as the next step.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Initialize Vercel Shop
Ask for the target directory if the user did not provide one. Always pass it explicitly.
- Inspect the target. If it already contains a Vercel Shop project, stop and use the relevant storefront skill instead. If it is a non-empty directory, ask for a different target rather than overwriting files.
Run:
pnpm create next-app@latest <target-directory> --example https://github.com/vercel/shopThe template pins pnpm 12 and Node.js 26.
- Confirm the generated project contains
AGENTS.md,.agents/skills/,app/,components/,lib/shopify/, andpackage.json. - Read the generated
AGENTS.mdbefore making further changes. If dependency installation fails, keep the generated project and show the retry command to run from its root:
pnpm installAsk one optional follow-up: Connect an existing Shopify store now?
If yes, ask only for the store's admin URL or
.myshopify.comdomain, then read references/storefront-token.md and follow its automated Shopify CLI flow. Try to reuse or create a public Storefront token before asking the user to visit the Headless channel.If no, finish with the normal environment setup as the next step.
Return the generated project path, whether a Shopify store was connected, and whether dependency installation needs a retry.
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.

