Does this skill work with Sidekiq or Solid Queue?

Yes, it works with any background processor supported by ActiveJob, as it focuses on the Ruby code structure rather than the specific queuing backend.

What is the _later and _now naming convention?

The _later method handles enqueuing the background job, while the _now method contains the actual business logic. This allows you to call the same logic synchronously in tests or the console by calling the _now variant.

Why does this skill limit jobs to only 3-5 lines?

Keeping jobs thin ensures that business logic stays within the domain models. This makes the logic easier to test synchronously, reuse in the console, and keeps infrastructure separate from domain rules.

Should I pass model IDs or objects to the job?

This skill encourages passing the model instance itself. ActiveJob uses GlobalID to automatically serialize and deserialize the object, reducing boilerplate code inside the job's perform method.

Vanilla Rails Jobs

Name: Vanilla Rails Jobs
Author: ZempTime

byZempTime

•

API 개발

Enforces a strict architectural pattern for Ruby on Rails background jobs by keeping jobs thin and moving logic into models.

소개

The Vanilla Rails Jobs skill helps developers maintain clean and testable Rails applications by enforcing the 'thin job' pattern. It ensures that ActiveJob classes remain minimal wrappers of 3-5 lines that delegate all business logic to domain models using a standardized _later and _now naming convention. By moving logic out of infrastructure components and into the model layer, this skill facilitates easier synchronous testing, improved reusability in the console, and better debuggability through clearer stack traces.

주요 기능

1 GitHub stars
Promotes object-based serialization over manual ID lookups
Enforces a 3-5 line limit for ActiveJob class implementations
Moves business logic, queries, and conditionals into model concerns
Identifies architectural red flags like logic split between jobs and models
Standardizes naming conventions using _later and _now patterns

사용 사례

Standardizing background task patterns across a distributed Rails engineering team
Implementing background notification systems that remain testable without job workers
Refactoring legacy 'fat jobs' into maintainable, model-driven logic

소개

주요 기능

1 GitHub stars
Promotes object-based serialization over manual ID lookups
Enforces a 3-5 line limit for ActiveJob class implementations
Moves business logic, queries, and conditionals into model concerns
Identifies architectural red flags like logic split between jobs and models
Standardizes naming conventions using _later and _now patterns

사용 사례

Standardizing background task patterns across a distributed Rails engineering team
Implementing background notification systems that remain testable without job workers
Refactoring legacy 'fat jobs' into maintainable, model-driven logic