styling-conventions

Styling Standards.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/sushaantu/boxento/styling-conventions
Clone the repo
git clone --depth 1 https://github.com/sushaantu/boxento

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 171 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00171
Opus 5 $0.00000 $0.00086
Sonnet 5 $0.00000 $0.00034
Haiku 4.5 $0.00000 $0.00017

Measured today against content hash 0bc2c12cd930, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

styling-conventions 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 today.

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.

.cursor/rules/styling-conventions.mdc · 17 lines

What it actually says

  • Use Tailwind CSS classes exclusively for styling
  • Follow utility-first CSS methodology
  • Avoid creating custom CSS files unless absolutely necessary
  • Use Tailwind's @apply directive for reusable styles in components
  • Maintain consistent spacing and layout using Tailwind's spacing scale
  • Use Tailwind's color palette for consistency
  • Support dark mode with Tailwind's dark: variant
  • Extract common class combinations into reusable React components
  • Use CSS variables (via Tailwind) for theming when appropriate
  • For complex animations, use framer-motion library with Tailwind classes
  • Place responsive design variants in a consistent order (sm:, md:, lg:, xl:)
  • Group related utility classes together (spacing, colors, typography)
Changes

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.

  1. today First seen · 17 lines · 171 tokens per session scan A 0bc2c12cd930

Subscribe to this mod's changes

styling-conventions is a cursor rule published in the GitHub repository sushaantu/boxento (153 stars, last pushed 20d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 171 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-09-01.