CLAUDE.md for a Rails project

When to use this

Use it on a Rails 7 app. The rule that earns its place here is the schema one: agents will happily edit schema.rb to make a test pass, which desyncs everyone else. Fill in the project name and switch the test command if you run RSpec.

# [Project] — agent guide

## Stack
Ruby on Rails 7, Ruby 3.3, PostgreSQL. Dependencies with Bundler.

## Commands
- Install: `bundle install`
- Run: `bin/rails server`
- Migrate: `bin/rails db:migrate`
- Test: `bin/rails test`
- Lint: `bundle exec rubocop`

## Conventions
- Fat models, thin controllers. Push logic into models or service objects.
- Use strong parameters in every controller action that writes.
- Name things the Rails way so the conventions do the work for you.
- Prefer the Hotwire and asset setup already in the app over new front-end tools.

## How to work here
- Run the tests and rubocop before you call a task done.
- Keep each change focused on one task.

## Do not
- Do not edit `schema.rb` by hand; change it through a migration.
- Do not commit `config/master.key` or any credential.
- Do not skip or delete tests to make a task pass.

Why each section is there

• Stack pins the Rails and Ruby versions so the agent uses current generators and syntax.
• Commands give the real bin/rails, test and lint lines.
• Conventions encode the Rails habits that keep a codebase readable.
• Do not protects the schema, the credentials and the test suite.

You can build one from a form with the CLAUDE.md generator. For how an agent works from a file like this, read working with agents.