mock-shop-starter / rules
Cursor rule1 starsChanged 2 months agoMITView on GitHub
mock.shop is the default development backend for this storefront
- Reads credentials
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,157 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/hydrogen-react-router.mdcCursor rule
- llms.txtllms.txt
The file
We split this mock-shop.mdc into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Do not invent product data or stub the Storefront API locally.
≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule 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
--- description: mock.shop is the default development backend for this storefront globs: alwaysApply: true --- # mock.shop is the default development backend This storefront reads mock.shop, Shopify's public, auth-free Storefront API, until a real store is linked. - Do not invent product data or stub the Storefront API locally. Query mock.shop; the schema is the real Storefront API schema. - mock.shop is a catalog of 100+ fictional stores, each on its own host. The directory is https://mock.shop/llms.txt. The default store at `mock.shop` sells apparel basics. - To use a different store, set `PUBLIC_STORE_DOMAIN` in `.env` to that store's host, for example `candles.mock.shop`, and leave `PUBLIC_STOREFRONT_API_TOKEN` empty. Read `https://<store>.mock.shop/llms.txt` for that store's categories, collections, and product counts. - Raw queries go to `POST https://<store>.mock.shop/api` with a JSON body and `Content-Type: application/json`. No token, no other headers. - Carts work. Checkout is mocked (no payment, no real order). The Customer Account API is not available on mock.shop; do not try to make it work against it. - Moving to a real store is `npx shopify hydrogen link` followed by `npx shopify hydrogen env pull`. Nothing in the code changes.
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.