styling

A set of styling rules for Tailwind CSS, a tool that applies predefined design classes to web interfaces. It focuses on writing classes in ways the project can reliably detect and include.

In plain words
What is it for?
Use it when writing Tailwind classes, handling conditional styles, combining classes, and building reusable interface components.
Why use it?
It helps prevent styles from disappearing during the build and keeps class combinations consistent across the interface.

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/innei-template/smart-webapp-template/styling
Clone the repo
git clone --depth 1 https://github.com/innei-template/smart-webapp-template

Made for: Cursor.

Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,104 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.00008 $0.01104
Opus 5 $0.00004 $0.00552
Sonnet 5 $0.00002 $0.00221
Haiku 4.5 $0.00001 $0.00110

Measured 2d ago against content hash 8c822507b00e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

.cursor/rules/styling.mdc · 173 lines

How it starts

The opening of the file, as written. The whole thing — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.

TailwindCSS Styling Guidelines

This project uses TailwindCSS 4 with specific patterns and constraints.

Critical Rule: No Dynamic Classes

All Tailwind classes must be statically defined - no dynamic className values:

// ❌ Wrong - Dynamic class construction
const size = 'large'
const className = `text-${size}` // This won't work with Tailwind purging

// ❌ Wrong - Template literals with variables
const color = 'blue'
const className = `bg-${color}-500`

// ✅ Correct - Static classes with conditional logic
const className = clsx({
  'text-base': size === 'small',
  'text-lg': size === 'medium',
  'text-xl': size === 'large',
})

// ✅ Correct - Predefined class mappings
const sizeClasses = {
  small: 'text-base',
  medium: 'text-lg',
  large: 'text-xl',
}
const className = sizeClasses[size]

Class Utility Function

Use the cn() utility from src/lib/cn.ts for combining classes:

import { cn } from '~/lib/cn'

function Button({ className, variant = 'primary', ...props }) {
  return (
    <button
      className={cn(
        // Base styles
        'px-4 py-2 rounded-md font-medium transition-colors',
        // Variant styles
        {
          'bg-primary text-white hover:bg-primary/90': variant === 'primary',
          'bg-secondary text-secondary-foreground hover:bg-secondary/80': variant === 'secondary',
          'border border-border bg-background hover:bg-fill': variant === 'outline'
        },
        // External className override
        className
      )}
      {...props}
    />
  )
}

Color System Integration

Always use Pastel colors (see color.mdc rule):

// ✅ Use Pastel semantic colors
<div className="bg-background text-text border border-border">

// ✅ Use Pastel application colors
<button className="bg-primary text-white">

// ✅ Use Pastel fill colors for interactive elements
<input className="bg-fill border border-border">

Responsive Design Patterns

// Mobile-first responsive design
<div className="w-full md:w-1/2 lg:w-1/3">

// Responsive spacing
<div className="p-4 md:p-6 lg:p-8">

// Responsive typography
<h1 className="text-2xl md:text-3xl lg:text-4xl">

Read the full file on GitHub · 173 lines

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. 2d ago First seen · 173 lines · 8 tokens per session scan A 8c822507b00e

Subscribe to this mod's changes

styling is a cursor rule published in the GitHub repository innei-template/smart-webapp-template (142 stars, last pushed 6d ago), licensed MIT. It adds 8 tokens to every session and 1,104 once invoked, about $0.0000 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-08-30.