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.
git clone --depth 1 https://github.com/levifig/rails-instructionsWrote 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/levifig/rails-instructions/styling)<a href="https://agentmods.dev/rules/levifig/rails-instructions/styling"><img src="https://agentmods.dev/badge/rules/levifig/rails-instructions/styling/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/levifig/rails-instructions/styling"><img src="https://agentmods.dev/badge/rules/levifig/rails-instructions/styling.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.01004 |
| Opus 5.5 | $0.00000 | $0.00402 |
| Sonnet 5.5 | $0.00000 | $0.00201 |
| Haiku 4.5 | $0.00000 | $0.00100 |
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 1mo 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rails Styling with TailwindCSS
Core Philosophy
- Use utility-first CSS for rapid development
- Avoid writing custom CSS when utilities exist
- Keep styling consistent across the application
- Design mobile-first, enhance for desktop
- Let TailwindCSS handle the complexity
TailwindCSS Principles
- Compose styles using utility classes
- Avoid premature abstraction into components
- Use consistent spacing and sizing scales
- Leverage TailwindCSS's design system
- Keep HTML as the source of truth for styling
Configuration Strategy
- Extend default theme rather than replacing it
- Define custom colors sparingly
- Use CSS variables for dynamic theming
- Configure content paths correctly
- Keep configuration minimal
Rails Integration
- Use Tailwind's standalone CLI approach
- Configure asset pipeline integration properly
- Set up proper purging for production
- Use Rails helpers with Tailwind classes
- Keep build process simple
Utility-First Approach
- Start with utilities before extracting components
- Use modifier classes for responsive design
- Apply state modifiers directly in HTML
- Leverage arbitrary values when needed
- Keep utility usage consistent
Component Patterns
- Extract components only when truly reusable
- Use
@applysparingly and deliberately - Keep extracted components simple
- Document component patterns clearly
- Prefer composition over complex components
Responsive Design
- Design mobile-first always
- Use breakpoint prefixes consistently
- Test at all breakpoint sizes
- Consider touch targets on mobile
- Optimize for common device sizes
Color Management
- Use Tailwind's color palette
- Define semantic color names
- Maintain consistent color usage
- Support dark mode properly
- Test color accessibility
Typography System
- Use Tailwind's typography scale
- Keep font sizes consistent
- Implement proper line heights
- Use appropriate font weights
- Consider readability always
Spacing Guidelines
- Use Tailwind's spacing scale exclusively
- Keep spacing consistent throughout
- Apply spacing systematically
- Use negative margins carefully
- Document spacing decisions
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.
- 1mo ago First seen · 185 lines · 0 tokens per session scan A 67fa2ff51fbf
styling is a cursor rule published in the GitHub repository levifig/rails-instructions (56 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,004 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
chakra-ui-best-practices
A set of rules for building React interfaces with Chakra UI, a component library for styled and accessible user interfaces. It covers themes, responsive layouts, accessibility, performance, and reusable components.
chakra-ui---accessibility-features
An accessibility rule for React interfaces built with Chakra UI, a component library. It covers semantic HTML, screen-reader labels, keyboard navigation, focus handling, and color contrast.
chakra-ui---responsive-design
Guidance for making Chakra UI layouts adapt to different screen sizes. It uses responsive style values, breakpoints, layout components, and conditional display rules for phones, tablets, and desktops.
chakra-ui---theme-directory-rules
Rules for organizing a Chakra UI theme into an entry file, foundational settings, and component-specific styles. The theme controls shared colors, fonts, spacing, breakpoints, and component variants.
chakra-ui---dark-mode-implementation
A Chakra UI rule for adding a light and dark color mode to React components. It covers switching modes, following the system preference, storing the choice, and preventing a flash of the wrong theme during loading.
react-chakra-ui---folder-structure
A standard folder layout for React and Chakra UI projects, including separate locations for components, pages, themes, hooks, utilities, and assets. It also defines how Chakra UI theme files are grouped.