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/goranerhartic/cursor-development-rules/stylinggit clone --depth 1 https://github.com/GoranErhartic/cursor-development-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/goranerhartic/cursor-development-rules/styling)<a href="https://agentmods.dev/rules/goranerhartic/cursor-development-rules/styling"><img src="https://agentmods.dev/badge/rules/goranerhartic/cursor-development-rules/styling.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.00017 | $0.00395 |
| Opus 5 | $0.00009 | $0.00198 |
| Sonnet 5 | $0.00003 | $0.00079 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
styling 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 yesterday.
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.
What it actually says
Styling with Tailwind CSS
Setup
- Config:
tailwind.config.ts—content: [paths],theme.extendfor colors, fontFamily, spacing, etc.;darkMode: 'class'(or'media') - Global CSS:
@tailwind base; @tailwind components; @tailwind utilities;; use@layer basefor CSS variables (e.g. for theming) - cn(): Use
clsx+tailwind-merge(or similar) to merge class names and resolve Tailwind conflicts
Design Tokens
- Define in
theme.extend: colors (including semantic: primary, muted, destructive), fontFamily, spacing, borderRadius, boxShadow - Reference in classes:
bg-primary,text-muted-foreground,rounded-lg
Responsive
- Breakpoints:
sm:,md:,lg:,xl:,2xl:; mobile-first (base = mobile) - Use for layout (
md:grid-cols-2), visibility (hidden md:block), typography
Dark Mode
- With
darkMode: 'class': addclass="dark"to root (e.g.<html>); usedark:prefix:bg-white dark:bg-gray-900 - Prefer CSS variables in
@layer basefor theme colors so components usebg-background,text-foreground
Conventions
- Prefer Tailwind utilities over custom CSS; extract repeated patterns with
@applyin@layer componentssparingly; keep components using utility classes for consistency
Anti-Patterns
- Inline styles for layout/sizing; arbitrary values everywhere; inconsistent token usage
See also: components.mdc
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.
- yesterday First seen · 37 lines · 17 tokens per session scan A da59c1846ecb
styling is a cursor rule published in the GitHub repository GoranErhartic/cursor-development-rules (19 stars, last pushed 6mo ago), licensed MIT. It adds 17 tokens to every session and 395 once invoked, about $0.0001 per session on Opus 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-09-03.
Other cursor rules, from other repositories
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.
chakra-ui---theme-directory-rules
主题目录的特定规则，用于管理和自定义 Chakra UI 主题.
chakra-ui-best-practices
强制执行 Chakra UI 最佳实践以保持一致性并利用框架的功能.
chakra-ui---responsive-design
利用 Chakra UI 的布局组件在 React 应用程序中创建响应式设计.
creative-phase-uiux
UI/UX Design Guidelines and Process for the Creative Phase.
react-chakra-ui---folder-structure
维护 React 和 Chakra UI 项目的定义文件夹结构以确保代码组织有序.