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.
git 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-ui-primitives)<a href="https://agentmods.dev/rules/dmenchaca/webflow-to-react/react-sot-ui-primitives"><img src="https://agentmods.dev/badge/rules/dmenchaca/webflow-to-react/react-sot-ui-primitives/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/rules/dmenchaca/webflow-to-react/react-sot-ui-primitives"><img src="https://agentmods.dev/badge/rules/dmenchaca/webflow-to-react/react-sot-ui-primitives.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.00000 | $0.00735 |
| Opus 5.5 | $0.00000 | $0.00294 |
| Sonnet 5.5 | $0.00000 | $0.00147 |
| Haiku 4.5 | $0.00000 | $0.00073 |
Grade A, and why
react-sot-ui-primitives 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 1mo 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI primitives — one SOT, variant stories (step 10g)
Webflow exports repeat the same UI chrome on every page: buttons, eyebrow chips, heading scales, icon slots. During migration, extract each pattern into one React component with Storybook variant stories — not per-route markup.
Two-tier SOT model
| Tier | Examples | Storybook folder | When |
|---|---|---|---|
| UI primitives (10g) | Button, Tagline, Heading, CopyableCodeBlock | Components/UI/… |
Before section SOT |
| Page sections (11a) | Hero, logo band, FAQ, CTA band | Components/Page sections/… |
Before routes (11) |
Sections compose primitives. Section CSS must not reimplement button borders, chip colors, or heading scales.
Audit signals (export)
| Pattern | Typical export classes |
|---|---|
| CTAs | .button, .w-button, .is-secondary, .is-icon |
| Eyebrows | mono uppercase bordered chips |
| Headings | .heading-style-h1 … h6, or repeated title classes |
| Code snippets | toolbar + monospace + copy |
Grep CSS and HTML before porting routes. One component per pattern.
Required pattern
// Components/UI/Button.tsx — one SOT
<Button variant="primary" theme="dark" href="/signup">Try it free</Button>
// Components/UI/Button.stories.tsx — variants, not routes
export const Primary: Story = { args: { variant: 'primary', children: 'Try it free' } }
export const Secondary: Story = { args: { variant: 'secondary', children: 'Talk to us' } }
Routes and page sections import Button — never:
// Forbidden on new work
<a href="…" className="button w-button is-secondary">…</a>
CSS ownership
- Primitive chrome (colors, padding, borders, font) → component CSS or global design-system entry.
- Forbidden: route
*-page.csstargeting.button,.w-button, or.ui-button__*internals. - Forbidden: different button markup per page when
ButtonSOT exists.
Storybook
- Install and wire preview in step 10f before 10g.
- Primitive stories use the same stylesheet tier as production.
- Name stories after variants (Primary, Secondary, On dark) — not after routes (Home CTA, Pricing CTA).
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.
- 1mo ago First seen · 70 lines · 0 tokens per session scan A b6b664ffd904
react-sot-ui-primitives is a cursor rule published in the GitHub repository dmenchaca/webflow-to-react (28 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 735 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
general
Wonder Blocks design system conventions, component patterns, and coding standards.
react-chakra-ui-cursorrules-prompt-file
Cursor rules for React development with Chakra UI integration.
ant-design
Definitive guidelines for building consistent, performant, and maintainable UIs with Ant Design v6.x, focusing on design tokens, layout, and component usage.
react-chakra-ui---folder-structure
A standard folder layout for React and Chakra UI projects, including separate locations for components, pages, themes, hooks, utilities, and assets. It also defines how Chakra UI theme files are grouped.
815-reactflow-diagrams
Conventions for narrative @xyflow/react canvases: custom nodes and edges, semantic stroke colors, Cloudflare orange shell grouping, readability inside tinted frames, handles, and verification before merge.
ui-design-system
UI, design tokens and mobile-first rules.