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 instructions/levifig/rails-instructions/rails-stylinggit 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/instructions/levifig/rails-instructions/rails-styling)<a href="https://agentmods.dev/instructions/levifig/rails-instructions/rails-styling"><img src="https://agentmods.dev/badge/instructions/levifig/rails-instructions/rails-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.01000 | $0.01000 |
| Opus 5 | $0.00500 | $0.00500 |
| Sonnet 5 | $0.00200 | $0.00200 |
| Haiku 4.5 | $0.00100 | $0.00100 |
Grade A, and why
rails-instructions rails-styling.instructions.md 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 5d 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 — 209 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.
- 5d ago First seen · 209 lines · 1,000 tokens per session scan A 5edc0fd9d7dc
rails-instructions rails-styling.instructions.md is an instructions file published in the GitHub repository levifig/rails-instructions (54 stars, last pushed 1y ago), licensed MIT. It adds 1,000 tokens to every session, about $0.0050 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.
Other instructions, from other repositories
claude-code-settings copilot-instructions.md
Instructions for feiskyer/claude-code-settings, covering claude.md, environment setup, required dependencies, configuration and skills.
PromptKit copilot-instructions.md
Instructions for microsoft/PromptKit, covering promptkit — copilot instructions, how to use this repository, what this repository is, architecture and component conventions.
agent-rules testing.instructions.md
Instructions for lirantal/agent-rules, covering testing guidelines for node.js applications, general testing principles, guiding principles, descriptive test naming (three-part structure) and structure tests by the aaa pattern.
apex-accelerator code-quality.instructions.md
Code quality guidelines: commenting best practices (WHY not WHAT) and review priorities with security checks.
agent-rules security-scanning.instructions.md
Instructions for lirantal/agent-rules, covering security scanning guidelines, your mission, security scanning of third-party dependencies and security scanning of code.
agent-rules child-process.instructions.md
Instructions for lirantal/agent-rules, covering system processes secure coding guidelines, your mission and spawning system processes.