Rails App taste — ChatGPT prompt: what it does, how to install
Rails App taste is a prompt for ChatGPT, Claude.ai, and Claude Code that sets pragmatic Ruby on Rails development standards. Use it before starting an app or planning its architecture.
CC0-1.0 ★ 178,201 updated 2026-10-24
Open on GitHubWhat Rails App taste does
The prompt provides a comprehensive set of conventions for building Ruby on Rails applications. It enforces thin RESTful controllers, domain logic in models, Hotwire for interactivity, and strict database constraints. The guidelines cover background jobs with Active Job, caching strategies, secure parameters, and deployment workflows.
It directs the AI to produce code aligned with established community practices. The rules cover testing with Minitest or RSpec, security scanning with Brakeman, and RuboCop linting configurations.
What it helps with
- architect new Rails applications
- build thin RESTful controllers
- configure background jobs and Active Job
- resolve N+1 database queries
- write safe database migrations
Example prompts for the agent
- Generate a model structure for a new service following Rails App taste
- Write a controller and migration adhering to Rails App taste guidelines
- Suggest tests for a model using Rails App taste practices
How to install Rails App taste
How to use
Paste the text at the start of a chat or into project instructions
Manually: put the files in place
.claude/commands/prompts.csv.mdQuestions about Rails App taste
How to install Rails App taste in Claude Code?
Place the prompt file at .claude/commands/prompts.csv.md in your project root.
What does Rails App taste do?
It defines architectural standards and conventions for Ruby on Rails development when working with AI assistants.
Which platforms support Rails App taste?
The prompt runs on ChatGPT, Claude.ai and Claude Code.
Source text
prompts.csv · CC0-1.0
# Rails App taste of a pragmatic Ruby on Rails developer - Start new apps on the latest Rails with PostgreSQL, and stick to the defaults unless there is a clear reason to swap a piece out. Confidence: 0.90 - Keep controllers thin and RESTful, adding new resources like SessionsController or ArchivesController instead of custom actions. Confidence: 0.90 - Put domain logic in models and plain Ruby objects under app/models, and reach for service objects only when a workflow spans many models. Confidence: 0.75 - Use concerns sparingly and only for behavior that is genuinely shared, not to hide a bloated model. Confidence: 0.75 - Prefer Hotwire with Turbo and Stimulus for interactivity before adding a separate JavaScript SPA. Confidence: 0.85 - Validate data in the model and back it with database constraints like NOT NULL, unique indexes and foreign keys. Confidence: 0.95 - Write reversible migrations, add indexes concurrently on large tables, and never edit a migration that has already run in production. Confidence: 0.90 - Keep callbacks for simple data normalization and move side effects like emails and API calls into explicit jobs. Confidence: 0.85 - Run background work with Active Job on Solid Queue or Sidekiq, and keep every job idempotent and safe to retry. Confidence: 0.90 - Pass record IDs to jobs, not whole objects, and reload the record inside the job. Confidence: 0.85 - Catch N+1 queries with strict_loading or the Bullet gem, and fix them with includes or preload. Confidence: 0.90 - Use strong parameters everywhere and never pass params straight into update or create. Confidence: 0.95 - Store secrets in encrypted credentials or environment variables, never in committed YAML files. Confidence: 0.95 - Test with Minitest or RSpec, leaning on model and request tests, with a few system tests for critical flows. Confidence: 0.80 - Use fixtures or lean factories, and avoid deep factory chains that create half the database per test. Confidence: 0.75 - Lint with RuboCop using the rubocop-rails-omakase config or a small agreed set of rules, enforced in CI. Confidence: 0.80 - Scan for security issues with Brakeman and bundler-audit on every pull request. Confidence: 0.90 - Cache expensive views with fragment caching and cache keys based on updated_at, using Solid Cache or Redis. Confidence: 0.80 - Use scopes and query objects for reusable queries instead of long chains repeated across controllers. Confidence: 0.80 - Keep gems few and well maintained, and upgrade Rails one minor version at a time with deprecation warnings fixed first. Confidence: 0.85 - Deploy with Kamal or a managed platform using a Docker image built in CI, and run migrations as a separate release step. Confidence: 0.80 - Use Active Record encryption for sensitive columns like tokens and personal data. Confidence: 0.80
© f · CC0-1.0 · f/prompts.chat