An API can look consistent and still be difficult to use safely. A successful response may hide unfinished work. A retry may create a second order. A cache may return one customer's data to another. These problems often come from convenient design shortcuts that become expensive once clients depend on them.
An anti-pattern is a recurring approach that appears useful but produces predictable problems in a particular context.
This catalog focuses on recognizing those contexts, identifying the harm, and choosing a correction that preserves legitimate client expectations.