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-ui-primitivesgit clone --depth 1 https://github.com/dmenchaca/webflow-to-reactWhat 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.00735 |
| Opus 5 | $0.00000 | $0.00367 |
| Sonnet 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 2d 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.
- 2d 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 (27 stars, last pushed 2mo 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.
chakra-ui
This guide provides opinionated, actionable best practices for using Chakra UI effectively, focusing on token-first theming, responsive design, component architecture, and performance for React 18+ applications.
react-floating-ui
React 19 + Floating UI 0.27 conventions and pitfalls for floating/anchored components (tooltips, popovers, context menus, dialogs, selects).
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
cursorrules
this is a simple react and vite project that allows users to manage a JSON file on their computer with a nice UI.
nextjs
Next.js 16 App Router Standards & Constraints.