Enforce Rails model patterns for associations, validations, scopes, and concerns.
npx skills add https://github.com/apdarr/lace --skill models-apdarr
Please help me install this Agent Skill. Skill: models Source: https://github.com/apdarr/lace/tree/main/.github/skills/models Command: npx skills add https://github.com/apdarr/lace --skill models-apdarr
Rails model design can be complex and error-prone; this guide consolidates ActiveRecord patterns, validations, callbacks, scopes, associations, concerns, query objects, and form objects into a coherent, maintainable approach.
Define a model applying the patterns for associations, validations, scopes, concerns, and validators and place related query objects and form objects in their respective folders.
High-intent search queries and answers about installing and using this skill.
Structure Rails models by extracting complex logic into concerns, query objects, and form objects, ensuring clear separation of concerns. This approach maintains data integrity and promotes reusable, testable components across your ActiveRecord domain.
You need query objects and form objects in ActiveRecord when extracting complex queries or handling multi-model forms to split responsibilities. Placing them in dedicated folders improves testability and promotes reusable components across your Rails application.
Handle ActiveRecord validations and database constraints by enforcing a comprehensive set of patterns across your models. This ensures data integrity and scalable business logic while maintaining clean boundaries between ActiveRecord and ActiveModel semantics.
Yes, this Rails model pattern approach works specifically for typical domain-rich Rails applications where reusable components, testability, and maintainable business logic are critical. It enables consistent model design across services with clear separation of concerns.
Prevent ActiveRecord pitfalls like N+1 problems and overbearing callbacks by applying lightweight callbacks and extracting complex queries into query objects. This maintains clean boundaries and avoids common AR pitfalls in your domain models.
Yes, you can use custom validators and concerns to split responsibilities in Rails models. This promotes reusable components and improves testability by enforcing clear separation of concerns with dedicated folders for validators and concerns.
ThinkOodleCreate plain Ruby objects with Rails model-like validations and attributes.
SnakeORestructure Rails codebases by extracting business logic into service objects, concerns, and query objects.
fabnExtract Rails business logic into service objects, concerns, and query objects.
hnabyz-botApply modern Ruby and Rails patterns to APIs and web applications.
