shop-preflightlisted

Forge⇄Epodsystem integration guide — the thin Forge-owned layer that sits ON TOP of Epodsystem's live single-source playbooks. Defers build mechanics to the live shop-core-rules, holds Forge's durable invariants (build-on-draft, backup-before-publish, verify-via-live-URL), and records how Forge routes around current service quirks so a quirk degrades instead of hard-failing. Referenced by shop-customize-draft, shop-products, shop-menus, shop-verify-draft, shop-publish, shop-rollback. Triggers on: any Epodsystem theme/store mutation, 'customize storefront', 'edit theme', 'add products', 'change menu'.
SidCorp-co/forge · ★ 4 · AI & Automation · score 70

Install: claude install-skill SidCorp-co/forge

# Forge ⇄ Epodsystem integration guide Forge's **thin guide layer** over Epodsystem. It exists so Forge can run Epod storefronts through the pipeline reliably AND proactively improve the way the user works — without forking Epodsystem's docs. Read this before any `shop-*` stage. It has three parts: what to defer, what Forge guarantees, how Forge handles current quirks. First resolve context with `forge_storefront_target` → `storeSlug`, `storeName`, `themeId` (live/main), `draftThemeId` (draft/staging), `commerceEnabled`, `endpoint`. The `crmk_` key is never exposed — it is injected into the `mcp__epodsystem__*` tools automatically. ## §1 — Single source of truth = the LIVE Epodsystem playbooks (do NOT duplicate) All build/redesign mechanics (palette tokens, the design contract, render rules, how to bind live data, image re-hosting) live in Epodsystem's own `shop-core-rules` — it is the maintained single source. **Load it live at runtime** with `get_skill shop-core-rules` (and the focused playbook for the task: `shop-redesign`, `shop-build-section`, `shop-create-product`, …) via the `mcp__epodsystem__*` server. Do not copy its steps into Forge — when Epodsystem updates, the live skill updates and Forge tracks it automatically. ## §2 — Forge durable invariants (Forge owns these; independent of the service) These hold no matter how Epodsystem implements themes — they never rot: 1. **Build on the DRAFT theme** (`draftThemeId`), never on main. Main is touched only by `shop-