Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add BanibrataChatterjee/AwesomeSalesforceSkills --skill digital-storefront-requirementsgit clone --depth 1 https://github.com/BanibrataChatterjee/AwesomeSalesforceSkillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/digital-storefront-requirements)<a href="https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/digital-storefront-requirements"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/digital-storefront-requirements/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/digital-storefront-requirements"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/digital-storefront-requirements.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00095 | $0.03961 |
| Opus 5 | $0.00048 | $0.01980 |
| Sonnet 5 | $0.00019 | $0.00792 |
| Haiku 4.5 | $0.00010 | $0.00396 |
Grade A, and why
digital-storefront-requirements scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Digital Storefront Requirements
This skill activates when a practitioner is gathering, assessing, or implementing requirements for a Salesforce Commerce Cloud (B2C Commerce / SFCC) digital storefront — covering architecture selection, branding, content management, personalization, mobile experience, and accessibility compliance. It is strictly for the proprietary SFCC infrastructure and does not apply to Experience Cloud portals or LWR-based Digital Experiences.
Before Starting
Gather this context before working on anything in this domain:
- Confirm the target platform is B2C Commerce (SFCC), accessed via Business Manager at
*.commercecloud.salesforce.com. If the user mentions WebStore, Digital Experiences, LWR, or Lightning Community, stop and route to the appropriate Experience Cloud skill. - Identify whether the merchant is on SFRA (existing implementation) or is evaluating a new build — new builds should default to PWA Kit / Composable Storefront per Salesforce's current architectural guidance.
- Clarify the accessibility compliance target explicitly. Merchants often assume SFRA provides WCAG 2.1 AA compliance by default because it ships with Bootstrap 4. It does not. Accessibility compliance is the merchant's legal responsibility and requires a dedicated audit and remediation effort.
- Determine whether branding changes are cosmetic (CSS/fonts/colors) or structural (template overrides). Structural changes require overlay cartridges and cannot be applied inside
app_storefront_base.
Core Concepts
SFRA vs. PWA Kit: Two Distinct Architectures
Salesforce B2C Commerce offers two primary storefront reference architectures:
SFRA (Storefront Reference Architecture):
- Server-side rendered, Bootstrap 4 base, cartridge-based extensibility
- Suitable for merchants with existing SFRA investments or teams without React expertise
- Customized exclusively through overlay cartridges positioned left of
app_storefront_basein the cartridge path - Page Designer and content slots are the primary CMS tools
- Mobile experience is responsive web (Bootstrap 4 grid) — no PWA installability by default
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 248 lines · 95 tokens per session scan A e9e103c45533
digital-storefront-requirements is a skill published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (3 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 95 tokens to every session and 3,961 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
b2c-commerce-store-setup
Use when configuring or troubleshooting a Salesforce B2C Commerce (SFCC) storefront — including Business Manager site creation, SFRA cartridge path setup, customer groups, search index rebuilding, and key quota limits. Trigger keywords: SFCC, Commerce Cloud, Business Manager, storefront, cartridge, SFRA, site…
conversion-forms-checkout-polish
Polish conversion journeys and visible states.
Color Palette Generator
Create beautiful, accessible color schemes for any project.
mega-menu-builder
Build a rich navigation mega menu with product images, category highlights, featured banners, and keyboard-accessible dropdowns for large catalogs.
recently-viewed-products
Show shoppers the products they recently browsed using browser storage so they can easily pick up where they left off on your store.
accessibility
Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".