shopify-graphql-reference
Integrate Shopify-validated Storefront or Customer Account GraphQL into Vercel Shop. Use after Shopify AI Toolkit has supplied and validated an API operation, or when adapting existing GraphQL to the template's operation placement, fragments, domain transforms, locale flow, cache role, invalidation, and route architecture.
Works with
--- name: shopify-graphql-reference description: Integrate Shopify-validated Storefront or Customer Account GraphQL into Vercel Shop. Use after Shopify AI Toolkit has supplied and validated an API operation, or when adapting existing GraphQL to the template's operation placement, fragments, domain transforms, locale flow, cache role, invalidation, and route architecture. license: MIT --- # Integrate Shopify GraphQL Treat Shopify AI Toolkit as authoritative for Shopify documentation, schemas, fields, arguments, enum values, API versions, operation design, and validation. This skill owns only the Vercel Shop integration layer. Read `references/REFERENCE.md` before editing. ## Delegate Shopify facts first 1. Choose the Shopify API: - Use Shopify AI Toolkit's Storefront GraphQL skill for catalog, search, menus, cart, and public metaobject reads. - Use its Customer skill for profiles, orders, addresses, and other authenticated customer data. - Use its custom-data skill first for metafields or metaobjects. 2. Search current Shopify documentation and validate the complete operation with that skill. 3. Do not copy schema snapshots, field catalogs, or generated API reference into this plugin. 4. If Shopify AI Toolkit is unavailable, use official Shopify documentation and validation tooling; do not guess. ## Apply the Vercel Shop conventions 1. Inspect the consuming route before choosing cache behavior. Classify the read as static-shell content, request-time shared content, or private/request-scoped data. 2. Add the operation to the closest file in `lib/shopify/operations/`; create a file only for a genuinely new domain. 3. Keep `#graphql` documents static, end them with `as const`, and use variables for dynamic values so codegen can validate them. 4. Reuse the smallest existing fragment that fits. Extend a shared fragment only when multiple operations need the same selection. 5. Pass locale context through existing country and language helpers when Shopify localizes the result. 6. Keep raw Shopify response types under `lib/shopify/**`; transform them into provider-independent domain types before presentation. 7. Preserve cache tags and the existing webhook invalidation hierarchy. Do not cache mutations. 8. Never place carts in the Next.js data cache; cart reads are memoized per request via `getCart`, so cart mutations need no cache invalidation step. ## Revalidate both boundaries 1. Validate the final GraphQL document again with Shopify AI Toolkit after fragment and variable changes. 2. Run `pnpm --filter template codegen` and the local lint, typecheck, build, and affected commerce flows. 3. Report separately: - Shopify validation performed; - Vercel Shop cache and route role; - domain transform and invalidation changes. Do not present this skill as a Shopify schema source. Shopify AI Toolkit determines what Shopify supports; this skill determines how validated operations fit Vercel Shop.
More API Design skills
lark-event
larksuite/cli
Lark/Feishu real-time event listening / subscribing / consuming: stream events as NDJSON via `lark-cli event consume <EventKey>` (covers IM messages/reactions/chat changes, Approval status changes, Task updates, VC meeting started/joined/ended, Minutes generated, Whiteboard updated, etc.). Use for Lark bots, real-time message processing, long-running subscribers, streaming webhook/push handlers. Supports `--max-events` / `--timeout` bounded runs and a stderr ready-marker contract — designed for AI agents running as subprocesses.
lark-contact
larksuite/cli
飞书 / Lark 通讯录:按姓名 / 邮箱解析成 open_id,或按 open_id 反查姓名 / 部门 / 邮箱 / 联系方式 / 个人状态 / 签名,以及按关键词搜索当前用户可见的机器人 / 智能体(agent)。当用户提到一个名字要下一步发消息 / 排日程,或拿到 open_id 想查具体信息时使用。不负责部门树遍历、按部门列员工、组织架构图,这类需求走原生 OpenAPI。
lark-openapi-explorer
larksuite/cli
飞书/Lark 原生 OpenAPI 探索:从官方文档库中挖掘未经 CLI 封装的原生 OpenAPI 接口。当用户的需求无法被现有 lark-* skill 或 lark-cli 已注册命令满足,需要查找并调用原生飞书 OpenAPI 时使用。

