Ask HN: Design patterns for separating business logic from common SASS config?

A common anti-pattern that is discussed around SASS codebases is the mixing of business logic with user configuration. Are there any design patterns that devs should know about that help keep unique business logic separate from the more generic user/billing/subscription/etc. portions?