shopify-app-development
Skill1 starsChanged 18 days agoMITView on GitHub
Build a Shopify app with the configured Admin API version, session-token auth for embedded admin requests, and HMAC-verified webhooks. Use when creating or changing a Shopify app, Admin GraphQL call, app proxy, or Shopify webhook handler.
In this repository28 other files it gives its agents.
- b2b-pricingSkill
- catalog-import-and-migrationSkill
- checkout-ux-and-conversionSkill
- conversion-event-trackingSkill
- ecommerce-seo-structured-dataSkill
- fraud-and-risk-basicsSkill
- google-merchant-product-feedsSkill
- headless-nextjs-storefrontSkill
- inventory-and-multi-warehouseSkill
- iranian-payment-gatewaysSkill
- marketplace-search-and-rankingSkill
- mcp-store-toolingSkill
- multi-vendor-payoutsSkill
- order-and-webhook-reliabilitySkill
- payment-gateway-integrationSkill
- product-catalog-modelingSkill
- product-description-guardrailsSkill
- returns-and-refundsSkill
- rtl-and-persian-localizationSkill
- storefront-accessibilitySkill
- storefront-performanceSkill
- stripe-paymentsSkill
- subscription-billingSkill
- tax-and-shippingSkill
- vector-product-searchSkill
- woocommerce-plugin-developmentSkill
- woocommerce-rest-apiSkill
- wordpress-plugin-securitySkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 6 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
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 12
Use this skill for a Shopify app.
- Very specific: line 18
Keep app configuration in shopify.app.toml, including the API version and app-specific webhook subscriptions.
- Distinctive: line 20
Call the GraphQL Admin API for new admin work.
- Distinctive: line 21
Ask for the narrowest access scopes the mutation needs.
- Very specific: line 22
Verify HTTPS webhooks with the app client secret over the raw body, then dedupe on X-Shopify-Webhook-Id.
- Distinctive: line 46
After the app client secret rotates, Shopify can keep signing with the previous secret for up to an hour.
- Very specific: line 53
Treat Admin GraphQL user errors and top-level errors as separate.
- Distinctive: line 54
Write webhooks and billing changes so a second delivery does not create a second subscription or a second charge.
- Distinctive: line 55
Do not log the access token, the client secret, or the raw HMAC.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Shopify app development
Use this skill for a Shopify app. Payment capture inside a shop you own is the payment skill. Webhook durability is the order and webhook skill. Storefront browsing without an admin token is the headless storefront skill.
Shopify's developer docs are the source for request authentication and webhook delivery. Re-check them when an API version or header name is load-bearing. This skill records the contracts those docs describe.
Procedure
- Keep app configuration in
shopify.app.toml, including the API version and app-specific webhook subscriptions. Do not hard-code an API version in a handler. TheX-Shopify-API-Versionheader says which version serialized that delivery, and the app configuration selects it. - Authenticate every request before using a shop domain from the query, body, or header.
- Call the GraphQL Admin API for new admin work. Do not start a new REST Admin API client.
- Ask for the narrowest access scopes the mutation needs.
- Verify HTTPS webhooks with the app client secret over the raw body, then dedupe on
X-Shopify-Webhook-Id.
Header and auth details are in the webhook and auth notes. Worked examples and checks are in evals/tasks.json.
Which credential
| Request | Proof |
| Embedded app in the Shopify admin | Session token (ID token) validated for signature, expiry, audience, and destination. |
| HTTPS webhook | HMAC-SHA256 of the raw body, Base64, in X-Shopify-Hmac-Sha256, keyed with the app client secret. Compare header names case-insensitively. |
| App proxy from a storefront | App proxy signature. It proves the shop, not the person. Do not change shop settings from an app proxy route. |
| Checkout or customer-account UI extension | That extension's session token. |
| Browser call that skips the app proxy | Anonymous. It may read public data. It must not mutate the shop. |
Reject a request that fails its check. Do not fall back to a shop parameter.
Webhooks
Compute Base64 HMAC-SHA256 over the raw body with the client secret. If a JSON parser runs first, the signature will not match. Return 401 when the signature does not match.
X-Shopify-Webhook-Id identifies one delivery. Store it and skip a repeat. X-Shopify-Event-Id is shared by deliveries from the same merchant action and is not a substitute for the delivery id when you are deduping retries of one POST.
Topic and shop-domain headers are untrusted until the HMAC matches. App-specific subscriptions in shopify.app.toml are kept in sync by Shopify. Use webhookSubscriptionCreate when the subscription has to be shop-specific. You cannot set the webhook API version on that mutation; it follows the app's webhook API version.
After the app client secret rotates, Shopify can keep signing with the previous secret for up to an hour. Accept that window only if you still have the previous secret stored for verification.
Google Cloud Pub/Sub and Amazon EventBridge deliveries do not use this HMAC header. Do not pretend an HTTPS verifier applies to those transports.
Admin writes
- Send the shop domain you got from the verified token, not from a form field.
- Treat Admin GraphQL user errors and top-level errors as separate. A 200 response can still contain
userErrors. - Write webhooks and billing changes so a second delivery does not create a second subscription or a second charge.
- Do not log the access token, the client secret, or the raw HMAC.
Gotchas
express.json()before verification replaces the raw body. Capture the bytes first.- A shop domain check must be anchored.
example.myshopify.com.attacker.exampleis not a shop domain. - OAuth
statehas to be bound to the browser that started the install and checked on return. - Scopes are not implied by installation. A missing scope is a failed call, not a reason to use a broader token you stored earlier.
Verification
- A webhook with a changed byte returns 401 and writes nothing.
- The same
X-Shopify-Webhook-Idapplied twice creates one record. - An embedded request with no valid session token does not run a mutation.
- An app proxy request cannot change shop settings.
Evaluation
Worked examples and the checks they must satisfy are in evals/tasks.json.
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.

