Skip to content

shopify-apps

Expert patterns for Shopify app development including Remix/React Router apps, embedded apps with App Bridge, webhook handling, GraphQL Admin API, Polaris components, billing, and app extensions.

1,018
installs
0 up / 0 down, score 0.00
votes
48,712
repo stars
Updated
less than a month ago
In the catalog since
6 Oct 2026
From
sickn33/agentic-awesome-skills
Get it through your agent npx skills add sickn33/agentic-awesome-skills@shopify-apps

Skill instructions

Rendered from the published SKILL.md, 29 lines.

Shopify Apps

Expert patterns for Shopify app development including Remix/React Router apps, embedded apps with App Bridge, webhook handling, GraphQL Admin API, Polaris components, billing, and app extensions.

Integration limits

Use the authorized development store/app, minimum scopes and protected-customer-data approvals; accessScopes does not prove protected-data approval. These legacy Remix/2024 API snippets are incomplete and require current generated SDK/template/schema validation. Test billing with explicit test mode and require merchant approval; production deploy/config/scopes/subscriptions and notification sends need task authority. Never log access tokens or customer payloads. Store tenant identity from verified sessions/webhooks and enforce it for every resource operation. No app/runtime was executed in this review.

Detailed Guide

Read the detailed guide before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end-to-end work, read the guide completely.

When to Use

  • User mentions or implies: shopify app
  • User mentions or implies: shopify
  • User mentions or implies: embedded app
  • User mentions or implies: polaris
  • User mentions or implies: app bridge
  • User mentions or implies: shopify webhook

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.