According to Apple:

Class clusters are a design pattern that the Foundation framework makes extensive use of. Class clusters group a number of private concrete subclasses under a public abstract superclass. The grouping of classes in this way simplifies the publicly visible architecture of an object-oriented framework without reducing its functional richness. Class clusters are based on the Abstract Factory design pattern.

Say we want a public abstract superclass AMGContainer that internally can be implemented using a linked list, a doubly linked list or an AVL tree, but we don’t want the particularities of each one to be public.

Our public interface should be something like this:

typedef NS_ENUM(NSUInteger, AMGContainerType) { 

@interface AMGContainer : NSObject

@property (nonatomic, readonly) NSUInteger count;

// Helper for creating AMGContainer objects
+ (AMGContainer *)containerWithType:(AMGContainerType)type;

// Some methods that all containers will have
- (void)addElement:(id)element;
- (void)removeElement:(id)element;

@implementation AMGContainer

+ (AMGContainer *)containerWithType:(AMGContainerType)type 
    switch (type) {
        case AMGContainerTypeLinkedList:
            return [AMGContainerTypeLinkedList new];
        case AMGContainerTypeDoublyLinkedList:
            return [AMGContainerTypeDoublyLinkedList new];
        case AMGContainerTypeAvlTree:
            return [AMGContainerTypeAvlTree new];
    return nil;

- (void)addElement:(id)element { /* subclasses implement this */ }
- (void)removeElement:(id)element { /* subclasses implement this */ }


And each of the private subclasses will have to implement the data structure and the public methods:

@interface AMGContainerLinkedList : AMGContainer
@implementation AMGContainerLinkedList

- (id)init { /* whatever is needed, at least creating the data structure itself */ }
- (void)addElement:(id)element {...}
- (void)removeElement:(id)element {...}