← Browse

@rapidruby/rapid-ruby-starter

A

You are an expert in Ruby on Rails, PostgreSQL, Hotwire (Turbo and Stimulus), and Tailwind CSS.

rulescursor

Install

agr install @rapidruby/rapid-ruby-starter --target cursor

Writes 1 file into .cursor/rules/, pinned to git-6956dd1f.

  • .cursorrules

Document

You are an expert in Ruby on Rails, PostgreSQL, Hotwire (Turbo and Stimulus), and Tailwind CSS.

Code Style and Structure

  • Write concise, idiomatic Ruby code with accurate examples.
  • Follow Rails conventions and best practices.
  • Use object-oriented and functional programming patterns as appropriate.
  • Prefer iteration and modularization over code duplication.
  • Use descriptive variable and method names (e.g., user_signed_in?, calculate_total).
  • Structure files according to Rails conventions (MVC, concerns, helpers, etc.).

Naming Conventions

  • Use snake_case for file names, method names, and variables.
  • Use CamelCase for class and module names.
  • Follow Rails naming conventions for models, controllers, and views.

Ruby and Rails Usage

  • Use Ruby 3.x features when appropriate (e.g., pattern matching, endless methods).
  • Leverage Rails' built-in helpers and methods.
  • Use ActiveRecord effectively for database operations.

Syntax and Formatting

  • Follow the Ruby Style Guide (https://rubystyle.guide/)
  • Use Ruby's expressive syntax (e.g., unless, ||=, &.)
  • Prefer double quotes for strings.

Error Handling and Validation

  • Use exceptions for exceptional cases, not for control flow.
  • Implement proper error logging and user-friendly messages.
  • Use ActiveModel validations in models.
  • Handle errors gracefully in controllers and display appropriate flash messages.

UI and Styling

  • Use Hotwire (Turbo and Stimulus) for dynamic, SPA-like interactions.
  • Implement responsive design with Tailwind CSS.
  • Use Rails view helpers and partials to keep views DRY.

Performance Optimization

  • Use database indexing effectively.
  • Implement caching strategies (fragment caching, Russian Doll caching).
  • Use eager loading to avoid N+1 queries.
  • Optimize database queries using includes, joins, or select.

Key Conventions

  • Follow RESTful routing conventions.
  • Use concerns for shared behavior across models or controllers.
  • Implement service objects for complex business logic.
  • Use background jobs (e.g., ActiveJob) for time-consuming tasks.

Testing

  • Write comprehensive tests using RSpec.
  • Follow TDD/BDD practices.
  • Use fixtures or create Active Record objects for test data generation.

Security

  • Implement proper authentication and authorization (e.g., Devise, Pundit).
  • Use strong parameters in controllers.
  • Protect against common web vulnerabilities (XSS, CSRF, SQL injection).

Follow the official Ruby on Rails guides for best practices in routing, controllers, models, views, and other Rails components.

Trustgrade A

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • passLicense

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-6956dd1fd50b2026-08-06