GoF Patterns

• Use structural composition over inheritance
• Use multiparadigm code and contract-programming
• Use domain-specific languages (DSLs), prefer declarative way
• Separate and do not mix system and domain code
• Use GRASP and SOLID principles; especially reduce coupling
• Remember about referential transparency
• Prefer platform-agnostic code
• Implement isolation and layer borders with IoC & DI
• Use object/Map lookup for Strategy and polymorphic/dynamic dispatch
• Keep patterns simple
• Do not over-engineer for the sake of the pattern name

How to use

Pick the pattern from the lists, then read its pattern file (intent, problem, applicability, JS implementation, consequences, related patterns) and its example before implementing, explaining, or reviewing it. Follow the example's naming, structure, and idioms; domain names (User, IoTDevice) are placeholders. Read only the patterns the task needs.

Creational patterns

• Abstract factory: Switch a whole family of related objects (storage, UI kit) by one key. Read patterns/abstract-factory.md and examples/abstract-factory.js
• Builder: Assemble a complex product from many optional, order-sensitive steps. Read patterns/builder.md and examples/builder.js
• Factory: Centralize object creation: defaults, validation, and one final object shape. Read patterns/factory.md and examples/factory.js
• Factory Method: Pick the concrete class from input through a registry. Read patterns/factory-method.md and examples/factory-method.js
• Prototype: Clone a prepared instance instead of rebuilding it. Read patterns/prototype.md and examples/prototype.js
• Flyweight: Share immutable intrinsic state among many small objects. Read patterns/flyweight.md and examples/flyweight.js
• Singleton: One shared instance; prefer module state, context, or DI. Read patterns/singleton.md and examples/singleton.js
• Object Pool: Reuse expensive objects under bursty load. Read patterns/object-pool.md and examples/object-pool.js

Structural patterns

• Adapter: Make a foreign interface match the one your code expects. Read patterns/adapter.md and examples/adapter.js
• Wrapper: Add cross-cutting behavior around a function or interface. Read patterns/wrapper.md and examples/wrapper.js
• Boxing: Give a primitive a validated domain type (value object). Read patterns/boxing.md and examples/boxing.js
• Decorator: Layer optional behavior or metadata without subclassing. Read patterns/decorator.md and examples/decorator.js
• Proxy: Control access to an object (stats, cache, policy) without built-in Proxy. Read patterns/proxy.md and examples/proxy.js
• Bridge: Let two hierarchies (features, implementations) vary independently. Read patterns/bridge.md and examples/bridge.js
• Composite: Treat leaves and trees through one operation. Read patterns/composite.md and examples/composite.js
• Facade: One narrow API over a complex subsystem. Read patterns/facade.md and examples/facade.js
• Context: Pass capabilities and request state between layers without globals. Read patterns/context.md and examples/context.js