What it requires. Context mappings pull unconventional custom fields or loosely named variables instead of standard pricing-context attributes.
Why it matters. [reasoned] The context definition is the contract between quote data and the engine: ad hoc mappings couple pricing to unstable schema, faults surface at quote time, and clutter obscures the release-time diff the extension mechanism exists to carry.
How to fix it. Map standard attributes where they exist; name and document any custom mapping as deliberately as a public interface.
Source. Salesforce KB 004259656 (adjacent extension guidance; mechanism reasoned)
Is this rule worth checking?
Votes and comments are published here. We read them, and we publish what we change with the reasoning — a vote does not move a rule on its own.