In short:
ak-shopifybuilds Shopify apps, extensions and themes, calls the GraphQL Admin API, receives webhooks and handles app billing. It identifies the kind of work, reads the installed CLI and configured API version, opens only the docs for that kind, then tests on a dev store or preview theme. It does not push to a live store until you name the store and theme and allow it, and it hands off to no other skill.
Disclosure: I maintain AgentKit and have an affiliate relationship with it: the AgentKit link in this post is an affiliate link; buying through it gets you 30% off.
Summary
Use it when you need a checkout extension, a theme change, an order webhook, a subscription plan for an app, or bulk data sync through the Admin API. If you only change the storefront's look, say it is a theme: the skill edits Liquid and does not build a new app.
flowchart LR
A["Shopify work: app, extension, theme, API"] --> B["ak-shopify"]
B --> C["Code running on a dev store or preview theme"]
C --> D["Stop, no handoff to another skill"]It rests on 4 ideas:
| Idea | Question | Example |
|---|---|---|
| Kind of work | Is this an app, an extension or a theme? | A "Gift message" field at checkout is an extension; changing the product page layout is a theme |
| Version in use | Which CLI version and API version does the project use? | If the project says api_version = "2025-10", queries and extensions are written for that version |
| Safety rails | What must never be loosened, even if the code runs? | Minimal scopes, HMAC-checked webhooks, the server holds payment state, safe reprocessing |
| Preview is not live | After testing, is it on the real store? | shopify theme dev is only a preview; going live needs the right store, theme and your permission |
The Shopify API ships a new version every quarter and supports each for 12 months, so recipes in the skill's docs may be older than your project. The skill checks against the real version and the official docs.
Sample prompt for a checkout extension:
/ak-shopify checkout Add a "Gift message" field to the checkout of the <app name> app.
Constraints: use the API version configured in the project, do not request extra scopes.
Done when: the field shows at checkout on the <dev store name> dev store and the message is saved to the order.This skill has no flags. After the skill name you can write the extension type and then the feature, for example checkout gift message. Both parts are optional.
Below is the detailed version: the run flow, 5 situations with prompts, how to write the input, the change history by ak release, and common pitfalls. The detailed version and the interactive page are for subscribers. Your agent can also search them through the portal's MCP.
Opens when your account has subscriber access
This guide is for subscribers
Once your account has access, the full piece, the interactive visual and the agent call all open.
- Sign in or create a modernEngineer accountReading access belongs to your account email.
- Choose a plan on the pricing page1, 3 or 12 months, paid by VietQR bank transfer. Access opens about a minute after the money arrives.
- Or redeem a Facebook subscriber codePeople supporting the page on Facebook get an activation code by message each month.
Already a subscriber? Sign in to read.
Use this piece in your agent
Get an API keyCopy the text below and paste it into Claude Code, Codex or whichever agent you use. The agent reads the piece and checks it against the repo you have open.
Read "ak-shopify: build Shopify apps, extensions and themes for your versions" on modernEngineer and apply it to this repo.
1. Call the content_get tool of the modernengineer MCP server with locale "en", slug "ak-shopify". If the modernengineer MCP server is not connected, stop and walk me through connecting it from https://modernengineer.dev/en/mcp.
2. Summarize the main steps of the piece and point out which apply to this repo.
3. Propose concrete changes and ask me before editing any file.Connect MCP in Claude Code (once)
claude mcp add --transport http modernengineer \
https://api.modernengineer.dev/mcp \
--header "Authorization: Bearer <API key>"Reading the full piece over MCP needs an API key from a subscriber account or one that bought this guide. Without access, the agent only gets the opening.
- Version
- v1.0.0
- Updated
- 22/10/2026
- Licence
- All rights reserved
- Slug
- ak-shopify
