@salesforce/b2c-dx-mcp 2.1.2 → 3.0.0

package/content/guidance/index.json

@@ -0,0 +1,1427 @@
+{
+  "version": 1,
+  "collections": [
+    {
+      "id": "b2c-cli",
+      "title": "B2C CLI Workflows",
+      "isGA": true
+    },
+    {
+      "id": "b2c",
+      "title": "B2C Commerce Development",
+      "isGA": true,
+      "workspaces": [
+        "cartridges",
+        "sfra"
+      ]
+    },
+    {
+      "id": "b2c-ops",
+      "title": "B2C Operations Runbooks",
+      "isGA": true
+    },
+    {
+      "id": "storefront-next",
+      "title": "Storefront Next",
+      "isGA": true,
+      "workspaces": [
+        "storefront-next"
+      ]
+    },
+    {
+      "id": "mcp",
+      "title": "MCP Workflows",
+      "isGA": true
+    }
+  ],
+  "entries": [
+    {
+      "id": "b2c-cli/b2c-am",
+      "collection": "b2c-cli",
+      "title": "b2c-am",
+      "description": "Manage Account Manager resources including API clients, users, roles, and organizations. Use this skill whenever the user needs to create or update API clients, onboard or offboard developers, assign Account Manager roles scoped to tenants, audit user permissions, look up organizations, or provision API clients for CI/CD pipelines. Also use when managing AM role assignments or querying Account Manager data — even if they just say \"add a new developer\" or \"set up an API client\". For instance-level Business Manager administration (BM roles, BM users, BM access keys, BM whoami), defer to the `b2c-cli:b2c-bm-users-roles` skill.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c-cli/skills/b2c-am/SKILL.md",
+      "headings": "B2C Account Manager Skill | Authentication | Role Requirements | API Clients | List Clients | Get Client | Create Client | Update Client | Change Client Password | Delete Client | Users | List Users | Get User | Create User | Update User | Delete User | Reset User Password | Roles | List Roles | Get Role | Grant Role to User | Revoke Role from User | Organizations | List Organizations | Get Organization | Business Manager Administration | Common Workflows | User Onboarding | User Offboarding | Bulk Operations with JSON | Common Patterns | More Commands",
+      "files": [
+        {
+          "path": "SKILL.md",
+          "bytes": 7983
+        }
+      ]
+    },
+    {
+      "id": "b2c-cli/b2c-bm-users-roles",
+      "collection": "b2c-cli",
+      "title": "b2c-bm-users-roles",
+      "description": "Manage Business Manager users, access roles, role permissions, and per-user access keys on a B2C Commerce instance using the b2c CLI. Use this skill whenever the user needs to list or search BM users on a sandbox or production instance, identify which BM user an OAuth token resolves to (\"whoami\"), assign or revoke instance-level access roles, edit role permissions, look up a user's WebDAV / OCAPI / Storefront access key, or rotate access keys for SSO-managed users. Also use when the user asks \"what's my BM login on sandbox X\", \"rotate my WebDAV password\", \"how do I make a custom BM role\", \"audit BM users on this instance\", or \"delete a stale BM user from a sandbox\".",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c-cli/skills/b2c-bm-users-roles/SKILL.md",
+      "headings": "B2C Business Manager Users, Roles, and Access Keys | API Backend | Authentication | Business Manager Roles | Role Permissions | Business Manager Users | Whoami — Identify the Current BM User | Access Keys (WebDAV, OCAPI, Storefront) | Common Workflows | Rotate my own WebDAV password (no admin privileges needed) | Audit users with admin role and stale logins | Provision a new custom role and assign one user | Cycle access keys for an SSO user (admin) | Common Patterns | More",
+      "files": [
+        {
+          "path": "SKILL.md",
+          "bytes": 12187
+        }
+      ]
+    },
+    {
+      "id": "b2c-cli/b2c-cap",
+      "collection": "b2c-cli",
+      "title": "b2c-cap",
+      "description": "Manage Commerce App Packages (CAPs), also called commerce apps or apps, and commerce features using the b2c CLI. Use this skill whenever the user needs to validate, package, install, uninstall, list, or pull commerce apps on B2C Commerce instances, view configuration tasks, or pull app sources for cartridge deployment or Storefront Next development. Also use when checking which apps are installed on an instance, inspecting app details or versions, or managing app lifecycle — even if they just say \"what apps do I have\", \"list my commerce apps\", \"which CAPs are installed\", \"install this app\", \"pull app sources\", or \"show installed apps\".",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c-cli/skills/b2c-cap/SKILL.md",
+      "headings": "B2C CAP Skill | Configuration & Authentication | Examples | List Installed Features | Pull App Sources | View Configuration Tasks | Validate a CAP | Package a CAP | Install a CAP | Uninstall a CAP | More Commands | Related Skills",
+      "files": [
+        {
+          "path": "SKILL.md",
+          "bytes": 6330
+        }
+      ]
+    },
+    {
+      "id": "b2c-cli/b2c-cip",
+      "collection": "b2c-cli",
+      "title": "b2c-cip",
+      "description": "Query CIP/CCAC sales, merchandising, payment, traffic, and API/controller analytics with the B2C CLI or MCP. Discover reports/tables, scope SQL, export results, and resolve analytics access.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c-cli/skills/b2c-cip/SKILL.md",
+      "headings": "Known CIP Tables | Aggregate Tables (`ccdw_aggr_*`) | Dimension Tables (`ccdw_dim_*`) | Fact Tables (`ccdw_fact_*`) | Practical Starters | Notes | Sales comparisons and coverage | Compare periods | Coverage check | Definitions | CIP Starter Queries | 1) Recent Daily Sales Snapshot | 2) Sales by Site (Joined) | 3) Top-Selling Products by Revenue | 4) Promotion Impact Summary | 5) OCAPI Request Volume | 6) SCAPI Request Volume | 7) Top Search Terms by Revenue | 8) Referrer Mix | 9) Customer Registration Trend | 10) Payment Method Performance | CIP analytics | Choose the surface | Configuration and access | Discover and execute | Select technical reports | Query and interpret | Conditional references",
+      "files": [
+        {
+          "path": "references/KNOWN_TABLES.md",
+          "bytes": 9466
+        },
+        {
+          "path": "references/SALES_ANALYSIS.md",
+          "bytes": 2642
+        },
+        {
+          "path": "references/STARTER_QUERIES.md",
+          "bytes": 4956
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 5926
+        }
+      ]
+    },
+    {
+      "id": "b2c-cli/b2c-code",
+      "collection": "b2c-cli",
+      "title": "b2c-code",
+      "description": "Deploy, download, and manage cartridge code versions on B2C Commerce instances. Use this skill whenever the user needs to upload or download cartridges to/from a sandbox, activate or delete code versions, watch for local file changes during development, or deploy a subset of cartridges. Also use when pushing code to an instance, pulling code from an instance, or setting up a dev workflow with live reload -- even if they just say 'push my code to the sandbox', 'download the code', or 'how do I activate the new version'.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c-cli/skills/b2c-code/SKILL.md",
+      "headings": "B2C Code Skill | MCP equivalent | Configuration & Authentication | Examples | Deploy Cartridges | Download Cartridges | Watch for Changes | List Code Versions | Activate Code Version | Delete Code Version | API Backend | More Commands | Related Skills",
+      "files": [
+        {
+          "path": "SKILL.md",
+          "bytes": 6359
+        }
+      ]
+    },
+    {
+      "id": "b2c-cli/b2c-config",
+      "collection": "b2c-cli",
+      "title": "b2c-config",
+      "description": "Configure B2C CLI/MCP authentication, instances, and project defaults; troubleshoot missing credentials, wrong targets, or configuration precedence. Routine inspection can use config_inspect or b2c setup inspect directly.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c-cli/skills/b2c-config/SKILL.md",
+      "headings": "B2C Config Skill | How the CLI Discovers Configuration | Shared Global Default | MCP Project Context | `dw.json` Key Casing | Authentication | `--user-auth` Flag | Tenant ID and Organization ID | Inspecting Configuration | When to Use | View Current Configuration | Debug Sensitive Values | JSON Output for Scripting | IDE Integration | Managing Instances | List Configured Instances | Create a New Instance | Switch Active Instance | Remove an Instance | Understanding the Output | Configuration Priority | Project Defaults in package.json | Troubleshooting | Command says \"credentials required\" or \"client-id is required\" | Command targets the wrong instance | `dw.json` is not being picked up | 401/403 errors on SCAPI/OCAPI calls | Missing `tenantId` / `shortCode` | MRT commands say \"API key required\" | Sensitive values masked in `setup inspect` | Missing values | Wrong source taking precedence | Still stuck | Getting Admin OAuth Tokens | More Commands",
+      "files": [
+        {
+          "path": "SKILL.md",
+          "bytes": 22816
+        }
+      ]
+    },
+    {
+      "id": "b2c-cli/b2c-content",
+      "collection": "b2c-cli",
+      "title": "b2c-content",
+      "description": "Export, list, and validate Page Designer content from B2C Commerce libraries. Use this skill whenever the user needs to export Page Designer pages, components, or content blocks, list pages in a content library, validate page JSON or metadefinitions, discover page IDs, migrate content between instances, or work with library XML offline. Also use when extracting content for review or building content deployment pipelines -- even if they just say 'export the homepage' or 'what pages are in the shared library'.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c-cli/skills/b2c-content/SKILL.md",
+      "headings": "B2C Content Skill | Configuration & Authentication | Examples | Export Pages | Export Directly into an Import-Set Migration | List Content | Content Blocks | Configuration | Validate Metadefinitions | More Commands | Troubleshooting | Related Skills",
+      "files": [
+        {
+          "path": "SKILL.md",
+          "bytes": 7776
+        }
+      ]
+    },
+    {
+      "id": "b2c-cli/b2c-debug",
+      "collection": "b2c-cli",
+      "title": "b2c-debug",
+      "description": "Debug B2C Commerce server-side scripts using the b2c CLI. Use this skill whenever the user needs to set breakpoints, step through code, inspect variables, evaluate expressions, or investigate runtime behavior on a B2C Commerce instance. Also use when the user wants to understand what a script is doing at runtime, capture state at a specific line, or drive the debugger from a headless script — even if they just say \"debug this controller\" or \"what's the value of basket at line 42\".",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c-cli/skills/b2c-debug/SKILL.md",
+      "headings": "B2C Debug Skill | Configuration & Authentication | Prerequisites | Interactive Debugging | Start a Debug Session | Set Breakpoints | Inspect State When Halted | Control Execution | Thread Management | RPC Mode (Headless / Agent Use) | Send Commands | Receive Responses and Events | Available RPC Commands | DAP Mode (IDE Integration) | Related Skills",
+      "files": [
+        {
+          "path": "SKILL.md",
+          "bytes": 6601
+        }
+      ]
+    },
+    {
+      "id": "b2c-cli/b2c-docs",
+      "collection": "b2c-cli",
+      "title": "b2c-docs",
+      "description": "Search and read B2C Commerce documentation using the b2c CLI. Covers Script API reference (dw.* classes/modules), Developer Center guides (Commerce API, PWA Kit, SFRA, Storefront Next, B2C Commerce), Salesforce Help (Business Manager administration and merchandising), tooling documentation (CLI/MCP/SDK), standard job steps, and XSD schemas. Use this skill for ANY B2C Commerce developer or administrator question that is not already grounded in a loaded skill or the current project context — even if they just say \"how do I implement passwordless login\" or \"what methods does Basket have\" or \"how do I deploy a PWA Kit bundle\" or \"how do I import a site archive\" or \"what SCAPI endpoints are available for checkout\".",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c-cli/skills/b2c-docs/SKILL.md",
+      "headings": "B2C Docs Skill | Key Features | Examples | Search Documentation | Workspace-Aware Search | Read Documentation | Standard Job Step Catalog | Download Documentation | Read XSD Schemas | Documentation Categories | Common Script API Classes | Common Schemas | More Commands",
+      "files": [
+        {
+          "path": "SKILL.md",
+          "bytes": 17299
+        }
+      ]
+    },
+    {
+      "id": "b2c-cli/b2c-ecdn",
+      "collection": "b2c-cli",
+      "title": "b2c-ecdn",
+      "description": "Manage eCDN zones, security settings, and edge configuration for B2C Commerce storefronts. Use this skill whenever the user needs to purge CDN cache, provision SSL certificates, configure WAF or firewall rules, set up rate limiting, enable logpush or Page Shield, manage MRT routing, configure mTLS or cipher suites, or optimize edge performance. Also use when troubleshooting CDN-layer issues or managing zone settings -- even if they just say 'clear the cache' or 'block bot traffic on our storefront'.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c-cli/skills/b2c-ecdn/SKILL.md",
+      "headings": "eCDN Advanced Reference | Logpush | MRT Rules | mTLS Certificates | Cipher Suites | Origin Headers | eCDN Security Reference | WAF (Web Application Firewall) | Firewall Rules | Rate Limiting | Page Shield | B2C eCDN Skill | Configuration | Prerequisites | Examples | List CDN Zones | Create a Storefront Zone | Purge Cache | Manage Certificates | Manage Rate Limiting Rules | Security Settings | Speed Settings | Additional Topics | Configuration Overrides | OAuth Scopes | More Commands",
+      "files": [
+        {
+          "path": "references/ADVANCED.md",
+          "bytes": 2420
+        },
+        {
+          "path": "references/SECURITY.md",
+          "bytes": 2082
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 4881
+        }
+      ]
+    },
+    {
+      "id": "b2c-cli/b2c-import-set-migrations",
+      "collection": "b2c-cli",
+      "title": "b2c-import-set-migrations",
+      "description": "Create and apply ordered, idempotent B2C Commerce site import/export archives from discovered cartridge metadata and project migrations using `b2c job import-set`. Use this opt-in project workflow for migrations built from focused instance exports, repeatable setup, onboarding, and CI/CD imports that apply once per instance. Also covers source exclusions, post-import README notes, resetting history, and recovering an interrupted run.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c-cli/skills/b2c-import-set-migrations/SKILL.md",
+      "headings": "Import Set Migrations Skill | Configuration & Authentication | Import Sources and Order | Naming convention | Commands | Flags | Source exclusions | Post-Import Notes (per-archive README) | Repeat Runs | Set IDs (namespaces) | Concurrent Runs and Recovery | Idiomatic Workflows | Local setup / onboarding | CI/CD | Adding a new migration | Building a migration from an instance export | Resetting Import History | Import Failure Recovery | Related Skills",
+      "files": [
+        {
+          "path": "SKILL.md",
+          "bytes": 15678
+        }
+      ]
+    },
+    {
+      "id": "b2c-cli/b2c-job",
+      "collection": "b2c-cli",
+      "title": "b2c-job",
+      "description": "Run existing B2C Commerce jobs, monitor executions, inspect failures, rebuild search indexes, and import or export site archives with the CLI.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c-cli/skills/b2c-job/SKILL.md",
+      "headings": "Export Site Archives | Compact Results | Export Commands | Output Directory Semantics | Available Data Units | Import Site Archives | Import Site Archives | Import Sets | Run and Monitor Jobs | Run a Job | Run System Jobs with Custom Request Bodies | Standard (System) Job Steps | View Job Logs | Search Job Executions | Delete Job Executions | API Backend | Wait for Job Completion | Run and Monitor Jobs | Configuration and tool choice | Run and inspect | Site archives | Output",
+      "files": [
+        {
+          "path": "references/EXPORT.md",
+          "bytes": 5933
+        },
+        {
+          "path": "references/IMPORT.md",
+          "bytes": 2106
+        },
+        {
+          "path": "references/RUN-AND-MONITOR.md",
+          "bytes": 4748
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 2740
+        }
+      ]
+    },
+    {
+      "id": "b2c-cli/b2c-logs",
+      "collection": "b2c-cli",
+      "title": "b2c-logs",
+      "description": "Retrieve and search logs from B2C Commerce instances using the b2c CLI. Use this skill whenever the user needs to view server logs, search for errors, filter log entries by level or time, or monitor logs in real-time. Also use when the user reports a 500 error, broken checkout, failing job, or any server-side issue that needs log investigation — even if they just say \"something's broken on the sandbox\" or \"check the logs\".",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c-cli/skills/b2c-logs/SKILL.md",
+      "headings": "B2C Logs Skill | Configuration & Authentication | Agent-Friendly Log Retrieval | Examples | Get Recent Logs | Filter by Time | Filter by Log Level | Search Text | Combined Filters | List Available Log Files | Real-Time Tailing (Human Use) | Downloading Full Log Files | JSON Output Structure | Log Types | Discovering Custom Log Files | Logs in Subdirectories | More Commands | Related Skills",
+      "files": [
+        {
+          "path": "SKILL.md",
+          "bytes": 10026
+        }
+      ]
+    },
+    {
+      "id": "b2c-cli/b2c-metrics",
+      "collection": "b2c-cli",
+      "title": "b2c-metrics",
+      "description": "Query observability metrics from SCAPI Metrics API (CLOSED BETA). Use this skill whenever the user needs request volume, latency distributions, error rates, cache performance, or technical health indicators for SCAPI, OCAPI, MRT, SFRA controllers, or overall system performance. Also use when they want to monitor third-party integrations, sales metrics, or eCDN performance -- even if they just say 'show me SCAPI metrics', 'what is my error rate', or 'check API performance'.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c-cli/skills/b2c-metrics/SKILL.md",
+      "headings": "B2C Metrics Skill | Command Structure | Configuration | Requirements | Quick Workflow | Metric Categories and Commands | Discovery Examples | Fetch Metrics Examples | Time Windows | Series Tags | Response Format | SDK Usage | Troubleshooting",
+      "files": [
+        {
+          "path": "SKILL.md",
+          "bytes": 14630
+        }
+      ]
+    },
+    {
+      "id": "b2c-cli/b2c-mrt",
+      "collection": "b2c-cli",
+      "title": "b2c-mrt",
+      "description": "Deploy and manage Managed Runtime (MRT) storefronts using the b2c CLI. Use this skill whenever the user needs to deploy a PWA Kit bundle, manage MRT environments and projects, set environment variables, configure URL redirects, or manage organization connections — even if they just say \"deploy my PWA\" or \"set up a staging environment\".",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c-cli/skills/b2c-mrt/SKILL.md",
+      "headings": "MRT Bundle Commands Reference | Bundle Deploy | Push Local Build | Deploy Existing Bundle | Bundle Upload (v2) | Bundle List | Bundle History | Bundle Download | Common Workflows | Development to Production Pipeline | Rollback to Previous Bundle | Download and Inspect Bundle | MRT Environment Commands Reference | Environment Management | List Environments | Create Environment | Get Environment Details | Update Environment | Delete Environment | Invalidate Cache | B2C Commerce Connection | Environment Variables | List Variables | Set Variables | Delete Variable | URL Redirects | List Redirects | Create Redirect | Delete Redirect | Clone Redirects | Access Control Headers | List Access Control Headers | MRT Project Commands Reference | Project Management | List Projects | Create Project | Get Project Details | Update Project | Delete Project | Member Management | List Members | Add Member | Get Member Details | Update Member Role | Remove Member | Deployment Notifications | List Notifications | Create Notification | Get Notification Details | Update Notification | Delete Notification | B2C MRT Skill | Configuration & Authentication | MRT Backends (legacy vs SCAPI) | Command Structure | Quick Examples | Deploy a Bundle | Manage Environments | Environment Variables | View Deployment History | Organization Members and Certificates | Project Management | URL Redirects | Configuration | dw.json | Environment Variables | ~/.mobify Config | Detailed References | More Commands",
+      "files": [
+        {
+          "path": "references/BUNDLE-COMMANDS.md",
+          "bytes": 7241
+        },
+        {
+          "path": "references/ENVIRONMENT-COMMANDS.md",
+          "bytes": 5493
+        },
+        {
+          "path": "references/PROJECT-COMMANDS.md",
+          "bytes": 4923
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 7994
+        }
+      ]
+    },
+    {
+      "id": "b2c-cli/b2c-sandbox",
+      "collection": "b2c-cli",
+      "title": "b2c-sandbox",
+      "description": "Create and manage on-demand sandboxes (ODS) for B2C Commerce using the b2c CLI. Use this skill whenever the user needs to spin up a new development sandbox, list running sandboxes, start/stop/restart an instance, or manage sandbox lifecycle — even if they just say \"I need a sandbox\" or \"restart my instance\".",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c-cli/skills/b2c-sandbox/SKILL.md",
+      "headings": "B2C Sandbox Skill | Configuration & Authentication | Sandbox ID Formats | Examples | List Sandboxes | Create Sandbox | Get/Start/Stop/Restart/Delete Sandbox | Clone Sandbox | More Commands",
+      "files": [
+        {
+          "path": "SKILL.md",
+          "bytes": 4928
+        }
+      ]
+    },
+    {
+      "id": "b2c-cli/b2c-scapi-custom",
+      "collection": "b2c-cli",
+      "title": "b2c-scapi-custom",
+      "description": "Check custom SCAPI endpoint registration status using the b2c CLI. Use this skill whenever the user needs to verify that their custom API endpoints are registered and working, debug 404 or \"endpoint not found\" errors on custom APIs, or list custom API endpoints and their deployment status — even if they just say \"my custom API returns 404\" or \"is my endpoint deployed\".",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c-cli/skills/b2c-scapi-custom/SKILL.md",
+      "headings": "B2C SCAPI Custom APIs Skill | Configuration | Tenant ID vs. Organization ID | Deriving Tenant ID from Hostname | Examples | Get Custom API Endpoint Status | Filter by Status | Group by Type or Site | Customize Output Columns | Debug Failed Registrations | Configuration Overrides | More Commands | OAuth Scopes (manual token minting) | Related Skills",
+      "files": [
+        {
+          "path": "SKILL.md",
+          "bytes": 5316
+        }
+      ]
+    },
+    {
+      "id": "b2c-cli/b2c-scapi-schemas",
+      "collection": "b2c-cli",
+      "title": "b2c-scapi-schemas",
+      "description": "Browse and retrieve SCAPI OpenAPI schema specifications. Use this skill whenever the user needs to list available SCAPI APIs, inspect endpoint paths or request/response shapes, explore data models for products or orders, check which fields an API returns, or understand SCAPI versioning. Also use when looking up API details before building an integration -- even if they just say 'what fields does the product API return' or 'show me the SCAPI endpoints'.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c-cli/skills/b2c-scapi-schemas/SKILL.md",
+      "headings": "SCAPI Schema CLI Examples | List Available Schemas | Filter Schemas | Get Schema (Collapsed/Outline - Default) | Get Schema with Selective Expansion | Get Full Schema | List Available Paths/Schemas/Examples | Output Formats | Custom Properties | Configuration Overrides | More Commands | B2C SCAPI Schemas Skill | Tool choice | Configuration | Tenant ID vs. Organization ID | Deriving Tenant ID from Hostname",
+      "files": [
+        {
+          "path": "references/CLI-EXAMPLES.md",
+          "bytes": 2776
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 4103
+        }
+      ]
+    },
+    {
+      "id": "b2c-cli/b2c-site-import-export",
+      "collection": "b2c-cli",
+      "title": "b2c-site-import-export",
+      "description": "Author, validate, import, and verify B2C Commerce site archives and metadata XML; export selected data for inspection or migration.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c-cli/skills/b2c-site-import-export/SKILL.md",
+      "headings": "Import Options | Import Commands | Import Local Directory | Import Remote Archive | Apply an Ordered, Idempotent Import Set | Import Archives Larger Than the Instance Limit | Metadata XML Patterns | XSD Schema Reference | Other Import Formats | System Object Extensions | Add String Attribute to Product | Add Enum Attribute to Order | Add Boolean Attribute to Customer Profile | Site Preferences | Boolean Preference | String Preference (API Key) | Preference Values | Custom Object Types | Simple Custom Object | Custom Object Data | Content Assets | Attribute Types Reference | Complete Import Example | Archive Workflows | Common Workflows | Adding a Custom Attribute to Products | Adding Site Preferences | Creating a Custom Object Type | Importing Custom Object Data | Site Archive Structure | Site Archives | Configuration and tool choice | Import and verify | Focused references",
+      "files": [
+        {
+          "path": "references/IMPORT-OPTIONS.md",
+          "bytes": 6436
+        },
+        {
+          "path": "references/METADATA-XML.md",
+          "bytes": 14637
+        },
+        {
+          "path": "references/WORKFLOWS.md",
+          "bytes": 5589
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 2960
+        }
+      ]
+    },
+    {
+      "id": "b2c-cli/b2c-sites",
+      "collection": "b2c-cli",
+      "title": "b2c-sites",
+      "description": "List storefront sites, check site status, and manage cartridge paths on B2C Commerce instances using the b2c CLI. Use this skill whenever the user needs to discover site IDs, check which storefronts are online or offline, get site configuration as JSON, or view/modify the ordered cartridge path for a site or Business Manager. Also use when the user needs site information for scripting, CI/CD pipelines, or as input to other commands — even if they just say \"what sites do I have\" or \"add this cartridge to my site\".",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c-cli/skills/b2c-sites/SKILL.md",
+      "headings": "B2C Sites Skill | Configuration & Authentication | Commands | `b2c sites list` | Cartridge Path Management | Common Use Cases | Related Skills",
+      "files": [
+        {
+          "path": "SKILL.md",
+          "bytes": 5077
+        }
+      ]
+    },
+    {
+      "id": "b2c-cli/b2c-slas",
+      "collection": "b2c-cli",
+      "title": "b2c-slas",
+      "description": "Create, update, and manage SLAS (Shopper Login and API Access Service) clients using the b2c CLI. Use this skill whenever the user needs to provision a SLAS client, update OAuth scopes, rotate client secrets, get a shopper access token, or configure shopper authentication for headless, PWA, or Storefront Next (SFNext) storefronts — even if they just say \"I need a shopper token\" or \"set up auth for my storefront\".",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c-cli/skills/b2c-slas/SKILL.md",
+      "headings": "B2C SLAS Skill | Configuration | When to Use | Examples | List SLAS Clients | Get SLAS Client Details | Create SLAS Client | Create Client for Custom API Testing | Get a Shopper Token | Update SLAS Client | Delete SLAS Client | Open SLAS Client | More Commands | Related Skills",
+      "files": [
+        {
+          "path": "SKILL.md",
+          "bytes": 7437
+        }
+      ]
+    },
+    {
+      "id": "b2c-cli/b2c-webdav",
+      "collection": "b2c-cli",
+      "title": "b2c-webdav",
+      "description": "List, upload, download, and manage files on B2C Commerce instances via WebDAV. Use this skill whenever the user needs to upload files to IMPEX directories, download exports from an instance, list remote files, create or delete directories, zip or unzip files on the server, manage file transfers to sandboxes, or browse instance file systems — even if they just say \"upload a file to the instance\" or \"check what's in the IMPEX folder\".",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c-cli/skills/b2c-webdav/SKILL.md",
+      "headings": "B2C WebDAV Skill | MCP equivalent | Configuration & Authentication | WebDAV Roots | Examples | List Files | Download Files | Upload Files | Create Directories | Delete Files | Delete Cartridges | Zip/Unzip Remote Files | Import-Set Managed State | More Commands | Related Skills",
+      "files": [
+        {
+          "path": "SKILL.md",
+          "bytes": 6088
+        }
+      ]
+    },
+    {
+      "id": "b2c/b2c-business-manager-extensions",
+      "collection": "b2c",
+      "title": "b2c-business-manager-extensions",
+      "description": "Build Business Manager extension cartridges with custom admin tools, menu items, and dialog actions. Use this skill whenever the user needs to create bm_* cartridges, add menu actions or dialog buttons in BM, configure bm_extensions.xml, or extend admin pages with form overlays. Also use when customizing the BM interface for back-office workflows -- even if they just say 'add a button to BM' or 'custom admin page'.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c/skills/b2c-business-manager-extensions/SKILL.md",
+      "headings": "Business Manager Extensions XML Reference | XSD Schema Reference | File Location & Encoding | Root Element | Localized text: `LocalizedString` | Positioning | Menu Item Element | Attributes | Child Elements (in schema order) | Menu Action Element | Attributes | Child Elements | exec Element | sub-pipelines and the permission check | The `NoPermissionCheck` idiom | Dialog Action Element | Attributes | Child Elements | Common Extension Points (`xp_ref`) | Form Extension Element | formextension attributes | valueinput attributes | valueinput child elements | Complete Example | Controller Template | ISML Template | Core Business Manager Menu IDs | Site Menu (`site=\"true\"`) | Administration Menu (`site=\"false\"`) | Business Manager Extensions Skill | Overview | ⚠️ Schema essentials (read first) | File Structure | Basic bm_extensions.xml | Menu Items | Menu Actions | The `NoPermissionCheck` idiom | Dialog Actions | Form Extensions | Controller Example | Template Example | Attaching to Existing BM Menus | Enabling the Extension | Best Practices | Detailed Reference",
+      "files": [
+        {
+          "path": "references/EXTENSIONS-XML.md",
+          "bytes": 16933
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 15768
+        }
+      ]
+    },
+    {
+      "id": "b2c/b2c-controllers",
+      "collection": "b2c",
+      "title": "b2c-controllers",
+      "description": "Create storefront controllers using SFRA or classic patterns with server.get/post, middleware chains, and res.render/json. Use this skill whenever the user needs to build a page route, handle form submissions, create AJAX endpoints, extend or override existing controllers, or add middleware to a request pipeline. Also use when debugging route registration or response rendering -- even if they just say 'new page endpoint' or 'handle a POST request'.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c/skills/b2c-controllers/SKILL.md",
+      "headings": "Classic Controller Patterns | When to Use Classic Controllers | Basic Structure | Request Handling | Response Types | HTML Response (ISML) | JSON Response | XML Response | Redirect | Status Codes | Error Handling | Database Operations | HTTPS Enforcement | Authentication Check | Complete Example | Comparison: Classic vs SFRA | SFRA Controller Patterns | Basic Route Structure | HTTP Methods | Multiple Middleware | Request Object Properties | Response Methods | View Data Pattern | Route Events | Extending Controllers | Using module.superModule | Append Pattern (Most Common) | Prepend Pattern | Replace Pattern | Common Middleware Examples | Caching Middleware | Authentication Middleware | HTTPS Middleware | CSRF Protection | Form Handling | AJAX Responses | Complete Controller Example | Controllers Skill | Overview | Two Controller Patterns | File Location | SFRA Controllers (Recommended) | Request Object (req) | Response Object (res) | Middleware | Common Middleware | Route Events | Extending Controllers | Classic Controllers (Non-SFRA) | Module Imports | Error Handling | Generating URLs | Best Practices | Detailed Reference",
+      "files": [
+        {
+          "path": "references/CLASSIC-PATTERNS.md",
+          "bytes": 7982
+        },
+        {
+          "path": "references/SFRA-PATTERNS.md",
+          "bytes": 8601
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 8729
+        }
+      ]
+    },
+    {
+      "id": "b2c/b2c-custom-api-development",
+      "collection": "b2c",
+      "title": "b2c-custom-api-development",
+      "description": "Develop Custom SCAPI REST endpoints with api.json routes, schema.yaml definitions, and OAuth scope configuration. Use this skill whenever the user needs to create a custom API on the Commerce platform, define OpenAPI 3.0 schemas for request/response, structure the rest-apis cartridge folder, or debug endpoint registration and 404 issues. Also use when building headless commerce integrations, choosing between Shopper (`ShopperToken`) and Admin (`AmOAuth2`) APIs, or troubleshooting why a Custom API endpoint isn't appearing or returning 404 in `b2c scapi custom status` — even if they just say 'custom REST endpoint', 'expose my script as an API', or 'my admin custom API isn't registering'.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c/skills/b2c-custom-api-development/SKILL.md",
+      "headings": "API Contract Reference (schema.yaml) | Full Schema Example | Contract Requirements | Shopper vs Admin APIs | Admin API call contexts | Path Parameter Example | Request Body Example (POST/PUT/PATCH) | Implementation Reference (script.js) | Complete Implementation Example | Best Practices | Caching Responses | Remote Includes | External Service Calls | services.xml Example | HTTP Methods Supported | Circuit Breaker Protection | Testing Custom APIs | Prerequisites for Testing | Get a Shopper Token (Private Client) | Call Your Custom API | Testing Admin APIs | Get an Admin Token via the CLI (recommended) | Get an Admin Token via curl | Testing Tips | Common Test Failures | Custom API Development Skill | Scope & grounding | Overview | Cartridge Structure | Component 1: API Contract (schema.yaml) | Cartridge path requirements (where the platform looks up your `rest-apis/` folder) | Component 2: Implementation (script.js) | Component 3: Mapping (api.json) | Development Workflow | Deployment | When you need to re-activate the code version (`--reload`) | Authentication Setup | For Shopper APIs | For Admin APIs | Troubleshooting | Registration Issues | Related Skills | Reference Documentation",
+      "files": [
+        {
+          "path": "references/CONTRACT.md",
+          "bytes": 5263
+        },
+        {
+          "path": "references/IMPLEMENTATION.md",
+          "bytes": 4568
+        },
+        {
+          "path": "references/TESTING.md",
+          "bytes": 4826
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 14684
+        }
+      ]
+    },
+    {
+      "id": "b2c/b2c-custom-caches",
+      "collection": "b2c",
+      "title": "b2c-custom-caches",
+      "description": "Implement custom caching with CacheMgr, caches.json definitions, and cache region configuration. Use this skill whenever the user needs to cache expensive computations or API responses server-side, define cache regions with TTL and size limits, invalidate cache entries, or debug disappearing cache data. Also use when optimizing script performance with application-level caching -- even if they just say 'cache this data' or 'my cached values keep disappearing'.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c/skills/b2c-custom-caches/SKILL.md",
+      "headings": "B2C Custom Caches | When to Use Custom Caches | Limitations | Defining a Custom Cache | File Structure | package.json | caches.json | Using Custom Caches | Script API Classes | Basic Usage | Recommended Pattern: get with Loader | Scoped Cache Keys | Cache Methods | Best Practices | Do | Don't | Cache Invalidation | Common Patterns | Caching External API Responses | Caching Expensive Calculations | Configuration Cache with Site Scope | Troubleshooting",
+      "files": [
+        {
+          "path": "SKILL.md",
+          "bytes": 8266
+        }
+      ]
+    },
+    {
+      "id": "b2c/b2c-custom-job-steps",
+      "collection": "b2c",
+      "title": "b2c-custom-job-steps",
+      "description": "Create custom job steps for B2C Commerce batch processing. Use this skill whenever the user needs to write a batch job, data export script, scheduled cleanup task, or any server-side processing that runs on a schedule. Also use when they ask about steptypes.json, chunk-oriented vs task-oriented job steps, read/process/write patterns, how to get a custom job to appear in Business Manager, or how to author and import a jobs.xml job definition (job/flow/step structure, step type, the required triggers element) so a step type becomes a runnable, schedulable job — even if they just say \"I need a script that runs nightly\" or \"batch process orders\".",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c/skills/b2c-custom-job-steps/SKILL.md",
+      "headings": "Chunk-Oriented Job Steps Reference | When to Use | Basic Structure | Product Export Example | Order Processing Example | Customer Sync Example | Chunk Lifecycle | Chunk Size Considerations | Transaction Handling | steptypes.json for Chunk Steps | jobs.xml Reference (Job Definitions) | Namespace & Schema | Document Structure (element order matters) | Minimal Single-Step Job | Step Element | Multi-Step Job | Triggers (required) | run-once (on-demand / manual) | run-recurring (scheduled) | Importing & Running | Common Pitfalls | Related | steptypes.json Reference | File Location | Root Structure | Task-Oriented Step Schema | Chunk-Oriented Step Schema | Step Attributes | Task Step Functions | Chunk Step Functions | Parameters | Parameter Attributes | Parameter Types | Status Codes | Complete Example | Task-Oriented Job Steps Reference | When to Use | Basic Structure | Status Codes | Step Execution Context | FTP Download Example | SFTP Example | HTTP/REST API Example | File Processing Example | Cleanup Example | steptypes.json for Task Steps | Custom Job Steps Skill | When to Use | Overview | File Structure | Step Type Definition (steptypes.json) | From Step Type to Runnable Job (jobs.xml) | Task-Oriented Steps | Script (scripts/steps/myTaskStep.js) | Status Codes | Chunk-Oriented Steps | Required Functions | Optional Functions | Script (scripts/steps/myChunkStep.js) | Parameter Types | Parameter Validation Attributes | Configuration Options | steptypes.json Attributes | Standard (System) Job Steps | Commonly used standard steps | Referencing an IMPEX-staged file from a prior step | Chaining custom + standard steps in one flow | In-flow standard step vs. the CLI equivalent | Best Practices | Related Skills | Detailed Reference",
+      "files": [
+        {
+          "path": "references/CHUNK-ORIENTED.md",
+          "bytes": 10148
+        },
+        {
+          "path": "references/JOBS-XML.md",
+          "bytes": 9451
+        },
+        {
+          "path": "references/STEPTYPES-JSON.md",
+          "bytes": 13956
+        },
+        {
+          "path": "references/TASK-ORIENTED.md",
+          "bytes": 9967
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 22735
+        }
+      ]
+    },
+    {
+      "id": "b2c/b2c-custom-objects",
+      "collection": "b2c",
+      "title": "b2c-custom-objects",
+      "description": "Store and query custom business data using CustomObjectMgr, OCAPI Data API, and Shopper Custom Objects API. Use this skill whenever the user needs to create, read, update, or search custom object instances, build processing queues with status fields, choose between site-scoped and organization-scoped storage, or query custom objects with bool/term filters. Also use when persisting non-standard data -- even if they just say 'store config per site' or 'query my custom data'.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c/skills/b2c-custom-objects/SKILL.md",
+      "headings": "OCAPI Custom Object Search Reference | Search Endpoint | Request Structure | Query Types | Term Query (Exact Match) | Text Query (Full-Text Search) | Range Filter | Boolean Query | Match All Query | Filtered Query | Nested Query | Sorting | Field Selection | Response Structure | Pagination Example | Complex Query Example | Error Handling | B2C Custom Objects | When to Use Custom Objects | Custom Object Types | Script API (CustomObjectMgr) | Getting Custom Objects | Creating Custom Objects | Querying Custom Objects | Deleting Custom Objects | Getting All Objects of a Type | CustomObjectMgr API Reference | OCAPI Data API | Get Custom Object | Create Custom Object | Update Custom Object | Delete Custom Object | Search Custom Objects | Search Query Types | Shopper Custom Objects API (SCAPI) | Get Custom Object (Shopper) | Required Scopes | Searchable System Fields | Best Practices | Do | Don't | Common Patterns | Configuration Store | Processing Queue | Detailed References",
+      "files": [
+        {
+          "path": "references/OCAPI-SEARCH.md",
+          "bytes": 6388
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 9887
+        }
+      ]
+    },
+    {
+      "id": "b2c/b2c-forms",
+      "collection": "b2c",
+      "title": "b2c-forms",
+      "description": "Build forms with validation in B2C Commerce using SFRA patterns. Use this skill whenever the user needs to create a storefront form (checkout, registration, profile edit, address, contact), define form fields in XML, handle form submission in a controller, add field validation rules, or render forms in ISML templates. Also use when they mention form XML definitions, server.forms.getForm, form groups/actions/lists, or CSRF protection on form posts — even if they just say \"I need a registration form\" or \"add validation to checkout\".",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c/skills/b2c-forms/SKILL.md",
+      "headings": "Form XML Reference | XSD Schema Reference | XML Schema | Field Element | All Attributes | Field Types | String Field | Integer Field | Number Field (Decimal) | Boolean Field | Date Field | Validation Patterns | Common Regular Expressions | Custom Validation Script | Groups | Lists | Actions | Object Binding | Complete Examples | Login Form | Address Form | Registration Form with Password Confirmation | Forms Skill | Overview | File Location | Form Definition (XML) | Basic Structure | Field Types | Key Field Attributes | Validation Error Messages | Controller Logic (SFRA) | Rendering a Form | Processing Form Submission | Prepopulating Forms | Template (ISML) | Basic Form Template | Localization | Best Practices | Detailed Reference",
+      "files": [
+        {
+          "path": "references/FORM-XML.md",
+          "bytes": 11322
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 7481
+        }
+      ]
+    },
+    {
+      "id": "b2c/b2c-hooks",
+      "collection": "b2c",
+      "title": "b2c-hooks",
+      "description": "Register and implement B2C Commerce platform hooks declared in hooks.json and invoked by HookMgr during OCAPI/SCAPI requests or system events. Use for hooks.json, HookMgr.callHook(), dw.system.Status, dw.ocapi.shop.* before/after/modifyResponse hooks, dw.order.payment.authorize/authorizeCreditCard, dw.order.calculate, app.payment.processor.*, SCAPI order-payment authorization and placement, rollback semantics, and request.custom transport. Do not use for external Node.js webhooks, SFRA controller middleware or prepend/append chains, scheduled job steps in steptypes.json, or Git/CI hooks.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c/skills/b2c-hooks/SKILL.md",
+      "headings": "OCAPI/SCAPI Hooks Reference | Prerequisites | Hook Naming Convention | Complete Hook Reference | Authentication | Basket | Basket Billing Address | Basket Customer | Basket Coupon | Basket Items | Basket Gift Certificate Item | Basket Payment Instrument | Basket Payment Methods | Basket Shipment | Basket Shipment Shipping Address | Basket Shipment Shipping Method | Basket Shipments Shipping Methods | Category | Customer | Customer Auth | Customer Address | Customer Baskets | Customer Orders | Customer Password | Customer Payment Instrument | Customer Product Lists | Customer Product List Items | Gift Certificate | Order | Order Payment Instrument | Order Payment Methods | Product | Product Search | Promotion | Search Suggestion | Store | Common Patterns | Validation (return error to reject request) | Modify Response (add custom properties) | Custom Properties | Notes | Shopper Order Payment Lifecycle (SCAPI/OCAPI) | Recommended Lifecycle | Hook Responsibilities | Payment-Instrument Resolution | Success and Failure Handling | Alternative: Complete Checkout in `order.afterPOST` | Two-Hook Variant | Cross-References | System Hooks Reference | Calculate Hooks | Extension Points | Registration | SFRA Implementation | SCAPI Consideration | Payment Hooks | Extension Points | Authorization Flow | Capture Flow | Refund Flow | Order Hooks | Order Number Generation | Checkout Hooks | Return Hooks | Shipping Order Hooks | Basket Merge Hooks | Request Hooks | Custom Extension Points | Hook Execution Order | Best Practices | Calculate Hooks | Payment Hooks | General | B2C Commerce Hooks | Hook Types Overview | Hook Registration | File Structure | package.json | hooks.json | Hook Script | HookMgr API | Status Object | Return Value Behavior (Important) | When to Return a Value | When NOT to Return a Value | Summary | OCAPI/SCAPI Hooks | Hook Types | Common Hook Patterns | Passing Data Between Hooks | Detect SCAPI vs OCAPI | Headless Order Payment: Use the Order-PI Authorization Seam | Authorization Semantics | Storefront/BFF Outcome Handling | Alternative: Authorize and Place in `order.afterPOST` | `request.custom` for Inter-Hook Data Passing | System Hooks | Calculate Hooks | Payment Hooks | Order Hooks | Custom Hooks | Remote Includes in Hooks | Best Practices | Error Handling | Circuit Breaker | Timeout | Detailed References",
+      "files": [
+        {
+          "path": "references/OCAPI-SCAPI-HOOKS.md",
+          "bytes": 24101
+        },
+        {
+          "path": "references/ORDER-HOOK-LIFECYCLE.md",
+          "bytes": 7901
+        },
+        {
+          "path": "references/SYSTEM-HOOKS.md",
+          "bytes": 16228
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 18143
+        }
+      ]
+    },
+    {
+      "id": "b2c/b2c-isml",
+      "collection": "b2c",
+      "title": "b2c-isml",
+      "description": "Build ISML templates with isprint, isset, isloop, isdecorate, isinclude tags, and ${...} expression syntax. Use this skill whenever the user needs to write or debug storefront templates, create decorator layouts with isreplace, build reusable template modules, control HTML encoding in output, or use ISML expression language for dynamic content. Also use when fixing template rendering issues -- even if they just say 'loop through products in the template' or 'my HTML is getting escaped'.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c/skills/b2c-isml/SKILL.md",
+      "headings": "ISML Expressions Reference | Expression Syntax | Property Access | Built-in Objects | pdict | session | request | response | customer | Operators | Arithmetic | Comparison | Logical | Ternary | String Concatenation | Null Check | Built-in Functions | empty() | Utility Classes | URLUtils | Resource | StringUtils | dw.util.Locale | Date/Time | Formatting Dates | Current Date | Collection Operations | Iteration | Size/Length | Check Contents | Common Patterns | Null-safe Access | Default Values | Conditional Classes | Price Formatting | Product Images | Localized Attributes | ISML Tags Reference | Control Flow Tags | isif / iselseif / iselse | isloop | isbreak / iscontinue / isnext | Variable Tags | isset | isremove | Output Tags | isprint | Template Composition | isinclude | isdecorate / isreplace | ismodule | Content Tags | iscontent | iscache | iscomment | iscomponent | Navigation Tags | isredirect | isstatus | Form Tags | isselect | Script Tag | isscript | Slot Tag | isslot | Cookie Tag | iscookie | Active Data Tags | isobject | isactivedatahead | isactivedatacontext | isanalyticsoff | Special Tags | isprint with style options | ISML Skill | Overview | File Location | Essential Tags | Conditional Logic | Loops | Variables | Output | Include Templates | Decorator Pattern | Expressions | Built-in Utilities | URLUtils | Resource (Localization) | StringUtils | Custom Modules | Caching | Content Type | Embedded Scripts | Comments | Tag Location Constraints | Best Practices | Detailed Reference",
+      "files": [
+        {
+          "path": "references/EXPRESSIONS.md",
+          "bytes": 6434
+        },
+        {
+          "path": "references/TAGS.md",
+          "bytes": 10031
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 8627
+        }
+      ]
+    },
+    {
+      "id": "b2c/b2c-localization",
+      "collection": "b2c",
+      "title": "b2c-localization",
+      "description": "Add translations and multi-language support to B2C Commerce storefronts. Use this skill whenever the user needs to translate a storefront, add a new locale, create or edit .properties resource bundles, display translated strings in templates, format dates or currencies for different regions, or build a language switcher. Also use when they mention Resource.msg, Resource.msgf, locale fallback, or i18n — even if they just say \"we need French translations\" or \"make this page work in multiple languages\".",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c/skills/b2c-localization/SKILL.md",
+      "headings": "Localization Patterns Reference | Resource Bundle Organization | Recommended Structure | Bundle Content Patterns | Template Patterns | Page Layout | Form Labels | Pluralization | Date Formatting | Number Formatting | Controller Patterns | Locale-Aware Controller | Multi-Locale Email | JavaScript Client-Side | Passing Messages to JS | Using in JS | Special Characters | Escaping in Properties | UTF-8 Encoding | Testing Localization | Pseudo-Localization | Checklist | Localization Skill | Overview | Locale Format | Resource Bundles | Directory Structure | Property File Format | Using Resources in Templates | Parameterized Messages | Locale Fallback | Static Files | Directory Structure | Referencing Static Files | Forms Localization | Form Definition | Resource Bundle | URL Localization | Locale-Aware URLs | Language Switcher | Controller Localization | Accessing Current Locale | Locale-Specific Logic | Email Templates | Setting Locale | Currency Formatting | Date Formatting | Best Practices | Detailed Reference",
+      "files": [
+        {
+          "path": "references/PATTERNS.md",
+          "bytes": 10391
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 9168
+        }
+      ]
+    },
+    {
+      "id": "b2c/b2c-logging",
+      "collection": "b2c",
+      "title": "b2c-logging",
+      "description": "Implement server-side logging with dw.system.Logger, custom log categories, and named log files. Use this skill whenever the user needs to add debug or error logging to Commerce scripts, write to a dedicated log file, configure log categories and levels, or use nested diagnostic context for tracing. Also use when setting up logging in controllers, hooks, or job scripts -- even if they just say 'add logging to my script' or 'write to a custom log file'.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c/skills/b2c-logging/SKILL.md",
+      "headings": "Log Files Reference | Log File Types | Custom Log Files | System Log Files | Custom Named Log Files | Log File Locations | WebDAV Access | Business Manager Access | Log Retention | Archive Process | Storage Limits | Custom Log Size Limits | File Count Limits | Custom Log File Quota | Log Entry Format | Standard Format | With NDC | Redundancy Tracking | Quota Log Format | Security Log Format | Import/Export Logs | Accessing Logs Programmatically | Via WebDAV Client | Via B2C CLI | Debug Logging on Production | Best Practices | 1. Monitor Log File Sizes | 2. Use Custom Named Logs for Integrations | 3. Clean Up Old Logs | 4. Configure Categories in Business Manager | 5. Use Appropriate Log Levels | Logging Skill | Overview | Log Levels | Basic Logging | Using Logger (Static Methods) | Using Log (Instance Methods) | Categories | Custom Named Log Files | File Name Rules | File Naming Pattern | Quota | Checking Log Level Status | Static Level Checks | Message Formatting | Nested Diagnostic Context (NDC) | NDC Methods | Best Practices | 1. Use Categories | 2. Check Level Before Expensive Operations | 3. Include Context in Messages | 4. Use Appropriate Levels | 5. Use Custom Log Files for Integration | 6. Don't Log Sensitive Data | Business Manager Configuration | Configuring Categories | Log Output Format | Detailed Reference | Script API Classes",
+      "files": [
+        {
+          "path": "references/LOG-FILES.md",
+          "bytes": 7369
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 10009
+        }
+      ]
+    },
+    {
+      "id": "b2c/b2c-metadata",
+      "collection": "b2c",
+      "title": "b2c-metadata",
+      "description": "Define custom attributes, custom object types, and site preferences for B2C Commerce using metadata XML. Use this skill whenever the user needs to add a field to products, orders, or customers, create a new custom object type, set up site preferences, or extend the B2C data model. Also use when they ask about system-objecttype-extensions.xml, custom-objecttype-definitions.xml, attribute groups in Business Manager, or data model definitions — even if they just say \"add a field to products\" or \"I need a new object type\".",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c/skills/b2c-metadata/SKILL.md",
+      "headings": "System Objects Reference | Product-Related | Product | ProductLineItem | Category | Order-Related | Order | Basket | Shipment | Customer-Related | Profile | CustomerAddress | Content-Related | Content | Folder | Site Configuration | SitePreferences | OrganizationPreferences | Other Objects | Store | GiftCertificate | SourceCodeGroup | Complete List of System Objects | Metadata XML Examples | XSD Schema Reference | Site Archive Structure | Adding Custom Attributes to Products | Metadata (meta/system-objecttype-extensions.xml) | Adding Custom Attributes to Orders | Custom Object Definition | Site Preferences | Metadata | Preference Values (sites/RefArch/preferences.xml) | Product Data with Custom Attributes | Custom Object Data | Metadata Skill | Scope & grounding | Overview | Site Archive Structure | System Object Extensions | Basic Structure | Common System Objects | Attribute Types | Enum Value Definitions | Product Custom Attribute Example | Custom Object Definitions | Site Preferences | Metadata (system-objecttype-extensions.xml) | Values (sites/MySite/preferences.xml) | Access in Code | Attribute Definition Options | Best Practices | Quick Reference",
+      "files": [
+        {
+          "path": "references/SYSTEM-OBJECTS.md",
+          "bytes": 9335
+        },
+        {
+          "path": "references/XML-EXAMPLES.md",
+          "bytes": 15657
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 17974
+        }
+      ]
+    },
+    {
+      "id": "b2c/b2c-onboarding",
+      "collection": "b2c",
+      "title": "b2c-onboarding",
+      "description": "Get started with Salesforce B2C Commerce development. Use this skill when the user is new to B2C Commerce, wants to set up a fresh development environment, is asking \"how do I get started\", needs to install the B2C CLI for the first time, wants to connect a sandbox, or wants to deploy their first cartridge. Triggers on phrases like \"help me get started\", \"set up B2C Commerce\", \"I'm new to this\", \"onboard me\", or \"first-time setup\". NOT for users who already have a configured environment and are asking about specific commands — those should go to the specific skill (b2c-code, b2c-sandbox, b2c-config, etc.).",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c/skills/b2c-onboarding/SKILL.md",
+      "headings": "B2C Commerce Onboarding Skill | Behavioral rules | Flow | Step 1 — Identify the editor | Step 2 — Install the other B2C skills plugins | Step 3 — Verify the B2C CLI is available | Step 4 — Account Manager access check | Step 5 — Check for existing configuration | Step 6 — Initialize configuration | Step 7 — Sandbox | Step 8 — First cartridge deploy (if applicable) | Step 9 — Route to the user's goal | Reference",
+      "files": [
+        {
+          "path": "SKILL.md",
+          "bytes": 7737
+        }
+      ]
+    },
+    {
+      "id": "b2c/b2c-ordering",
+      "collection": "b2c",
+      "title": "b2c-ordering",
+      "description": "Manage the order lifecycle in B2C Commerce including order creation, status transitions, failure handling, and checkout completion. Use this skill whenever the user needs to create an order from a basket, transition order status, handle failed or cancelled orders, implement payment authorization in checkout, or understand async order processing — even if they just say \"my order is stuck\" or \"finish the checkout flow\".",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c/skills/b2c-ordering/SKILL.md",
+      "headings": "B2C Ordering | Order Lifecycle | Creating Orders | Standard Flow (Synchronous) | SCAPI Flow: Create, Authorize Through Order PI, Then Place | OrderMgr API Reference | Order Creation | Order Status | Order Queries | Querying Orders | Get Order by Number | Search Orders | Query by Date Range | Order Status Management | Cancel Order | Fail Order | Handling Failed Orders | SCAPI: Fail Order and Reopen Basket | Undo Cancelled Order | Order Properties | Custom Order Numbers | Best Practices | Do | Don't | Error Handling | Related Skills",
+      "files": [
+        {
+          "path": "SKILL.md",
+          "bytes": 12120
+        }
+      ]
+    },
+    {
+      "id": "b2c/b2c-page-designer",
+      "collection": "b2c",
+      "title": "b2c-page-designer",
+      "description": "Define Page Designer page types and component types with regions, attributes, and rendering scripts. Use this skill whenever the user needs to create a new page or component type, configure regions with allowed component constraints, define attribute_definition_groups, debug why a component does not appear in the editor, or fix enum/color attribute pitfalls. Also use when building visual merchandising experiences -- even if they just say 'my component is missing from PD' or 'add a hero banner component'.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c/skills/b2c-page-designer/SKILL.md",
+      "headings": "Page Designer Attribute Types Reference | String Types | string | text | markup | Numeric Types | integer | Boolean Type | boolean | Selection Types | enum | enum with display names | Media Types | image | file | URL Type | url | Commerce Types | product | category | page | CMS Type | cms_record | Custom Type | custom | Complete Component Example | Page Designer Meta Definitions Reference | Page Type Schema | Page Type Properties | Region Definition Properties | Component Type Schema | Component Type Properties | Attribute Definition Properties | Complete Page Type Example | Complete Component Type Example | Container Component Example | Page Script Context | Component Script Context | Page Designer Skill | Scope & grounding | Overview | File Structure | Page Types | Meta Definition (pages/homepage.json) | Page Script (pages/homepage.js) | Page Template (templates/default/experience/pages/homepage.isml) | Component Types | Meta Definition (components/banner.json) | Component Script (components/banner.js) | Component Template (templates/experience/components/banner.isml) | Attribute Types | Region Definitions | Rendering Pages | In Controllers | In ISML | Component Groups | If the component does not appear in Page Designer | Best Practices | Detailed Reference",
+      "files": [
+        {
+          "path": "references/ATTRIBUTE-TYPES.md",
+          "bytes": 8272
+        },
+        {
+          "path": "references/META-DEFINITIONS.md",
+          "bytes": 10494
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 16065
+        }
+      ]
+    },
+    {
+      "id": "b2c/b2c-querying-data",
+      "collection": "b2c",
+      "title": "b2c-querying-data",
+      "description": "Write efficient data queries in B2C Commerce for products, customers, and orders. Use this skill whenever the user needs to search products on a storefront page, look up customer profiles, query orders, paginate search results, or fix slow category pages. Also use when they ask about performance problems with data access, replacing database-intensive APIs with index-backed alternatives, or choosing between search vs query methods — even if they just say \"my category page is slow\" or \"how do I find customers by email\".",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c/skills/b2c-querying-data/SKILL.md",
+      "headings": "Performance-Critical APIs | Product APIs | Database-Intensive (Avoid on Storefront Pages) | Index-Friendly Replacements | Order APIs | Customer / Profile APIs | Custom Object APIs | General Query Performance Rules | Querying Data in B2C Commerce | Product Search (Storefront) | Basic Product Search | Paging Search Results | Getting Variation Data from Search Hits | Search Refinements | ProductSearchModel API Summary | Order Queries | OrderMgr.searchOrders / queryOrders | Query by Date Range | searchOrders vs queryOrders | Customer / Profile Queries | CustomerMgr (Preferred) | Batch Processing (Jobs) | Customer Query Behaviors | System Object Queries (SystemObjectMgr) | Database-Intensive APIs to Avoid | Related Skills | Best Practices | Do | Don't | Job-Specific Guidelines | Detailed References",
+      "files": [
+        {
+          "path": "references/PERFORMANCE-APIS.md",
+          "bytes": 4476
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 10467
+        }
+      ]
+    },
+    {
+      "id": "b2c/b2c-scapi-admin",
+      "collection": "b2c",
+      "title": "b2c-scapi-admin",
+      "description": "Build backend integrations that sync data between B2C Commerce and external systems like ERPs, OMS, WMS, or CRMs using SCAPI Admin APIs. Use this skill whenever the user needs to pull or push orders, products, inventory, or customer data programmatically from a backend service, set up server-to-server authentication with Account Manager client credentials and admin OAuth scopes, implement bulk inventory imports with NDJSON, or call any Commerce API from a script or pipeline (not a storefront). Also use when building nightly data exports, warehouse sync jobs, or customer data integrations — even if they just say \"pull orders into our ERP\" or \"sync inventory from the warehouse\".",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c/skills/b2c-scapi-admin/SKILL.md",
+      "headings": "SCAPI Client Examples | Overview | Base URL Structure | Authentication | Get Admin Token via CLI | Get Token Programmatically | Dual Scope Requirement | Account Manager Setup | API Families | Products API | Catalogs API | Orders API | Inventory Availability API | Inventory IMPEX API | Customers API | Promotions API | Request Tracking | Correlation IDs | Verbose Logging | Error Handling | Common Errors | Rate Limiting | Related Skills | Reference Documentation | Integration Patterns Reference | Inventory Sync Pattern | Real-Time Inventory Updates | Bulk Inventory Import (IMPEX) | Best Practices for Inventory IMPEX | Order Export Pattern | Polling for New Orders | Order Status Updates | Product Sync Pattern | Delta Product Updates | Customer Data Sync Pattern | Export Customers to CRM | Error Handling Pattern | Retry with Exponential Backoff | Dead Letter Queue Pattern | Token Management Pattern | Automatic Token Refresh | Monitoring Pattern | Request Logging | Scheduling Best Practices | Spread Load Over Time | Off-Peak Processing | Idempotency | Admin API OAuth Scopes Reference | Scope Format | Scope Suffix Convention | Getting Tokens with Scopes | Via CLI | Via cURL | Product API Scopes | Order API Scopes | Inventory API Scopes | Pricing API Scopes | Customer Management Scopes | Configuration Scopes | Experience Scopes | CDN API Scopes | Developer API Scopes | SLAS Admin Scopes | Recommended Scope Sets | Order Management Integration | Catalog/Product Sync | Inventory Sync | Customer Data Sync | Read-Only Analytics/Reporting | Full Admin Access | Best Practices | Principle of Least Privilege | Separate Clients for Different Integrations | Token Caching | Audit Scope Usage | Scope Errors | 403 Forbidden - Missing Scope | 403 Forbidden - Missing Tenant Scope | Invalid Scope Error | SCAPI Admin APIs | Tool choice | Execute deliberately | Conditional references",
+      "files": [
+        {
+          "path": "references/CLIENT-EXAMPLES.md",
+          "bytes": 13741
+        },
+        {
+          "path": "references/INTEGRATION-PATTERNS.md",
+          "bytes": 15062
+        },
+        {
+          "path": "references/OAUTH-SCOPES.md",
+          "bytes": 10069
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 3575
+        }
+      ]
+    },
+    {
+      "id": "b2c/b2c-scapi-shopper",
+      "collection": "b2c",
+      "title": "b2c-scapi-shopper",
+      "description": "Call Shopper Commerce APIs (SCAPI) from headless storefronts and composable commerce apps. Use this skill whenever the user is building with PWA Kit, Storefront Next (SFNext), or a headless frontend and needs to search products, manage baskets, submit orders, access customer data, or set shopper context. Also use when they ask about Shopper API authentication, checkout flows from a frontend app, or performance optimization for API calls — even if they just say \"search products from my PWA\" or \"build a headless checkout\".",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c/skills/b2c-scapi-shopper/SKILL.md",
+      "headings": "Checkout Flow Reference | Flow Overview | Prerequisites | Step 1: Create Basket | Step 2: Add Items | Update Item Quantity | Remove Item | Step 3: Set Customer Info | Step 4: Set Shipping Address | Step 5: Get and Select Shipping Method | Get Available Shipping Methods | Set Shipping Method | Step 6: Add Payment Instrument | Set Billing Address | Step 7: Submit Order | Step 8: Authorize the Order Payment Instrument | Step 9: Fail a Deterministically Declined Order | Single-Request Basket Creation | Multiple Shipments | Applying Promotions | Apply Coupon Code | Remove Coupon | Error Handling | Common Basket Errors | Basket Validation | SCAPI Client Examples | Overview | Base URL Structure | Configuration Values | Authentication | Create SLAS Client | Get Guest Token | Required Scopes | API Families | Shopper Products | Shopper Search | Shopper Baskets | Shopper Orders | Shopper Customers | Shopper Context API | When to Set Context | Quota Limits | Best Practices | Performance Optimization | Use `select` Parameter | Use `expand` Carefully | Enable Compression | Debugging | Correlation IDs | Verbose Logging | Related Skills | Reference Documentation | Common Patterns Reference | Response Optimization | Field Selection with `select` | Using `expand` Parameter | Compression | Pagination | Offset-Based Pagination | Response Metadata | Error Handling | Error Response Format | Common HTTP Status Codes | Error Handling Pattern | Retry with Exponential Backoff | URL Encoding | Special Characters | Query Parameters | Caching Strategies | Client-Side Caching | CDN Cache Headers | Request Batching | Multiple Products | Parallel Requests | Debugging Requests | Include Correlation ID | Verbose Logging | Log Request/Response | Shopper API Scopes Reference | Scope Overview | Scope Categories | Product APIs | Search APIs | Checkout APIs | Customer APIs | Pricing APIs | Store APIs | Context APIs | Configuration APIs | Product Lists APIs | Special Scopes | Authentication Scopes | Trusted Agent/System Scopes | AI Agent Scope | Custom Scopes | Default Scopes | Recommended Scope Sets | Basic Shopping App (PWA Kit) | Read-Only Catalog Browser | Guest Checkout Only | Full Customer Experience | Best Practices | Minimize Scope Set | Avoid Redundant Scopes | Separate Clients for Different Purposes | Don't Mix Admin and Shopper Scopes | Verifying Token Scopes | Shopper Commerce APIs | Tool choice | Integration essentials | Conditional references",
+      "files": [
+        {
+          "path": "references/CHECKOUT-FLOW.md",
+          "bytes": 14479
+        },
+        {
+          "path": "references/CLIENT-EXAMPLES.md",
+          "bytes": 11952
+        },
+        {
+          "path": "references/COMMON-PATTERNS.md",
+          "bytes": 9837
+        },
+        {
+          "path": "references/SCOPES.md",
+          "bytes": 8446
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 3497
+        }
+      ]
+    },
+    {
+      "id": "b2c/b2c-slas-auth-patterns",
+      "collection": "b2c",
+      "title": "b2c-slas-auth-patterns",
+      "description": "Implement SLAS authentication patterns in B2C Commerce including passwordless login (email OTP, SMS OTP, passkeys), session bridging between PWA Kit/Storefront Next and SFRA, hybrid authentication (B2C 25.3+), token refresh flows, trusted system on behalf of (TSOB), and JWT validation. Use this skill whenever the user asks about shopper authentication beyond basic login, token exchange flows, passwordless or biometric auth, keeping sessions alive across storefronts, handling 409 Conflict errors on token endpoints, refreshing shopper tokens, or validating JWTs — even if they don't mention SLAS by name.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c/skills/b2c-slas-auth-patterns/SKILL.md",
+      "headings": "Passkeys (FIDO2/WebAuthn) | Registration Flow (3 Steps) | Authentication Flow | Session Bridge Reference | Token Types | PWA Kit to SFRA | Step 1: Generate Bridge Tokens | Step 2: Redirect with Tokens | Step 3: SFRA Establishes Session | SFRA to PWA Kit | Step 1: Generate Bridge Tokens in SFRA | Step 2: Redirect to PWA Kit | Step 3: PWA Kit Handles Callback | Hybrid Navigation Component | Error Handling | Security Considerations | Testing | Token Lifecycle Reference | Token Types and Expiry | Access Token Lifecycle | Best Practices for Access Tokens | Refresh Token Patterns | Public Client (Single-Use) | Private Client (Reusable) | Token Rotation Strategy | Public Clients - Handle Race Conditions | Storage Strategies | Session Timeout Handling | Proactive Refresh | Activity-Based Extension | Guest to Registered Transition | Logout and Token Revocation | Error Handling Reference | Debugging Token Issues | B2C SLAS Authentication Patterns | Scope & grounding | Canonical docs | Authentication Methods Overview | Passwordless Email OTP | Flow Overview | Step 1: Initiate Passwordless Login | Step 2: Handle Callback and Send OTP | Step 3: Exchange OTP for Tokens | Rate Limits | Passwordless SMS OTP | Using Marketing Cloud | Custom SMS Provider | Passkeys (FIDO2/WebAuthn) | Session Bridge | Hybrid Authentication (B2C 25.3+) | Benefits | Migration from Plugin SLAS | Token Refresh | Public Clients (Single-Use Refresh) | Private Clients (Reusable Refresh) | Trusted System on Behalf (TSOB) | Use Cases | Get Token on Behalf of Shopper | Important Constraints | Required Configuration | JWT Validation | Get JWKS | Validate Token | Token Claims | Best Practices | Security | Token Management | User Experience | Detailed References",
+      "files": [
+        {
+          "path": "references/PASSKEYS.md",
+          "bytes": 4525
+        },
+        {
+          "path": "references/SESSION-BRIDGE.md",
+          "bytes": 7808
+        },
+        {
+          "path": "references/TOKEN-LIFECYCLE.md",
+          "bytes": 9793
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 15862
+        }
+      ]
+    },
+    {
+      "id": "b2c/b2c-webservices",
+      "collection": "b2c",
+      "title": "b2c-webservices",
+      "description": "Implement web service integrations in B2C Commerce using LocalServiceRegistry. Use this skill whenever the user needs to call external REST or SOAP APIs from a cartridge, configure service credentials and profiles in services.xml, handle HTTP requests with createRequest/parseResponse callbacks, set up FTP or SFTP file transfers, or troubleshoot circuit breaker errors. Also use when connecting to payment gateways, shipping providers, or third-party services -- even if they just say 'call an external API from my controller' or 'my service keeps timing out'.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c/skills/b2c-webservices/SKILL.md",
+      "headings": "FTP/SFTP Services Reference | FTPService Methods | Configuration Styles | Style 1: setOperation (Simple) | Style 2: execute (Advanced) | SFTP Operations | List Directory | Download File | Download to String | Download to Local File | Upload File | Upload String Content | Upload Local File | Delete File | Create Directory | Move/Rename File | Complex Multi-Operation Example | Keep Connection Open | SFTP Key Authentication | File Info | Mock FTP Operations | FTP (Legacy) | HTTP Services Reference | HTTPService Methods | HTTPClient Properties (in parseResponse) | REST API Examples | GET Request | POST with JSON Body | PUT Request | DELETE Request | GET with Query Parameters | Authentication Patterns | Basic Authentication | Bearer Token (OAuth) | API Key Authentication | OAuth 2.0 Client Credentials Flow | Form Submissions (HTTPForm) | Multipart Form Data | Downloading Files | Response Caching | Custom HTTP Client Configuration | Mutual TLS (mTLS) | XML API Example | Error Response Handling | Services XML Import/Export Reference | XSD Schema Reference | XML Namespace | XML Structure | Service Credential | Credential Elements | Password Encryption | Credential with Custom Attributes | Service Profile | Profile Elements | Profile Examples | Service | Service Elements | Service Types | Complete Example | Delete Mode | Import via CLI | Export via Business Manager | Best Practices | SOAP Services Reference | SOAPService Methods | SOAP Service Setup | 1. Upload WSDL | 2. Generate Stub | 3. Create Service Configuration | Basic SOAP Service | Alternative: Set Client in createRequest | WS-Security | WSUtil Methods | WS-Security with Timestamps | Custom SOAP Headers | Handling Complex Types | Error Handling | Mock SOAP Services | Multiple Operations | Setting SOAP Endpoint | MTOM/Attachments | Web Services Skill | Overview | Service Types | Service Framework Components | Business Manager Configuration | Script Components | Basic Pattern | Service Callbacks | Result Object | Unavailable Reasons | Error Handling | Log Filtering | Mocking Services | Service Configuration in Business Manager | Creating a Service | Service Profile Settings | Service Credential Settings | Detailed References | Script API Classes",
+      "files": [
+        {
+          "path": "references/FTP-SERVICES.md",
+          "bytes": 12987
+        },
+        {
+          "path": "references/HTTP-SERVICES.md",
+          "bytes": 14908
+        },
+        {
+          "path": "references/SERVICES-XML.md",
+          "bytes": 10962
+        },
+        {
+          "path": "references/SOAP-SERVICES.md",
+          "bytes": 17847
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 10289
+        }
+      ]
+    },
+    {
+      "id": "b2c-ops/b2c-checkout-triage",
+      "collection": "b2c-ops",
+      "title": "b2c-checkout-triage",
+      "description": "Investigate B2C Commerce checkout or payment failures, increased failed orders, or falling order volume. Compare bounded order evidence, integration logs and affected data; separate payment failures from traffic and reporting gaps.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c-ops/skills/b2c-checkout-triage/SKILL.md",
+      "headings": "Checkout and payment triage | Scope and impact | Access and tools | Checks and decisions | Mitigation and recovery | Escalation and handoff",
+      "files": [
+        {
+          "path": "SKILL.md",
+          "bytes": 5326
+        }
+      ]
+    },
+    {
+      "id": "b2c-ops/b2c-job-health",
+      "collection": "b2c-ops",
+      "title": "b2c-job-health",
+      "description": "Review B2C Commerce scheduled jobs during routine operations or investigate failed jobs, missing runs, stale imports, and green executions with incomplete results. Check logs and business data before proposing a rerun.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c-ops/skills/b2c-job-health/SKILL.md",
+      "headings": "Job execution logs | Job health | Scope and impact | Access and tools | Checks and decisions | Mitigation and recovery | Escalation and handoff",
+      "files": [
+        {
+          "path": "references/job-logs.md",
+          "bytes": 1263
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 4839
+        }
+      ]
+    },
+    {
+      "id": "b2c-ops/b2c-order-failure-triage",
+      "collection": "b2c-ops",
+      "title": "b2c-order-failure-triage",
+      "description": "Find and investigate FAILED B2C Commerce orders, quantify their share of indexed orders, and correlate failed inputs with logs and jobs. Covers SCAPI status-filter limitations and the OCAPI Shop order_search fallback.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c-ops/skills/b2c-order-failure-triage/SKILL.md",
+      "headings": "Failed-order search recipe | Choose a supported surface | Access and execution | Bounded query recipe | Errors and interpretation | Failed-order triage | Scope and impact | Access and tools | Checks and decisions | Mitigation and recovery | Escalation and handoff",
+      "files": [
+        {
+          "path": "references/order-evidence.md",
+          "bytes": 4051
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 5265
+        }
+      ]
+    },
+    {
+      "id": "b2c-ops/b2c-production-triage",
+      "collection": "b2c-ops",
+      "title": "b2c-production-triage",
+      "description": "Investigate B2C Commerce incidents using B2C MCP logs, SCAPI code-mode job/data reads, and CLI fallbacks. Route error spikes, stale data, or checkout failures to focused runbooks and produce a team or Support handoff.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/b2c-ops/skills/b2c-production-triage/SKILL.md",
+      "headings": "Escalation and support cases | Select the owner | Case or handoff draft | Official platform guidance | Production triage | Scope and impact | Access and tools | Checks and decisions | Mitigation and recovery | Escalation and handoff",
+      "files": [
+        {
+          "path": "references/escalation.md",
+          "bytes": 5594
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 7592
+        }
+      ]
+    },
+    {
+      "id": "storefront-next/sfnext-authentication",
+      "collection": "storefront-next",
+      "title": "sfnext-authentication",
+      "description": "Implement authentication in Storefront Next using split-cookie architecture, SLAS tokens, and auth middleware. Use when accessing user identity in loaders, detecting guest vs registered users, using getAuth or useAuth, or understanding session management and token refresh.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/storefront-next/skills/sfnext-authentication/SKILL.md",
+      "headings": "Authentication Skill | Overview | Cookie Design | Usage in Loaders/Actions | Usage in Components | Common Patterns | Protected Routes | Conditional Data Loading | Troubleshooting | Related Skills",
+      "files": [
+        {
+          "path": "SKILL.md",
+          "bytes": 3717
+        }
+      ]
+    },
+    {
+      "id": "storefront-next/sfnext-components",
+      "collection": "storefront-next",
+      "title": "sfnext-components",
+      "description": "Build UI components in Storefront Next using createPage HOC, Suspense/Await patterns, shadcn/ui, and Tailwind CSS v4. Use when creating page components, adding Suspense boundaries, integrating shadcn/ui, styling with Tailwind, or organizing component files. Covers server vs client rendering patterns and the cn() utility.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/storefront-next/skills/sfnext-components/SKILL.md",
+      "headings": "Components Skill | Page Component Pattern | createPage HOC (Optional) | Suspense Boundaries and Code Splitting | shadcn/ui Components | Tailwind CSS Styling | Dark Mode | Responsive Design | File Organization | Best Practices | Related Skills",
+      "files": [
+        {
+          "path": "SKILL.md",
+          "bytes": 6110
+        }
+      ]
+    },
+    {
+      "id": "storefront-next/sfnext-configuration",
+      "collection": "storefront-next",
+      "title": "sfnext-configuration",
+      "description": "Manage Storefront Next application configuration using config.server.ts, schema types, environment variables, and multi-site setup. Use when editing config.server.ts, adding PUBLIC__ environment variables, using useConfig or getConfig, or configuring multiple sites. NOT for initial project creation — see sfnext-project-setup.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/storefront-next/skills/sfnext-configuration/SKILL.md",
+      "headings": "Configuration Skill | Overview | Adding Configuration | 1. Define the type in `src/types/config.ts` | 2. Set defaults in `config.server.ts` | 3. Override via environment variables | Accessing Configuration | In React Components | In Server Loaders/Actions | In Browser Code (Non-Route Modules) | Environment Variable Rules | Multi-Site Configuration | Security | Common Pitfalls | Related Skills",
+      "files": [
+        {
+          "path": "SKILL.md",
+          "bytes": 5008
+        }
+      ]
+    },
+    {
+      "id": "storefront-next/sfnext-create-component",
+      "collection": "storefront-next",
+      "title": "sfnext-create-component",
+      "description": "Author a new Storefront Next design-system component the right way — pick the correct layer (primitive vs composite), reuse-or-extend before creating, define CVA variants bound to semantic tokens, add data-slot attributes, satisfy the accessibility checklist, and ship a Storybook story. Use when asked to create, add, or build a new UI component, button/badge/tile/card variant, or design-system primitive. This is the design-system authoring discipline; for createPage/Suspense/shadcn page-rendering patterns see sfnext-components.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/storefront-next/skills/sfnext-create-component/SKILL.md",
+      "headings": "Component authoring standards | Vertical extensions — existing components always have priority | Decision gate (run this before creating any extension component) | Concrete examples | Extend before create — mandatory check before any new component | Multi-vertical extension governance | Layer model — know which layer you are in before writing a line | Primitives (`src/components/ui/`) | CVA — class-variance-authority | data-slot attributes | TypeScript requirements | Copyright header | Naming conventions | Storybook requirement | Accessibility checklist | Project Structure Reference | Key architecture | Theme file layout (the vertical surface) | App file organization | Common commands | Token System Reference | The one rule that overrides everything else | Token files and what they own | Semantic token meanings — use the right one | Text colors | Background colors | Borders | Header/navigation surfaces | Status and feedback | Dark mode rules | What changes per vertical — and what does not | Changes (vertical-specific, lives in `src/theme/tokens/brand.css`) | Does NOT change (shared, lives in core/header/status/swatch/components) | Tailwind utility bridge | Troubleshooting Reference | Token not found in Tailwind utilities | Colors look wrong in dark mode | Vertical changes leak into other verticals | Component already exists | Local pages won't render without SCAPI | Linter errors after changes | Snapshot tests fail after visual changes | Create a Component Skill | Before you start — scan first (extend before create) | Step 1 — Decide the layer | Step 2 — Create the file with the copyright header | Step 3 — Type the props explicitly | Step 4 — Define CVA variants (if the component has visual states) | Step 5 — Write the component | Step 6 — Create the Storybook story | Step 7 — Accessibility check | Verification | Related Skills | Reference Documentation",
+      "files": [
+        {
+          "path": "references/COMPONENT-AUTHORING.md",
+          "bytes": 8647
+        },
+        {
+          "path": "references/PROJECT-STRUCTURE.md",
+          "bytes": 1652
+        },
+        {
+          "path": "references/TOKEN-SYSTEM.md",
+          "bytes": 5525
+        },
+        {
+          "path": "references/TROUBLESHOOTING.md",
+          "bytes": 1914
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 7651
+        }
+      ]
+    },
+    {
+      "id": "storefront-next/sfnext-create-vertical",
+      "collection": "storefront-next",
+      "title": "sfnext-create-vertical",
+      "description": "Create a new Storefront Next vertical (brand theme / storefront variant) by editing brand design tokens, typography, dark mode, and the Figma kit. Use when asked to create a new vertical, brand, theme, or storefront variant, re-skin the storefront, or change the brand palette. Covers the brand.css token layer, semantic token rules, fixture-based local development, and the extension-vs-base decision. NOT for engineering component patterns — see sfnext-components.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/storefront-next/skills/sfnext-create-vertical/SKILL.md",
+      "headings": "Component authoring standards | Vertical extensions — existing components always have priority | Decision gate (run this before creating any extension component) | Concrete examples | Extend before create — mandatory check before any new component | Multi-vertical extension governance | Layer model — know which layer you are in before writing a line | Primitives (`src/components/ui/`) | CVA — class-variance-authority | data-slot attributes | TypeScript requirements | Copyright header | Naming conventions | Storybook requirement | Accessibility checklist | Project Structure Reference | Key architecture | Theme file layout (the vertical surface) | App file organization | Common commands | Token System Reference | The one rule that overrides everything else | Token files and what they own | Semantic token meanings — use the right one | Text colors | Background colors | Borders | Header/navigation surfaces | Status and feedback | Dark mode rules | What changes per vertical — and what does not | Changes (vertical-specific, lives in `src/theme/tokens/brand.css`) | Does NOT change (shared, lives in core/header/status/swatch/components) | Tailwind utility bridge | Troubleshooting Reference | Token not found in Tailwind utilities | Colors look wrong in dark mode | Vertical changes leak into other verticals | Component already exists | Local pages won't render without SCAPI | Linter errors after changes | Snapshot tests fail after visual changes | Create a Vertical Skill | What a vertical is — and is not | Before you start — read the token layer first | Workflow | 1. Establish the brand palette | 2. Add optional typography overrides | 3. Keep local development stable with fixtures | 4. Run the component extension audit before coding | 5. Validate | 6. Sync the Figma kit | Execution modes | Required outcomes | Verification | Related Skills | Reference Documentation",
+      "files": [
+        {
+          "path": "references/COMPONENT-AUTHORING.md",
+          "bytes": 8647
+        },
+        {
+          "path": "references/PROJECT-STRUCTURE.md",
+          "bytes": 1652
+        },
+        {
+          "path": "references/TOKEN-SYSTEM.md",
+          "bytes": 5525
+        },
+        {
+          "path": "references/TROUBLESHOOTING.md",
+          "bytes": 1914
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 6608
+        }
+      ]
+    },
+    {
+      "id": "storefront-next/sfnext-custom-apis",
+      "collection": "storefront-next",
+      "title": "sfnext-custom-apis",
+      "description": "End-to-end workflow for consuming custom SCAPI endpoints from a Storefront Next project — adding them as typed clients via `b2c sfnext scapi add custom`, discovering their schema, and calling them from loaders/actions/useScapiFetcher. Use this skill whenever the user wants to call a custom API from their Storefront Next app, gets a 404 or 401 when calling a custom endpoint from their sfnext loader, needs to add a custom API as a typed client in their storefront, asks about the full workflow from custom API cartridge to sfnext consumption, or says 'custom API in storefront next'. Also use when they ask how createApiClients exposes custom API methods or how to use useScapiFetcher with a custom endpoint. NOT for writing the custom API cartridge files (schema.yaml/script.js) from scratch — see b2c:b2c-custom-api-development. NOT for just checking registration status — see b2c-cli:b2c-scapi-custom.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/storefront-next/skills/sfnext-custom-apis/SKILL.md",
+      "headings": "Workflow Examples | Example 1: Shopper Custom API — Loyalty Points | Cartridge Structure | schema.yaml | api.json | Deploy and Register | Add to Storefront Next Project | Discover and Use | Storefront Code | Example 2: Admin Custom API — Inventory Check | Key Differences from Shopper APIs | api.json | Usage in Storefront Context | Example 3: useScapiFetcher with Custom API | How It Works | Custom APIs in Storefront Next | Overview | End-to-End Workflow | Step 1: Create the Custom API | Step 2: Deploy and Register | Step 3: Add as Typed Client | Step 4: Discover the API Shape | Step 5: Call from Loaders and Actions | Calling from a Loader (Shopper API) | Calling from an Action (Mutation) | Using useScapiFetcher (Interactive) | Step 6: Debug Issues | Custom API Client Naming | Shopper vs Admin Custom APIs | Common Pitfalls | Related Skills | Reference Documentation",
+      "files": [
+        {
+          "path": "references/WORKFLOW-EXAMPLES.md",
+          "bytes": 7317
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 8439
+        }
+      ]
+    },
+    {
+      "id": "storefront-next/sfnext-data-fetching",
+      "collection": "storefront-next",
+      "title": "sfnext-data-fetching",
+      "description": "Implement server-side data fetching in Storefront Next using loaders, actions, and useScapiFetcher. Use when writing loader functions, making SCAPI calls, handling form submissions, or implementing interactive data fetching. Covers synchronous loaders, streaming patterns, createApiClients, and parallel requests. NOT for client-side Zustand state — see sfnext-state-management.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/storefront-next/skills/sfnext-data-fetching/SKILL.md",
+      "headings": "Loader Patterns Reference | Data Flow | Initial Page Load (SSR) | Subsequent Navigation (SPA) | Decision Tree: Which Pattern to Use | Pattern: Multiple API Calls with Dependencies | Pattern: Conditional Data Loading | SCAPI Fetcher Reference | How useScapiFetcher Works | API | loader vs useScapiFetcher | Timeline Comparison | Complete Example: Search Suggestions | Data Fetching Skill | Overview | Loader Patterns | When to Use Each Pattern | Action Functions | useScapiFetcher — Interactive Data Fetching | API Client Usage | Parallel vs Sequential Requests | Common Pitfalls | Related Skills | Reference Documentation",
+      "files": [
+        {
+          "path": "references/LOADER-PATTERNS.md",
+          "bytes": 2807
+        },
+        {
+          "path": "references/SCAPI-FETCHER.md",
+          "bytes": 2527
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 7497
+        }
+      ]
+    },
+    {
+      "id": "storefront-next/sfnext-deployment",
+      "collection": "storefront-next",
+      "title": "sfnext-deployment",
+      "description": "Build and deploy Storefront Next storefronts to Managed Runtime (MRT) using the sfnext CLI. Use when running production builds, pushing bundles to MRT with sfnext push, configuring deployment environments, or deploying Page Designer cartridges. This is for Storefront Next deployment — for general MRT management via b2c CLI, see b2c-cli:b2c-mrt.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/storefront-next/skills/sfnext-deployment/SKILL.md",
+      "headings": "MRT Deployment Reference | Managed Runtime (MRT) | Deployment Commands | Environment Variables on MRT | Setting Variables | Variable Limits | Production Configuration Example | Bundle Management | Rollback | Multi-Environment Setup | Deployment Verification | Deployment Skill | Overview | Production Build | Deploying to MRT | Using the Template's Push Script | Deployment Flow | Environment Configuration | MRT Deployment Variables | Application Variables (set in MRT Dashboard) | Page Designer Cartridge Deployment | Pre-Deployment Checklist | Troubleshooting | Related Skills | Reference Documentation",
+      "files": [
+        {
+          "path": "references/MRT-DEPLOYMENT.md",
+          "bytes": 3289
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 5611
+        }
+      ]
+    },
+    {
+      "id": "storefront-next/sfnext-extensions",
+      "collection": "storefront-next",
+      "title": "sfnext-extensions",
+      "description": "Build extensions for Storefront Next using target-config.json, target points, extension routes, and translation namespaces. Use when creating modular features, inserting components into UI targets, adding extension routes, adding a section to an existing page, or using SFDC_EXT_ integration markers. Covers the base-audit decision gate (deciding whether to extend at all vs token/variant override), extension structure, targetId configuration, and extension registration in src/extensions/config.json.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/storefront-next/skills/sfnext-extensions/SKILL.md",
+      "headings": "Base Audit Reference | The gate, step by step | Worked examples | Example 1 — duplicate section (wrong) vs additive section (right) | Example 2 — restyle, don't re-render | Example 3 — pick the right layer | Finding the slots and base render points | Extension Examples Reference | Store Locator Extension | target-config.json | Route | Translations | Integration Marker Patterns | Single-Line Import | Block Integration | BOPIS Extension (Buy Online, Pick Up In Store) | Extensions Skill | Overview | Before You Build — Audit the Base First (Decision Gate) | Extension Structure | Target Configuration | Target Points | Extension Routes | Extension Translations | Integration Markers | Best Practices | Related Skills | Reference Documentation",
+      "files": [
+        {
+          "path": "references/BASE-AUDIT.md",
+          "bytes": 3183
+        },
+        {
+          "path": "references/EXTENSION-EXAMPLES.md",
+          "bytes": 2670
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 5708
+        }
+      ]
+    },
+    {
+      "id": "storefront-next/sfnext-hybrid-storefronts",
+      "collection": "storefront-next",
+      "title": "sfnext-hybrid-storefronts",
+      "description": "Implement hybrid storefronts that run Storefront Next alongside SFRA or SiteGenesis. Use when planning gradual migration from SFRA, configuring hybrid proxy for local development, setting up session bridging between storefronts, or routing traffic between old and new implementations.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/storefront-next/skills/sfnext-hybrid-storefronts/SKILL.md",
+      "headings": "Hybrid Proxy Configuration Reference | Overview | Environment Variables | All Environments | Local Development Only | Routing Rules Format | Required Patterns | Automatically Excluded Paths (never proxied) | Path Transformation | Cookie Handling (Local Dev) | Custom Route Matching | CDN Routing (Production) | Shared Cookie Requirements | Hybrid Storefronts Skill | Overview | Architecture | Configuration | Application Config (All Environments) | Proxy Plugin Config (Local Development Only) | Client-Side Navigation Middleware | Session Bridging | Cookie Handling (Local Dev) | SFRA to Storefront Next | Storefront Next to SFRA | Traffic Routing Patterns | Gradual Migration Strategy | Required Routing Rules | Keep Rules in Sync | Common Considerations | Troubleshooting | Related Skills",
+      "files": [
+        {
+          "path": "references/HYBRID-PROXY-CONFIG.md",
+          "bytes": 4619
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 6744
+        }
+      ]
+    },
+    {
+      "id": "storefront-next/sfnext-i18n",
+      "collection": "storefront-next",
+      "title": "sfnext-i18n",
+      "description": "Implement internationalization in Storefront Next using i18next with useTranslation for components and getTranslation for server-side code. Use when adding translations, configuring locales, handling pluralization, using the Zod schema factory pattern, or managing extension translations. Covers namespaces, interpolation, and language switching.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/storefront-next/skills/sfnext-i18n/SKILL.md",
+      "headings": "Internationalization (i18n) Skill | Overview | Translation File Structure | Namespace structure in `translations.json` | Separate namespace file (`product.json`) | Usage in Components | Usage in Server Code | Validation Schemas — Factory Pattern | Language Switching | Extension Translations | Common Pitfalls | Related Skills",
+      "files": [
+        {
+          "path": "SKILL.md",
+          "bytes": 5328
+        }
+      ]
+    },
+    {
+      "id": "storefront-next/sfnext-page-designer",
+      "collection": "storefront-next",
+      "title": "sfnext-page-designer",
+      "description": "Integrate Page Designer with Storefront Next using React decorators, component registry, and Region rendering. Use when creating merchant-editable pages, adding Page Designer components with @Component/@AttributeDefinition decorators, using fetchPageFromLoader, or rendering Regions. This is for the React/Storefront Next implementation — for classic ISML Page Designer, see b2c:b2c-page-designer.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/storefront-next/skills/sfnext-page-designer/SKILL.md",
+      "headings": "Component Registry Reference | Overview | Static Registry | Component Registration | Component Loaders | Data Flow | Adding a New Page Designer Component | Decorator Patterns Reference | @Component Decorator | @AttributeDefinition Decorator | Attribute Types | Type Inference by MCP Tool | @RegionDefinition Decorator | @PageType Decorator | Complete Component Example | Page Designer Skill | Overview | Which Pages Use Page Designer | Route Setup | In the Loader | In the Layout | Component Setup | Metadata Class with Decorators | React Component | Components with Server Data | Design Mode | MCP Tools | Typical Workflow | Best Practices | Related Skills | Reference Documentation",
+      "files": [
+        {
+          "path": "references/COMPONENT-REGISTRY.md",
+          "bytes": 2514
+        },
+        {
+          "path": "references/DECORATOR-PATTERNS.md",
+          "bytes": 4638
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 6108
+        }
+      ]
+    },
+    {
+      "id": "storefront-next/sfnext-performance",
+      "collection": "storefront-next",
+      "title": "sfnext-performance",
+      "description": "Optimize Storefront Next performance with bundle size limits, DynamicImage component, Lighthouse audits, and progressive streaming. Use when checking bundle sizes, optimizing images, improving page load speed, or configuring performance metrics. Covers parallel data fetching, image optimization, and performance monitoring.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/storefront-next/skills/sfnext-performance/SKILL.md",
+      "headings": "Performance Skill | Bundle Size Limits | Built-in Metrics | Parallel Data Fetching | Image Optimization | Image Best Practices | Progressive Streaming | Lighthouse Optimization | Troubleshooting | Related Skills",
+      "files": [
+        {
+          "path": "SKILL.md",
+          "bytes": 4039
+        }
+      ]
+    },
+    {
+      "id": "storefront-next/sfnext-project-setup",
+      "collection": "storefront-next",
+      "title": "sfnext-project-setup",
+      "description": "Create and configure Storefront Next projects. Use when creating a new storefront, understanding project structure, setting up environment variables, or running the sfnext CLI for the first time. Covers project creation, directory layout, .env configuration, and sfnext CLI basics.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/storefront-next/skills/sfnext-project-setup/SKILL.md",
+      "headings": "Environment Variables Reference | Naming Convention | Rules | Required Variables | Server-Only Variables | Multi-Site Configuration | Setting Complex Values | Security Guidelines | Project Structure Reference | Top-Level Files | Source Directory (`src/`) | `src/routes/` | `src/components/` | `src/config/` | `src/lib/` | `src/locales/` | `src/middlewares/` | `src/extensions/` | `src/test-utils/` | Build Output | Cartridges | Project Setup Skill | Overview | Creating a Project | Via Business Manager (instance-connected storefront) | Via CLI (local exploration) | Project Structure | Environment Setup | Required Variables | Development Commands | Non-Negotiable Rules | Troubleshooting | Related Skills | Reference Documentation",
+      "files": [
+        {
+          "path": "references/ENV-VARIABLES.md",
+          "bytes": 2749
+        },
+        {
+          "path": "references/PROJECT-STRUCTURE.md",
+          "bytes": 4013
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 7445
+        }
+      ]
+    },
+    {
+      "id": "storefront-next/sfnext-routing",
+      "collection": "storefront-next",
+      "title": "sfnext-routing",
+      "description": "Implement file-based routing in Storefront Next with React Router 7. Use when adding new pages, creating layout routes, defining route parameters, or understanding route module exports (loader, action, component, meta). Covers flat-routes conventions, nested layouts, and the _app prefix.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/storefront-next/skills/sfnext-routing/SKILL.md",
+      "headings": "Route Conventions Reference | Flat Routes File Naming | Syntax Reference | Common Route Patterns | Layout Nesting | Route Module Exports | Important Notes | Routing Skill | Overview | Route File Conventions | File Name to URL Mapping | Naming Rules | Route Module Exports | loader — Server-side data loading | action — Handle mutations (form submissions) | default — Page component | Layout Routes | Adding a New Page | Resource Routes | Related Skills | Reference Documentation",
+      "files": [
+        {
+          "path": "references/ROUTE-CONVENTIONS.md",
+          "bytes": 2750
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 5850
+        }
+      ]
+    },
+    {
+      "id": "storefront-next/sfnext-scapi-management",
+      "collection": "storefront-next",
+      "title": "sfnext-scapi-management",
+      "description": "Add, remove, and list typed SCAPI clients in a Storefront Next project using `b2c sfnext scapi` commands, and browse API schemas to discover endpoints before writing loaders. Use this skill whenever the user says 'sfnext scapi', 'add an API to my storefront next project', 'what SCAPI clients does my sfnext project have', 'remove an API client', 'list available APIs for sfnext', 'browse schema before writing a loader', or asks how to integrate a specific SCAPI (shopper-baskets, shopper-search, etc.) into their Storefront Next project as a typed client. Also use when they want to check what parameters an endpoint accepts before coding. NOT for making actual SCAPI calls from loaders — see sfnext-data-fetching. NOT for standalone schema browsing outside a Storefront Next project — see b2c-cli:b2c-scapi-schemas.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/storefront-next/skills/sfnext-scapi-management/SKILL.md",
+      "headings": "CLI Commands Reference | How It Works | `b2c sfnext scapi available` | `b2c sfnext scapi add` | `b2c sfnext scapi list` | `b2c sfnext scapi remove` | Complementary: `b2c scapi schemas` | SCAPI Client Management Skill | Overview | Managing Project Clients | List Available APIs | Add a Client | List Current Project Clients | Remove a Client | Discovering API Shapes | The Schema-First Workflow | Step 1: Find the API | Step 2: See Available Endpoints | Step 3: Expand Endpoint Details | Step 4: Write Your Loader | Example: Adding and Using a New API | Common Pitfalls | Related Skills | Reference Documentation",
+      "files": [
+        {
+          "path": "references/CLI-COMMANDS.md",
+          "bytes": 4184
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 6818
+        }
+      ]
+    },
+    {
+      "id": "storefront-next/sfnext-state-management",
+      "collection": "storefront-next",
+      "title": "sfnext-state-management",
+      "description": "Manage client-side state in Storefront Next using React context providers and feature-level Zustand stores. Use when handling basket/auth UI state, creating extension stores (for example store locator), or syncing client-visible state after server mutations. NOT for server-side data loading — see sfnext-data-fetching for loader patterns.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/storefront-next/skills/sfnext-state-management/SKILL.md",
+      "headings": "State Management Skill | Overview | Zustand Store Pattern (Feature-Level) | Context Integration | Post-Mutation Sync Pattern | Best Practices | When to Use Each Mechanism | Related Skills",
+      "files": [
+        {
+          "path": "SKILL.md",
+          "bytes": 5079
+        }
+      ]
+    },
+    {
+      "id": "storefront-next/sfnext-testing",
+      "collection": "storefront-next",
+      "title": "sfnext-testing",
+      "description": "Write tests for Storefront Next using Vitest unit tests, Storybook stories, interaction tests, snapshot tests, and accessibility tests. Use when writing component tests, creating Storybook stories, running test coverage, or setting up test utilities. Covers testing-library patterns, play functions, and coverage thresholds.",
+      "entrypoint": "SKILL.md",
+      "source": "skills/storefront-next/skills/sfnext-testing/SKILL.md",
+      "headings": "Storybook Patterns Reference | Story File Structure | Story Variants | Interaction Tests (Play Functions) | Decorators | Responsive Testing | Accessibility Testing | Story Coverage | Testing Skill | Unit Tests (Vitest) | Test Utilities | Running Tests | Coverage Requirements | Testing Libraries | Storybook | Story Structure | Storybook Commands | Story Tags | Route Testing | Test Organization | Best Practices | Related Skills | Reference Documentation",
+      "files": [
+        {
+          "path": "references/STORYBOOK-PATTERNS.md",
+          "bytes": 3059
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 6088
+        }
+      ]
+    },
+    {
+      "id": "mcp/b2c-config",
+      "collection": "mcp",
+      "title": "b2c-config",
+      "description": "MCP configuration, authentication setup, external access grants, and masked inspection. Use for setup or unresolved configuration issues; routine config_inspect needs no skill read.",
+      "entrypoint": "SKILL.md",
+      "source": "guidance/mcp/b2c-config/SKILL.md",
+      "headings": "MCP Configuration | Inspect resolved values | Where configuration comes from | Setup and access | CLI, when requested | Further reading",
+      "files": [
+        {
+          "path": "SKILL.md",
+          "bytes": 5153
+        }
+      ],
+      "featured": true
+    },
+    {
+      "id": "mcp/cip",
+      "collection": "mcp",
+      "title": "MCP CIP Analytics",
+      "description": "Discover and run CIP reports or analytics SQL for sales, merchandising, and technical operations. Resolve warehouse access, bound results, and interpret site/date scope.",
+      "entrypoint": "SKILL.md",
+      "source": "guidance/mcp/cip/SKILL.md",
+      "headings": "CIP analytics | Choose and discover | Configuration and access | Query and interpret",
+      "files": [
+        {
+          "path": "SKILL.md",
+          "bytes": 5633
+        }
+      ],
+      "featured": true
+    },
+    {
+      "id": "mcp/debugger",
+      "collection": "mcp",
+      "title": "MCP Debugger Usage",
+      "description": "Bounded debugger capture, request triggering, state inspection, and reliable session cleanup.",
+      "entrypoint": "SKILL.md",
+      "source": "guidance/mcp/debugger/SKILL.md",
+      "headings": "MCP Debugger Usage | Prerequisites | Capture and cleanup | Stepping | Recovery | CLI or IDE, when requested",
+      "files": [
+        {
+          "path": "SKILL.md",
+          "bytes": 4098
+        }
+      ],
+      "featured": true
+    },
+    {
+      "id": "mcp/scapi",
+      "collection": "mcp",
+      "title": "MCP SCAPI Code Mode",
+      "description": "Discover standard and live custom SCAPI contracts, compose Admin requests, and verify changes using configured authentication and safety rules.",
+      "entrypoint": "SKILL.md",
+      "source": "guidance/mcp/scapi/SKILL.md",
+      "headings": "Custom Admin APIs | Live custom property definitions | Job review and investigation | Basic product creation | Join campaign assignments to promotions | Save a reusable workflow | Built-in SCAPI snippets | builtin/create-product | builtin/campaign-promotions | builtin/failed-job-triage | builtin/job-execution-review | builtin/job-execution-inspect | builtin/code-version-inspect | builtin/site-cartridge-inspect | Token exports for external clients | Account Manager | SLAS | Output and failures | SCAPI Code Mode | Discover | Task map | Tenant custom properties and APIs | Authentication | Compose and verify | Reusable workflows",
+      "files": [
+        {
+          "path": "references/custom-apis.md",
+          "bytes": 2716
+        },
+        {
+          "path": "references/custom-properties.md",
+          "bytes": 1845
+        },
+        {
+          "path": "references/jobs.md",
+          "bytes": 1873
+        },
+        {
+          "path": "references/products.md",
+          "bytes": 2355
+        },
+        {
+          "path": "references/promotions.md",
+          "bytes": 1065
+        },
+        {
+          "path": "references/saving.md",
+          "bytes": 739
+        },
+        {
+          "path": "references/snippets.md",
+          "bytes": 3745
+        },
+        {
+          "path": "references/tokens.md",
+          "bytes": 2753
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 9669
+        }
+      ],
+      "featured": true
+    },
+    {
+      "id": "mcp/server",
+      "collection": "mcp",
+      "title": "server",
+      "description": "B2C MCP setup, toolset customization, available capabilities, tool choice, and skill discovery.",
+      "entrypoint": "SKILL.md",
+      "source": "guidance/mcp/server/SKILL.md",
+      "headings": "Instance files and cartridge uploads | B2C MCP Server | Server configuration and tool availability | Tool choice and project configuration | Skills | Setup references",
+      "files": [
+        {
+          "path": "references/files.md",
+          "bytes": 2373
+        },
+        {
+          "path": "SKILL.md",
+          "bytes": 5965
+        }
+      ],
+      "featured": true
+    }
+  ]
+}