ericrisco/rsc-harness / skills/shopify
shopify
VerifiedUse when building or customizing a Shopify store across its three code surfaces — themes (Liquid, Online Store 2.0 sections, blocks and JSON templates), apps (Remix with the versioned GraphQL Admin API and its query-cost model), and checkout (UI extensions, Functions, Web Pixels), plus the CLI flow and checkout-extensibility migration. NOT WooCommerce or PHP stores (that is `wordpress`), NOT the React layer of a headless storefront (that is `nextjs`), NOT non-Shopify payment integrations (that is `stripe`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.4 KB |
| evals/README.md | markdown | 1.0 KB |
| evals/cases.yaml | config | 2.8 KB |
| references/apps-graphql.md | markdown | 3.5 KB |
| references/checkout-extensibility.md | markdown | 3.8 KB |
| references/liquid-themes.md | markdown | 3.8 KB |
| scripts/verify.shexecutable | script | 5.0 KB |
evals/README.md
View on GitHub# Evals — shopify
Run these against the repo's eval harness pointed at the `shopify` skill id. The
`should_trigger` cases mirror the `description` triggers across all three surfaces (theme, app,
checkout) and include the non-obvious ones — the "broke after the August upgrade" checkout-
migration framing, the `MAX_COST_EXCEEDED` query-cost framing, and the Catalan phrasing — to
confirm the skill fires when the surface is implicit. The `should_not_trigger` cases each route to
a real sibling (`wordpress`, `stripe`, `nextjs`, `no-code-app`, `api-design`) and exist to catch
surface confusion: WooCommerce/PHP, non-Shopify payments, the headless React layer, no-code
builders, and generic API-contract design must *not* pull in Shopify. The single `capability` case
is graded against its `must_include` rubric — a correct answer scaffolds an OS 2.0 section
(`render` not `include`, a `presets` + `@app` block schema) plus a Remix loader on a pinned
`apiVersion` with `admin.graphql()` and cost/throttle awareness, and never reaches for
`checkout.liquid`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |