Writing Design Patterns

Writing a design pattern requires a using a unique approach to documentation. The content of the pattern must be generic enough to avoid prescribing feature design yet specific enough to adequately define standards. It must account for common contexts without making the pattern too long. It must address the needs of all disciplines that use it.

The content of the pattern must define a component in a manner that allows interaction designers to reference it, in the context of any feature wireframe, as the foundation of the component’s appropriate usage, default behavior, interaction behavior, and appropriate considerations. When written well, design patterns free interaction designers to focus their efforts on defining how the component is used in the specific feature they are designing.

I know how to write design patterns with this approach.