| name | domain-modeling |
|---|---|
| description | Use when designing models, planning features, structuring controllers, or making architectural decisions in a Rails app. Triggers on questions like "how should I model X", "where does this logic go", "should I make a service object", adding new resources, or restructuring existing domain logic. Use this skill whenever the user is thinking about where behavior lives in their app. |
This skill guides domain modeling decisions. The approach favors rich models, vanilla Rails conventions, and pragmatic simplicity over architectural ceremony.
The principles here are strong defaults, not commandments. Sometimes the right call is something different. Trust your judgment and the user's context.