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 agentmods add rules/dmenchaca/webflow-to-react/react-sot-storybook-paritygit clone --depth 1 https://github.com/dmenchaca/webflow-to-reactWrote 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/rules/dmenchaca/webflow-to-react/react-sot-storybook-parity)<a href="https://agentmods.dev/rules/dmenchaca/webflow-to-react/react-sot-storybook-parity"><img src="https://agentmods.dev/badge/rules/dmenchaca/webflow-to-react/react-sot-storybook-parity.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.01562 |
| Opus 5 | $0.00000 | $0.00781 |
| Sonnet 5 | $0.00000 | $0.00312 |
| Haiku 4.5 | $0.00000 | $0.00156 |
Grade A, and why
react-sot-storybook-parity 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 5d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SOT components — Storybook must match production
When a migration introduces reusable section components or UI primitives (buttons, headings, chips) with co-located CSS and Storybook stories, the story is the contract. A route that mounts the same component with the same props must look the same — without extra route CSS or Storybook-only compensations on that component.
Two tiers: UI primitives (10g, Components/UI/*) and page sections (11a, Components/Page sections/*). See rules/react-sot-ui-primitives.mdc.
The failure mode (avoid this)
- Component ships a default look via co-located CSS + CSS custom properties.
- Storybook adds preview-only overrides (shorter canvas, decorator wrapper) that inflate tokens so the story “looks right.”
- Migration copies export HTML + per-route hooks instead of the SOT component.
- Someone hand-appends token overrides to a PurgeCSS extract or global embed file so the live page “matches” export.
- Result: Storybook, live route A, and live route B each show a different variant of the “same” component.
Ownership model (one visual concern → one owner)
| Concern | Owner | Route / page CSS |
|---|---|---|
| Component chrome (padding, borders, masks, video reveal, chip colors) | Variant class on the SOT root (e.g. --has-media, --theme-dark) + co-located or global-tier stylesheet |
Forbidden — no token overrides on SOT BEM roots |
| Page layout (grid, sidebar width, max-width on a child slot) | Route *-page.css or parent wrapper |
Allowed — layout only, not internal SOT classes |
| Webflow export residue | PurgeCSS / compiled bundle — read-only build output | Never hand-edit for React SOT fixes |
| Storybook frame compensation | Decorator scoped to .storybook-* (or your preview root) |
Only when the live surface is a different component or a different frame height — never inflate the SOT default the routes rely on |
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.
- 5d ago First seen · 93 lines · 0 tokens per session scan A 0aab3e80dabb
react-sot-storybook-parity is a cursor rule published in the GitHub repository dmenchaca/webflow-to-react (27 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,562 tokens. 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.
Other cursor rules, from other repositories
nextjs-react-tailwind-cursorrules-prompt-file
Cursor rules for Next.js development with React and Tailwind CSS integration.
react-components-creation-cursorrules-prompt-file
Cursor rules for React component creation and development.
react-chakra-ui-cursorrules-prompt-file
Cursor rules for React development with Chakra UI integration.
react-styled-components-cursorrules-prompt-file
Cursor rules for React development with Styled Components integration.
chakra-ui-best-practices
强制执行 Chakra UI 最佳实践以保持一致性并利用框架的功能.
react-chakra-ui---folder-structure
维护 React 和 Chakra UI 项目的定义文件夹结构以确保代码组织有序.