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/rayfernando1337/llm-cursor-rules/tailwind-v4git clone --depth 1 https://github.com/RayFernando1337/llm-cursor-rulesWrote 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/rayfernando1337/llm-cursor-rules/tailwind-v4)<a href="https://agentmods.dev/rules/rayfernando1337/llm-cursor-rules/tailwind-v4"><img src="https://agentmods.dev/badge/rules/rayfernando1337/llm-cursor-rules/tailwind-v4.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.00768 |
| Opus 5 | $0.00000 | $0.00384 |
| Sonnet 5 | $0.00000 | $0.00154 |
| Haiku 4.5 | $0.00000 | $0.00077 |
Grade A, and why
Tailwind-v4 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 3d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
General Guidelines
- Use Tailwind utility classes for consistent styling, with custom CSS only for special cases
- Organize classes logically (layout, spacing, color, typography)
- Use responsive and state variants (e.g., sm:, md:, lg:, hover:, focus:, dark:) in markup
- Embrace Tailwind v4 features like container queries and CSS variables
- Keep
tailwind.config.tsupdated with design tokens and purge paths - Rely on Tailwind classes rather than inline styles or external CSS files for a unified design language
Configuration (CSS Files)
- Use the
@themedirective to define custom design tokens like fonts, breakpoints, and colors - Prefer modern color formats such as
oklchfor better color gamut support, defining them in the:rootscope - Take advantage of automatic content detection, which eliminates the need for a
contentarray in configuration - Rely on Oxide engine to scan project files, excluding those in
.gitignoreand binary extensions - Add specific sources with
@sourceonly when necessary - Extend Tailwind with custom utilities using the
@utilitydirective in CSS files
Styling (CSS Files)
- Incorporate 3D transform utilities like
rotate-x-*,rotate-y-*, andscale-z-*for advanced visual effects - Implement container queries with
@container,@max-*, and@min-*utilities for adaptive layouts - Use arbitrary values and properties with square bracket notation (e.g.,
[mask-type:luminance]ortop-[117px]) - Apply modifiers like
hoverorlgwith arbitrary values for flexible styling - Use the
not-*variant for:not()pseudo-classes and thestartingvariant for@starting-style - Check browser support for advanced features like
@starting-styleusing resources like caniuse
Components (HTML)
- Apply Tailwind utility classes directly in HTML for styling components
- Use dynamic arbitrary values like
grid-cols-[1fr_500px_2fr]for flexible layouts - Implement data attribute variants like
data-current:opacity-100for conditional styling - Ensure accessibility by pairing Tailwind utilities with appropriate ARIA attributes
- Use
aria-hidden="true"orrole="presentation"when applying utilities likehiddenorsr-only
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.
- 3d ago First seen · 51 lines · 768 tokens per session scan A b56221763104
Tailwind-v4 is a cursor rule published in the GitHub repository RayFernando1337/llm-cursor-rules (888 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 768 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
css-styling
CSS architecture, tokens, and styling rules for this Docusaurus site. Apply when creating or modifying components, styles, layouts, or any UI-facing code.
frontend-web
Cursor rule "frontend-web" from groupultra/telegram-search, covering frontend (apps/web), routing, layouts & navigation, state & data fetching, ui, styling & ux and error handling & notifications.
codex-premium-website-skills
Apply Codex Skills standards to frontend, website, motion, accessibility, QA, agent reasoning, and handoff work.
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
frontend-architecture
Vite + React SPA architecture - directory layout, providers, bundle splitting. Tailwind styling in tailwind.mdc.
css-render-blocking-diagnosis
Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.