agentmods.dev

sfnext-components

sfnext-components is a skill for Claude Code from SalesforceCommerceCloud/b2c-developer-tooling. It costs 190 tokens per session (2,575 once invoked), scanned A, original, Apache-2.0.

A set of coding patterns for building Storefront Next user-interface components with React, shadcn/ui, and Tailwind CSS. It covers page components, loading states, styling, and choosing server or browser rendering.

In plain words
What is it for?
Use it when creating page components, showing placeholders while data loads, adding shadcn/ui components, or styling with Tailwind CSS.
Why use it?
It gives developers a consistent way to build pages that load data progressively and remain organized as the storefront grows.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths; mentions AGENTS.md.

Part of the storefront-next plugin — 24 skills shipped together

not rated 56repo changed 15d ago A scan SkillSpector: warn 190 tokens original Apache-2.0

Good fit Use it when creating page components, showing placeholders while data loads, adding shadcn/ui components, or styling with Tailwind CSS.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/salesforcecommercecloud/b2c-developer-tooling/sfnext-components
View source ↗ SalesforceCommerceCloud/b2c-developer-tooling salesforcecommercecloud.github.io
Install

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.

Any agent
npx skills add SalesforceCommerceCloud/b2c-developer-tooling --skill sfnext-components
Clone the repo
git clone --depth 1 https://github.com/SalesforceCommerceCloud/b2c-developer-tooling

Made for: Claude Code.

Or install storefront-next, the plugin that ships this one along with the rest of its 24 skills.

Wrote 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.

agentmods badge for sfnext-components

README.md
[![agentmods](https://agentmods.dev/badge/skills/salesforcecommercecloud/b2c-developer-tooling/sfnext-components/github.svg)](https://agentmods.dev/skills/salesforcecommercecloud/b2c-developer-tooling/sfnext-components)
Your own site
<a href="https://agentmods.dev/skills/salesforcecommercecloud/b2c-developer-tooling/sfnext-components"><img src="https://agentmods.dev/badge/skills/salesforcecommercecloud/b2c-developer-tooling/sfnext-components/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.

agentmods 80×15 button for sfnext-components

Your own site · 80×15
<a href="https://agentmods.dev/skills/salesforcecommercecloud/b2c-developer-tooling/sfnext-components"><img src="https://agentmods.dev/badge/skills/salesforcecommercecloud/b2c-developer-tooling/sfnext-components.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 190 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,575 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 3 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium MCP Rug Pull · line 92
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 93
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 94
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00190 $0.02575
Opus 5.5 $0.00076 $0.01030
Sonnet 5.5 $0.00038 $0.00515
Haiku 4.5 $0.00019 $0.00258

Measured 15d ago against content hash 3e0cd247f46e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

sfnext-components 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 15d 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.

skills/storefront-next/skills/sfnext-components/SKILL.md · 154 lines

How it starts

The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Storefront Next Components

How to write, style, and verify components in your storefront. Your project already ships the rules in AGENTS.md, docs/README-UI-STYLING.md, docs/README-SHAPE-TOKENS.md, docs/README-SUSPENSE.md, and docs/README-STORYBOOK.md; this skill is the task-oriented path through them.

Before you create anything

  1. Search src/components/ for an existing component (ls src/components). Extend or compose it before adding a new one.
  2. Decide the layer:
    • Primitive (Button, Card, Dialog): a shadcn fork in src/components/ui/. Only shadcn forks live there.
    • Composite / domain component: everything else, in src/components/<kebab-name>/.
    • Optional feature: a folder under src/extensions/ (see storefront-next:sfnext-extensions).
  3. Match the folder shape already used by neighbors:
src/components/my-widget/
├── index.tsx                   # implementation (default or named export)
├── index.test.tsx              # Vitest + Testing Library
└── stories/
    ├── index.stories.tsx       # Storybook (stories/ subfolder is required)
    ├── my-widget-snapshot.tsx  # optional snapshot fixture
    └── __snapshots__/          # generated baselines, commit them

Every .ts/.tsx file needs the Apache header enforced by the custom/header-format lint rule. Copy it from any existing file (or AGENTS.md).

Styling rules

  • Tailwind utility classes only; merge with cn() from @/lib/utils. No CSS modules, no per-component CSS files, no style={{}} (a truly dynamic API-driven value is the only exception).
  • Global/theme CSS lives in src/theme/ only (entry src/theme/index.css). There is no src/app.css.
  • Use semantic token classes, never hard-coded colors. The custom/color-linter rule fails pnpm lint on raw palette classes such as text-white or bg-red-500; use text-primary-foreground, text-destructive-foreground, bg-card, text-muted-foreground, border-border.
  • Header/footer chrome has its own classes: bg-header-background, text-header-foreground, bg-header-menu-background, bg-footer-background. Do not write bg-[--header-background].
  • A new token needs two edits: the value in src/theme/tokens/*.css and a --color-x: var(--x) line inside @theme inline in src/theme/tailwind.css. See TOKEN-SYSTEM.md.
  • The shipped theme defines one (light) palette; there is no .dark token block. Do not promise dark mode in component work.
  • Breakpoints are mobile-first (sm, md, lg, xl, 2xl).

Read the full file on GitHub · 154 lines

Files

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.

Changes

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.

  1. 15d ago Changed · -38 lines · +116 tokens per session 3e0cd247f46e
  2. 1mo ago First seen · 192 lines · 74 tokens per session scan A ec1ac9e84e1b

Subscribe to this mod's changes

sfnext-components is a skill published in the GitHub repository SalesforceCommerceCloud/b2c-developer-tooling (56 stars, last pushed today), licensed Apache-2.0. It adds 190 tokens to every session and 2,575 once invoked, about $0.0008 per session on Opus 5.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-08-30.

CSS and stylingFrontendReactb2cclidx
Related

Other skills, from other repositories

od-react-export

Use this plugin when the user wants to hand an accepted Open Design artifact to a React app.

wolfenazz/YzPzCode · 0 tokens

artifacts-builder

Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.

bobmatnyc/claude-mpm · 63 tokens

style-modus-components-with-tailwind

Style Modus components using custom border and opacity utilities that work with CSS variables, avoiding Tailwind patterns that don't work with runtime CSS variables.

julianoczkowski/create-trimble-app · 35 tokens

react-shadcn

Builds UI components for a React SPA (Vite) with shadcn/ui (CLI 4.21.0) and Tailwind CSS v4 on whichever component base the project uses — Base UI (default for new projects since July 2026), Radix UI (unified radix-ui package, fully supported) or React Aria (added July 2026): forms (Field/FieldLabel/FieldError pattern…

fusengine/codex · 35 tokens

heroui

Build accessible UIs using HeroUI v3 components (React + Tailwind CSS v4 + React Aria). Use when creating React interfaces, selecting UI components, implementing forms, navigation, overlays, or data display. Use when installing HeroUI v3, customizing themes, accessing component documentation, building with compound…

ruchernchong/claude-kit · 121 tokens

artifacts-builder

Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui).

wolfenazz/YzPzCode · 35 tokens