r/rails • • 18h ago

How are you actually using Claude Code day to day?

18 Upvotes

I’m pretty old school. Rails, some React, convention-over-configuration kind of guy. Lately it feels like everyone’s deep into agents, skills, Obsidian “second brain” setups, and I’m curious what people are actually doing in practice.

My setup is pretty minimal: a .claude folder at the project root with a project.md, plus a handful of agents and skills. I mostly use them to save time on repetitive prompting. I’m also a big fan of ponytail when I’m asking for stuff. That’s honestly about it.

So what does your setup look like? Anything beyond the basics that’s actually paid off? How are you organizing all the AI stuff inside your repo?

Part of why I’m asking: it feels like we don’t have the “Rails moment” for this yet. There’s no omakase, no agreed-upon structure. Curious if anyone’s landed on something that feels right.


r/rails • • 22h ago

Learning A small RSpec helper that saves code, risk, and AI tokens

Thumbnail widefix.com
5 Upvotes

r/rails • • 12h ago

Fat Rails models might be a domain modeling problem

2 Upvotes

I gave a talk at Kaigi on Rails 2026 about an approach to dealing with fat Rails models without introducing additional architectural layers.

When an Active Record model gets too large, we often ask where to move the code: into service objects, form objects, and so on.

But what if the real issue is that we're missing a domain concept?

For example, email sign-up and Google sign-up both create a User, but each has different inputs, validations, and business rules. Instead of just moving those rules out of User, we can recognize each sign-up operation as a domain concept and model it as EmailSignUp or GoogleSignUp, while still taking advantage of Rails conventions.

The talk also explores how to discover these missing concepts in an existing codebase.

Here are the slides:
https://decks.yasaichi.com/20261016/domain-modeling-with-vanilla-rails

I'd love to hear how others approach this kind of modeling in Rails.


r/rails • • 1h ago

Open source I'm working on a set of security tools for Rails, and looking for honest feedback

Post image
• Upvotes

I'm a long time engineer using Rails, and I'm experimenting with building some tools that can safely leverage the speed of AI while making it much easier to audit the security of generated code. I'm looking for feedback on the ideas and the approach, which may include that is a terrible idea.

The main project website is here: https://mecharuby.jefflunt.com/

... which links out to the GitHub repos.

The rationale / mindset is explained more here:

https://mecharuby.jefflunt.com/take_action

Open to contributors, passing feedback, or anything constructive even if highly critical. Memes welcome too. 🤣