When is a model considered a candidate for this refactoring?

A model is a candidate if it has 3+ methods sharing a prefix, coordinates multiple associations simultaneously, or contains mixed conceptual domains that make the API confusing.

Can I use Affordances for single-method extractions?

No, the pattern specifically requires a minimum of 3 related methods to avoid over-engineering; single methods should remain as plain methods or association extensions.

Does this skill help with testing?

Yes, by extracting logic into POROs with the parent model as the only dependency, it makes unit testing domain logic much simpler and faster compared to testing fat ActiveRecord models.

What is an Affordance in the context of Ruby on Rails?

An Affordance is a PORO (Plain Old Ruby Object) wrapper that groups 3 or more related operations around a specific noun or concept, providing a cleaner API than traditional model methods.

How does this differ from a Rails Concern?

Concerns are best for infrastructure, callbacks, and validations that Rails calls implicitly. Affordances are for explicit operations and domain logic that the developer calls directly.

Rails Writing Affordances

Name: Rails Writing Affordances
Author: ZempTime

byZempTime

•

개발자 도구

Refactors bloated Rails models into clean, concept-driven PORO wrappers to improve maintainability and domain clarity.

소개

The Writing Affordances skill helps developers deconstruct 'fat' Ruby on Rails models by identifying related method clusters and extracting them into specialized Plain Old Ruby Object (PORO) wrappers. It provides a structured architectural pattern for grouping operations around specific nouns or concepts, moving away from repetitive method prefixes and cluttered model files. This skill offers a comprehensive decision framework to distinguish when to use Affordances versus Concerns or Association Extensions, ensuring that your business logic remains isolated, testable, and intuitively accessible through a clean, noun-based API.

주요 기능

1 GitHub stars
Distinguishes between Concern-based infrastructure and Affordance-based APIs
Provides heuristics for coordinating logic across multiple model associations
Identifies repetitive method prefixes (e.g., entropy_*) for extraction
Guides the implementation of factory patterns for model-centric wrappers
Enforces PORO constraints to prevent ActiveRecord inheritance bloat

사용 사례

Refactoring a monolithic Rails model with overlapping domain responsibilities
Grouping complex notification or state-tracking logic into a dedicated object
Cleaning up models where 3+ methods coordinate multiple disparate associations

소개

주요 기능

1 GitHub stars
Distinguishes between Concern-based infrastructure and Affordance-based APIs
Provides heuristics for coordinating logic across multiple model associations
Identifies repetitive method prefixes (e.g., entropy_*) for extraction
Guides the implementation of factory patterns for model-centric wrappers
Enforces PORO constraints to prevent ActiveRecord inheritance bloat

사용 사례

Refactoring a monolithic Rails model with overlapping domain responsibilities
Grouping complex notification or state-tracking logic into a dedicated object
Cleaning up models where 3+ methods coordinate multiple disparate associations