القائمة
Use when the platform is Shopify or the run needs the Shopify-specific schema, sync, install, or verification branch.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when you need GA4 + GTM tracking delivery from site discovery through publish, or when the right phase entry point is still unclear.
Use when the user wants crawl coverage, platform detection, dataLayer discovery, or a fresh artifact directory before grouping and schema work.
Use when the user wants schema preparation, event design, selector validation, schema review, or event-spec generation.
Use when the user wants GTM-ready config generation, GTM workspace sync, or container selection from an approved schema.
Use when the user wants preview QA, failure interpretation, release readiness, or an explicit publish handoff.
Use when the user wants to inspect the real live GTM runtime before schema generation or compare multiple live GTM containers.
| name | tracking-shopify |
| description | Use when the platform is Shopify or the run needs the Shopify-specific schema, sync, install, or verification branch. |
Use this skill as the Shopify-specific branch contract after platform detection.
Use this skill when:
site-analysis.json reports platform.type: "shopify"Shopify still uses the same early workflow as generic sites:
Use tracking-discover and tracking-group for those phases.
Schema phase:
prepare-schemashopify-schema-template.jsonshopify-bootstrap-review.mdtriggerType: "custom"Sync phase:
sync also generates shopify-custom-pixel.jssync also generates shopify-install.mdVerification phase:
Expect some or all of:
<artifact-dir>/shopify-schema-template.json<artifact-dir>/shopify-bootstrap-review.md<artifact-dir>/shopify-custom-pixel.js<artifact-dir>/shopify-install.md<artifact-dir>/workflow-state.jsonStop after the Shopify-specific artifact or manual verification plan the user asked for.
Do not force the generic preview path on a Shopify run.