Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Design & UI

implementation-design-patterns

Implementation guide for the 22 Gang of Four design patterns in TypeScript, distilled from refactoring.guru. Use this skill when writing, refactoring, or reviewing TypeScript that exhibits a pattern-shaped problem — class-explosion from inheritance, conditionals switching on type, tight coupling to concrete classes, tree-shaped models, runtime algorithm selection, undo/redo, snapshot-and-restore, state-dependent behavior, subscriber notification, or hiding subsystem complexity. Each pattern entry includes intent, problem, solution, applicability (when to use AND when NOT to use), a runnable TypeScript example, implementation steps, pros/cons, and relations to sibling patterns. Trigger even when no pattern is named — cues like "class getting unwieldy," "giant switch," "swap implementations at runtime," "combinatorial subclasses," "need undo," or "traverse a tree" are pattern-shaped. Covers all 5 Creational, 7 Structural, and 10 Behavioral GoF patterns.

pproenca · AI review on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add pproenca/dot-skills --skill implementation-design-patterns

About this skill


name: implementation-design-patterns description: Implementation guide for the 22 Gang of Four design patterns in TypeScript, distilled from refactoring.guru. Use this skill when writing, refactoring, or reviewing TypeScript that exhibits a pattern-shaped problem — class-explosion from inheritance, conditionals switching on type, tight coupling to concrete classes, tree-shaped models, runtime algorithm selection, undo/redo, snapshot-and-restore, state-dependent behavior, subscriber notification, or hiding subsystem complexity. Each pattern entry includes intent, problem, solution, applicability (when to use AND when NOT to use), a runnable TypeScript example, implementation steps, pros/cons, and relations to sibling patterns. Trigger even when no pattern is named — cues like "class getting unwieldy," "giant switch," "swap implementations at runtime," "combinatorial subclasses," "need undo," or "traverse a tree" are pattern-shaped. Covers all 5 Creational, 7 Structural, and 10 Behavioral GoF patterns.

TypeScript Design Patterns Best Practices (Refactoring Guru)

Implementation reference for the 22 Gang of Four design patterns in TypeScript, distilled from refactoring.guru. Each of the 22 pattern files across 3 categories captures intent, problem, solution, applicability, a runnable TypeScript example, implementation steps, pros/cons, and relations to sibling patterns.

The patterns are a vocabulary for structural decisions, not a prescription. Reach for a pattern only when its applicability criteria match the problem at hand — every pattern entry includes a When NOT to Use section to guard against over-engineering.

When to Apply

  • Refactoring a class that has grown unwieldy via inheritance — combinatorial subclasses, conditional branching on type, or a "god class" with many responsibilities
  • Designing a new module whose collaborators are not yet fixed — you want to keep the interface stable while implementations vary
  • Integrating an incompatible third-party API, library, or legacy class into existing code
  • Modeling a tree-shaped domain (file systems, organization charts, expression ASTs, UI component trees) where leaves and branches must be treated uniformly
  • Adding cross-cutting behavior at runtime — logging, caching, access control, decoration — without subclassing
  • Selecting an algorithm or behavior variant at runtime based on configuration, user input, or environmental conditions
  • Implementing undo/redo, history snapshots, transactional rollback, or scheduling/queueing of operations
  • Coordinating many objects whose direct mutual references have become tangled — a hub that brokers communication
  • Notifying many subscribers when something changes — event systems, reactive data flows
  • Reviewing code that smells like a pattern is implicit (large switch on kind, parallel class hierarchies, identical algorithm skeletons across siblings) — make it explicit

Rule Categories

#CategoryImpactPatternsWhen to reach for this group
1CreationalHIGH5Object construction is non-trivial, varies by configuration, or risks tight coupling to concrete classes
2StructuralHIGH7Composing classes/objects into larger structures while keeping parts substitutable
3BehavioralHIGH10Distributing responsibility and defining how objects collaborate at runtime

How to Use

  1. Recognize the shape. Read the Quick Reference below and identify which pattern's intent matches your problem. Most pattern-shaped problems sound like one of the listed phrases.
  2. Read the pattern reference. Open references/{category}-{pattern}.md. Confirm intent, then read Applicability and When NOT to Use before adopting.
  3. Adapt the example. The TypeScript example uses pedagogical names (ConcreteStrategyA, Receiver). Rename to domain terms before merging.
  4. Check the relations. Each entry ends with Related Patterns — siblings worth considering for the same problem.

Quick Reference

1. Creational Patterns (object instantiation)

  • creational-factory-method — Subclasses decide which concrete product to create. "I need to add new product types without touching the creator code." — HIGH
  • creational-abstract-factory — Produce families of related objects together. "My code must work with multiple matching variants (chair+sofa+table) and shouldn't mix families." — MEDIUM-HIGH
  • creational-builder — Construct complex objects step by step. "My constructor has 10+ parameters or I have a telescoping-constructor smell." — HIGH
  • creational-prototype — Clone objects through their own clone() method. "I need to copy objects without depending on their concrete class." — MEDIUM
  • creational-singleton — Guarantee a single shared instance with a global access point. "I need exactly one instance of this class — config, registry, pool." — MEDIUM

2. Structural Patterns (composition)

  • structural-adapter — Translate one interface to another. "I need to use a library whose API doesn't match what my code expects." — HIGH
  • structural-bridge — Split abstraction from implementation so they can vary independently. "I have two orthogonal dimensions and the subclass count is exploding." — MEDIUM
  • structural-composite — Treat individual objects and compositions uniformly. "I have a tree (folders/files, groups/items, components/children) and want one interface for leaves and branches." — HIGH
  • structural-decorator — Wrap an object
Read the complete source ↗